Using an UTF-8 character in a category slug seems to cause issues. After creating the category the admin gives a 404 and the category is inaccessible using the category link (/c/b%C3%A4r/6/l/latest.json?ascending=false) Tested on 2.7.0.beta3. I think this is a regression? [image]

What is the value of slug generation method ?

I was not even aware of that setting. It was set to ascii. Setting it to encoded solves the issue. Thanks! Not sure I understand why, since the generated slug was nicely encoded.

We do quite a lot of extra work do deal with the encoded slugs when this site setting is enabled. I believe what we are missing is a validation that block you from setting this non-ascii slug manually without flipping the setting first?

UTF-8 character in category slug causes problems with ASCII slugs

Support

RGJ (Richard - Communiteq) January 29, 2021, 7:38pm 5

Yes, I think you’re hitting the nail on the head.

1 Like

Topic		Replies	Views
Allow or not accented characters in category slug according to "slug generation method" setting Feature	6	1365	November 19, 2020
404 on various categories Bug	8	1174	October 16, 2019
Newly added non-ASCII category page does not load Bug	12	1306	July 30, 2020
Click the edit button on the category page to go to page 404 Bug	10	1087	December 28, 2021
Category slug containing Unicode characters results in redirect loop Bug	7	1642	January 15, 2021

UTF-8 character in category slug causes problems with ASCII slugs

Related topics