Details
-
Bug
-
Resolution: Unresolved
-
High
-
1.7.1, 1.7.1.1, 1.8.0, 1.7.2, 1.9.0-beta1
-
None
Description
Not sure this is actually an issue or not, but it comes as something that legacy had, that does not yet exist on platform, seemingly.
On legacy, on had the setting:
[URLTranslator] TransformationGroup=urlalias_iri
on:
ezpublish_legacy/settings/override/site.ini.append.php
and it would allow to have a content named, for instance, "ÀßÇЀƒ".
One could afterwards access the content from frontend like:
http://<your_hostname>/ÀßÇЀƒ
Steps to reproduce:
1. Go to platform ui admin interface, to "Content -> Content structure";
2. Under home content "eZ Platform" create some content of any content type, and name it ÀßÇЀƒ. Publish it;
There is no way to access the content from its name, something like: http://<your_hostname>/MyArticle
If you try:
http://<your_hostname>/ÀßÇЀƒ
you will get a 404 Error because the name has been encoded to something else.
This arises from running sanity tests on EZP-26748 on platform.