Affects Version/s: 1.7.1, 188.8.131.52, 1.8.0, 1.7.2, 1.9.0-beta1
Fix Version/s: QA tracked issues
Component/s: Platform > Repository & Services (Public API impl)
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:
and it would allow to have a content named, for instance, "ÀßÇÐ€ƒ".
One could afterwards access the content from frontend like:
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:
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.