I agree 1 is a better path to take, I would recommend continuing down this path
7 Likes
Pull request is up
9 Likes
I see this was merged. How long does it usually take to get deployed to a hosted site?
1 Like
faced similar problem after we’ve updated to latest today. reporting here to see if it is the same bug. is it?
this topic doesn’t load and it gives us 400 bad request:
or this one opens up as a blank page:
https://padpors.com/t/نقد-حرکتِ-«شکل-دادن-به-بانکی-از-پرسشها-و-مسئله��/6841
update: for the moment we’ve changed the slug generation method to ascii, as any topic with long topic length happened to open blank or with 400-error.
Are we good on this @Falco?
I confirm the bug has been fixed (just updated Discourse)
Thanks Discourse team 
5 Likes
I updated my discourse but I am still facing the same issue.
Are you on tests-passed? How did you update?
1 Like
I realized that some topics are showing 400 Bad Request, examples
https://forums.coretabs.net/t/مشكلة-في-عمل-فورمة-تسجيل-بيانات-للمستخدم-بـ-دجانج%/3117
https://forums.coretabs.net/t/كيف-أغير-الواجهة-في-vue-حسب-الحالة-مسجل-دخول-غير-مسجل%/3109
https://forums.coretabs.net/t/مشروع-يضم-مبرمجين-لتطبيقات-الموبايل-مع-مبرمجين-ا%D/2843/9
The common thing is that they all have % symbol
While other “working” topics do not have that symbol.
- I tried putting the IP address of the server instead of
forums.coretabs.net, and nginx shows the same error (instead of cloudflare).
1 Like
Always via Discourse updater. The right way!
That doesn’t really answer my question. Which version are you on according to /admin?
Did you visit /admin/update to force an update? You won’t be alerted unless a new beta release goes out and need to manually visit that URL to grab the incremental updates to tests-passed.
2 Likes
Hello @Stephen,
You are right. I wasn’t notified for this update, after visiting the upgrade page, there was a new update. It fixed my problem. Thank you @Falco for the fix.
-=-=-=- Update -=-=-=-
After upgrade, some pages get 400 Error just like the problem @YaserAlnajjar is facing here.
5 Likes
@Pad_Pors @YaserAlnajjar @Arta_S just merged another round of fixes, please update and check it out.
6 Likes
Hi @Falco, I just updated and unfortunately the problem continues. 
4 Likes
Are you using encoded slug generation method, and was it set to that during the update?
3 Likes
Honestly, I don’t know what method using … only that my forum is in Spanish language and after updating, the categories whose name bears “accent” show error 404.
3 Likes
Oh my I spent so much looking into this, and looks like you are using ascii slugs. Please revert back to encoded.
5 Likes
How should I do this? any guide or tutorial… thanks for you help.
2 Likes
Search the site settings slug generation method in your admin dashboard.
5 Likes
Great, great, thanks! … I change for encoded and everything works now!
Ascii was the one by default … I still don’t understand what differences these make, but at least it works for me. 
2 Likes