FIX: Properly encoded slugs when configured to (PR #8158)

When an admin changes the site setting slug_generation_method to encoded, we weren’t really encoding the slug, but just allowing non-ascii characters in the slug (unicode).

That brings problems when a user posts a link to topic without the slug, as our topic controller tries to redirect the user to the correct URL that contains the slug with unicode characters. Having unicode in the Location header in a response is a RFC violation and some browsers end up in a redirection loop.

Bug report:

This commit also checks if a site uses encoded slugs and clear all saved slugs in the db so they can be regenerated using an onceoff job.


You’ve signed the CLA, xfalcox. Thank you! This pull request is ready for review.

This pull request has been mentioned on Discourse Meta. There might be relevant details there:

This does mean that every slug will be regenerated