Add option to use case-insensitive Redirects #13085
Labels
Comments
This comment has been minimized.
This comment has been minimized.
|
Hi @andylolz! Before opening this issue, I went through the issues and saw the one you mentioned. My proposal is related to the Wagtail Redirects feature specifically. We have no desire to change the page routes. |
|
Oh I see! Apologies – I misunderstood. Yes, that makes sense. In that case, I’ve hidden my reply as off-topic. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your proposal related to a problem?
Last month, we migrated our government website to Wagtail, and it has 184,269 Pages as all departments publish their content to the same website. Usually, departments and the central government use redirects to publicise and advertise campaigns, services and other information. One example is
/ActionPlanOnBullyingor/ActuarialReviewoftheSocialInsuranceFund, where they use capitalisation for better understanding, to be more intuitive and make it easier for citizens to memorise.For each of those redirects, the content managers need to create multiple redirects to guess possible ways it will be advertised or used by other media and users.
Describe the solution you'd like
Wagtail have an option to change the Redirect model and middleware to handle redirects in a case-insensitive manner, for example,
REDIRECTS_CASE_INSENSITIVE = True.Describe alternatives you've considered
The redirect middleware is easy to extend or replace, but for the model, the only option is to replace it entirely or maybe monkeypatch it.
Additional context
I would prefer to first check if Wagtail can have a customisation for it before adding any custom code on top of it, as we are using and plan to use Wagtail for all government websites we manage.
Working on this
N/A
Anyone can contribute to this. View our contributing guidelines, add a comment to the issue once you’re ready to start.
The text was updated successfully, but these errors were encountered: