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

UTF-8 characters in page name can cause loading to fail

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Neutral
    • None
    • 6.2.11
    • Pages app
    • None

    Description

      Steps to reproduce

      1. Enable UTF-8 encoding by setting magnolia.utf8.enabled in magnolia.properties
      2. Create a page with a name containing a UTF-8 encoded ä in NFD form (\x61\xCC\x88)
      3.  Preview the created page

      Alternatively there is a PR with UI tests reproducing the issue.

      Expected results

      The page previews normally

      Actual results

      Page preview results in a 404

      Workaround

      Only use NFC form. Rename existing pages accordingly.

      Development notes

      The pages app can be fixed by normalising the node names in NodeNameHelper#getValidatedName(java.lang.String, java.lang.String).
      This doesn't fix the problem when bootstrapping content though. In that case we deal with YAML (which doesn't specify the encoding) or XML (which does). YAML is handled by (DataTransporter#importYamlStream) us so we could do the normalising somehow. XML is fed into JR directly (DataTransporter#importXmlStream) making normalisation much harder.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              mduerig Michael Duerig
              AuthorX
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Checklists

                  Bug DoR
                  Task DoD