Topic with Japanese in URL doesn't redirect if URL doesn't perfectly match

We had the same issues, @Falco fixed those issues yesterday.

You should upgrade your Discourse installation (through https://myforum.example.com/admin/upgrade) and after the upgrade you’ll need to “rebake” the slugs. You can follow @Falco’s directions on that:

Those directions worked perfectly for us :smiley: (btw thanks @Falco!)

5 Likes

This solution has fixed the problem, I had to rebake the slugs.


Amigo @Falco, thank you so much for putting so much effort for fixing the issue.

Also thank you @codinghorror @sam and everyone else who are putting years of experience for something free like discourse in order to make the internet a better place. Thank you

We appreciate your effort.

8 Likes

Thanks @Falco and Discourse team for the fix :rose:

After changing slug generation into encoded, it fixed the issue of 404 topics (without the need to rebake slugs).

We still faced the issue with not found categories, I tried things on staging Discourse to make sure I don’t mess up :grin:

Description of The Issue

  1. When I return the slug generation into ascii:

The categories work again, and their generated URLs are just fine (Arabic as expected):

https://discourse.coretabs.net/c/%D8%A7%D9%84%D8%A3%D8%B3%D8%A6%D9%84%D8%A9-%D9%88%D8%A7%D9%84%D8%A7%D8%B3%D8%AA%D9%81%D8%B3%D8%A7%D8%B1%D8%A7%D8%AA

But, the generated URLs for topics are just English (despite the title is actually Arabic), e.x:

https://discourse.coretabs.net/t/5-mktbat-baythwn-mfydt-lmsharye-telym-alalt/2930/5
  1. When I change the slug generation into encoded:

The categories do not work (showing Oops! That page doesn’t exist or is private.), though their generated URLs are just fine (Arabic as expected):

https://discourse.coretabs.net/c/%D8%B9%D8%A7%D9%85

And the topics are working, with their Arabic expected URLs:

https://discourse.coretabs.net/t/5-%D9%85%D9%83%D8%AA%D8%A8%D8%A7%D8%AA-%D8%A8%D8%A7%D9%8A%D8%AB%D9%88%D9%86-%D9%85%D9%81%D9%8A%D8%AF%D8%A9-%D9%84%D9%85%D8%B4%D8%A7%D8%B1%D9%8A%D8%B9-%D8%AA%D8%B9%D9%84%D9%8A%D9%85-%D8%A7%D9%84%D8%A2%D9%84%D8%A9/2930/5

The Fix

  1. Change the slug generation settings into ascii
  2. Change categories slugs into English from every category page
  3. Change the slug generation settings into encoded
  4. Now you can change the categories slugs into your language of choice
5 Likes

When I share the link to some other sites, the link becomes

E0%AE%AE%E0%AE%BF%E0%AE%A9%E0%AF%8D%E0%AE%A9%E0%AE%B2%E0%AF%8D-%E0%AE%B5%E0%AE%BF%E0%AE%B4%E0%AE%BF%E0%AE%AF%E0%AF%87-%E0%AE%95%E0%AF%81%E0%AE%9F%E0%AF%8D%E0%AE%9F%E0%AE%BF%E0%AE%A4%E0%AF%8D-%E0%AE%A4%E0%AE%BF%E0%AE%AE%E0%AE%BF%E0%AE%B0%E0%AF%87-2/1154/3

Encoding Works fine in URL

image

but when I copy & paste the URL somewhere, it becomes

I upgraded the Discourse to the latest release.

and I rebake the slugs as @Falco Mentioned. Still I am facing same issue. :frowning:

That is not an issue, it’s how it’s supposed to be.

A lot of places don’t support IRIs (URLs with “special” characters), so we are encoding those (those lots of %XX) so the will work anywhere (like when posting to Twitter).

Your browser is smart enough to show it decoded for you, so you don’t have to stare at it in the location bar.

10 Likes

Thank you for enlighten me! @Falco :slight_smile:
I will use URL shortener before share anywhere.

3 Likes

Several people on community.wanikani.com already noticed the fix for the original issue, and it looks good to me as well. However, I’m seeing the same subcategory issue others have mentioned (404 error for subcategories containing unicode characters). Since it’s a hosted site, can someone deploy the latest fixes and do the rebake (if necessary), so I can verify it’s fully fixed? If not, I guess I’ll check again in a week.

1 Like

Sure, we can do it early next week.

3 Likes

I think you have to go through the fix mentioned here:

3 Likes

Your site has been deployed to the last version and slugs have been rebaked.

4 Likes

My case seemed solved, as I mentioned above, :roll_eyes: but I see that in the “Categories” with “accents” these can be seen, but does not load the second page. :unamused:

I have the slugs in encoded

If I manually edit the category names and remove the accent, it works as expected, otherwise it doesn’t.

1 Like

Be sure to update to latest again, as subcategories received a fix last Friday. Visit /admin/upgrade to update.

3 Likes

This topic was automatically closed after 7 hours. New replies are no longer allowed.