Uploaded image for project: 'Jahia Community'
  1. Jahia Community
  2. JAHIA-2108 XML migration: required improvements
  3. JAHIA-2110

Dinamicaly modify the sitekey when there's a conflict with an already existing site

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Done
    • Major
    • WCM 5.0 SP3
    • WCM 5.0 SP3
    • None

    Description

      When we import a site which has the same sitekey that an already existing site, import fails. so we have to edit the site.properties file in export archive in order to modify the key and then reimport. A so much trivial but boring operation could be more userfriendly if we had the possibility to modify it during import process.
      Maybe an intermediate screen displayed only when there's a conflict. I don't know if there would be a problem as we stay on sites management screen after import starts. Maybe we should be displayed a "preparing import" screen while archive is uploaded / opened , a "sitekeys conflict" screen if needed, and finally a "processing import" screen. An other potential problem I see is that if the archive contains more that one site, it seems to me that sites are imported one after one. In this case, sitekeys should be checked for each site at the begining of the import process, it would be problematic that import stops waiting user defining a new sitekey for the second imported site.

      TestRail: Results

        Attachments

          Activity

            People

              tdraier_old Thomas Draier (Inactive)
              dsaulnier_old Damien Saulnier
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                TestRail: Runs

                  TestRail: Cases

                    Packages

                      Version Package
                      WCM 5.0 SP3