Dissallowed key character error when å-ä-ö in url
Development and Programming
Hello.
I have 2 EE sites running on the very same hosts. Only difference is that one is yet running on EE2 and other is running on latest EE3 version.
How ever, when I try to access some foo-bar address where is scandinavian letters, the EE2 installation finds its way to 404, but the EE3 version shoots Dissallowed Key Character error instead of going to 404.
The reason why I tested this, was because of the reason im using Solspace TAG on both of my sites and thought this were an Tag-related issue. But it is not.
So, when i type example.com/foo/påå - EE2 = 404 as supposed. - EE3 = Disallowed Key Characters.
What has been changed, this sounds a bug to me.
I’ve managed to get the same error on at least one other situation also, where iframe-code block was set wrong. Seems to be pretty dead to try to talk here since no answers?
How are you managing to save an entry with those characters in the URL? As far as I’m aware, EE doesn’t support non-Latin characters in URL titles. I’ve found that restriction to be a real problem in the past when localising websites. My workaround was to create a “Custom URL Title” field that acts as a proxy for the real URL Title field. If you want to bullet-proof it, you can also create an extension that auto-fills the “Custom URL Title” field based on the title. You’ll also need to URL encode all instances of the Custom URL Title in your templates though. To do that you can make use of a plugin like Streeng.
Its a Tag that is coming to url when using Solspace Tag Add-on. So, if I add a tag to entry as “fåå” and click the tag cloud that is searching all entries with a tag “fåå” it shoots the dissallowed-error. Havent yet updated to 3.3.0 and latest Tag, so dont know if something has been done to this.
I’ve just tested those characters in my EE3 site and I don’t receive the disallowed characters message - the site simply shows the 404 page, as expected. However, I don’t have Solspace Tag installed.
Im beat. I even uninstalled Tag and still getting the error every possible scenario instead of ending up to 404. No idea how to start tracking why that error comes and not the 404 as should?