Search

Syntax Help
AdvancedBasic
1 of 1
Uploaded image for project: 'Repository'
  1. Repository
  2. REPOSITORY-493

Automatic migration: newrepository is never false

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • 4.4.14, 4.5.4, 4.6.0
    • 4.4.13, 4.5.3, 4.6.0
    • None
    • None
    • 4.6 M2

      On automatic migration on new repositories, the property ametys:newrepository on ametys:versions node is never set to false because we never save the modification when setting it to false.

          Bérénice Maurel added a comment - - edited

          You may arrived on this issue during a failed automatic migration, please follow this guide.

          Script to detect potential migration problems

          Replace deliverDate by your first deliver date. If it is before august 2020, you should not have these issues.

          let deliverDate = '2020-08-01';

if (Ametys.serviceManager.lookup("org.ametys.plugins.repository.migration.jcr.data.VersionsRootHelper").isNewRepository())
{
    const DateUtils = Java.type("org.ametys.core.util.DateUtils");
    const DATE_FORMATTER = java.time.format.DateTimeFormatter.ofPattern("dd/MM/yyyy");

    let oldMigrationsToCheck = Repository.query(`//element(*, ametys:version)[not(fn:name() = 'v-0') and jcr:like(@ametys:comment, 'Automatic Initialization%') and @ametys:executionDate > xs:dateTime('${deliverDate}T00:00:00.000+01:00')]`);
    if (oldMigrationsToCheck.getSize() > 0)
    {
        logger.warn("Old migrations to check:");
        oldMigrationsToCheck.forEach(
            version =>
            {
                logger.warn(` + ${DATE_FORMATTER.format(DateUtils.asZonedDateTime(version.getExecutionDate()))} ${version.getVersionNumber()} ${version.getComponentId()} ${version.getComment()}`);
            }
        );
    }
}

          If you obtain a list of versions, you can exclude the version of your first delivery date, and the migration components from plugins which are new in your project. For example, on December 2021, you added the plugin cart, and you deliver your project, the line plugin.cart.jcr in december 2021 can be ignored.

          For other cases, you have to check each migration, maybe they should be done manually, and at the end, the property ametys:versions/@ametys:newrepository should be set to false (don't forget to save it).

          Bérénice Maurel added a comment - - edited You may arrived on this issue during a failed automatic migration, please follow this guide. Script to detect potential migration problems Replace deliverDate by your first deliver date. If it is before august 2020, you should not have these issues. let deliverDate = '2020-08-01' ; if (Ametys.serviceManager.lookup( "org.ametys.plugins.repository.migration.jcr.data.VersionsRootHelper" ).isNewRepository()) { const DateUtils = Java.type( "org.ametys.core.util.DateUtils" ); const DATE_FORMATTER = java.time.format.DateTimeFormatter.ofPattern( "dd/MM/yyyy" ); let oldMigrationsToCheck = Repository.query(` //element(*, ametys:version)[not(fn:name() = 'v-0' ) and jcr:like(@ametys:comment, 'Automatic Initialization%' ) and @ametys:executionDate > xs:dateTime( '${deliverDate}T00:00:00.000+01:00' )]`); if (oldMigrationsToCheck.getSize() > 0) { logger.warn( "Old migrations to check:" ); oldMigrationsToCheck.forEach( version => { logger.warn(` + ${DATE_FORMATTER.format(DateUtils.asZonedDateTime(version.getExecutionDate()))} ${version.getVersionNumber()} ${version.getComponentId()} ${version.getComment()}`); } ); } } If you obtain a list of versions, you can exclude the version of your first delivery date, and the migration components from plugins which are new in your project. For example, on December 2021, you added the plugin cart, and you deliver your project, the line plugin.cart.jcr in december 2021 can be ignored. For other cases, you have to check each migration, maybe they should be done manually, and at the end, the property ametys:versions/@ametys:newrepository should be set to false (don't forget to save it).

            bmaurel Bérénice Maurel
            bmaurel Bérénice Maurel
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: