Repository navigation
Add redirect module and/or document work-around #693
Description
Activity
Hi @MRigal
Yes, I think something should be done about this. https://github.com/etianen/django-historylinks may work well for this, do you know this package? I haven't used it yet but I think this should solve the problem in a generic way.
- What do you think about it @matthiask ? Is there a work-around, or some way to do so currently? I couldn't find anything like this in the docs, neither browsing the codeThere is, but it's not automatic. You have a "redirect to" in page admin under "other options", that, well, redirects to somewhere else, even automatically translating Page IDs to the appropriate URL. So if you move a page, you'd have to generate a new page, fill the redirect_to field with "Page.page:342" (or whatever the id of the moved page is, the magnifying glass allows you to chose a page), and place it where the old page was.
Thanks to both of you!
@mjl we are actually using the
redirect_tofunction, but when combined with i18n and parent pages, we found ourselves several times landing in 404 deep water and we would have to manage a big amount of redirect pages. This one only really works well for smaller changes.The django-historylinks may be a good option, although not so well maintained. Let's see if we get to continue to work on the feature, I'll keep you updated!
Hi folks,
This is between an issue and a feature request I guess. Here is the use case:
Ideally, there would be a module/plugin that would automatically add 301 redirects to the old urls. Optionally, there is some option to do so while renaming/moving.
What do you think about it @matthiask ? Is there a work-around, or some way to do so currently? I couldn't find anything like this in the docs, neither browsing the code