-
Bug
-
Resolution: Unresolved
-
Neutral
-
None
-
6.2.11
-
None
Steps to reproduce
- Enable UTF-8 encoding by setting magnolia.utf8.enabled in magnolia.properties
- Create a page with a name containing a UTF-8 encoded ä in NFD form (\x61\xCC\x88)
- 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.
Acceptance criteria