Uploaded image for project: 'Magnolia pages module'
  1. Magnolia pages module
  2. PAGES-150

Pages app fails after i18n changes

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Critical
    • None
    • 5.5
    • Pages app

    Description

      If a site is copied and gets a different i18n settings then the wrong language version is displayed on content edit.

      Problem reproduction:

      1. Context Travel-Demo
      2. Duplicate the travel site in pages app
      3. Duplicate the travel site definition, adopt /travel/mappings/website@handlePrefix to travel0
      4. Change /travel0/i18n@fallbackLocale to de
      5. Edit /travel0/about

      Result
      The page itself is rendered in german. If a component is edited then english content is displayed. If the language is changed to eng then no content is displayed at all.

      How to fix this:

      BasicTransformer.deriveLocaleAwareName decides which locale should be used. This can't be overwritten.
      To solve this simply move the logic into i18NAuthoringSupport.deriveLocalisedPropertyName

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              jschulte Jan Schulte
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Bug DoR
                  Task DoD