Skip to content

Minor restructuring without messing up old links #122

Closed
ballaschk opened this issue Sep 24, 2021 · 7 comments
Closed

Minor restructuring without messing up old links #122

ballaschk opened this issue Sep 24, 2021 · 7 comments

Comments

@ballaschk
Copy link
Collaborator

ballaschk commented Sep 24, 2021

Hi,

I consider carving out the "Events" from out of "Life at MPIMG" and putting them as a separate Top-Level item. We could then push the calendar inside that "Events" menu. Furthermore, the slug for "Life at MPIMG" is "/comissions/" which is a rather unfortunate remnant from our first steps when we built the menu. I'd like to rename this to, e.g., simply "life".

Could we pull this off without losing all the old links and bookmarks? Is it possible to move around the Calendar without breaking things?

I took a look at the "Weiterleitungen" section inside wagtail, but this seem rather inflexible and there are no wildcards allowed. I'd like to forward the page in the whole tree below the named sections to the new pages. As far as I can see, the forwarding tools only allow individual pages. Would I actually have to go through this and make entries for every individiual page in "en" and "de" flavors? (If yes, is there a way to feed the system a table with links, so that I have not to click a thousand times?)

EDIT: I just found the cryptic menu "wichtige Weiterleitungen" which accepts a text file. Now I just need a quick dump of the site's structure … I will try this on the testing server. The calendar cannot be moved as it seems.

Best
Martin

@donald
Copy link
Member

donald commented Sep 24, 2021

"Wichtige Weiterleitungen"? What is it in English? Switch.... "Import Redirects" 😂😂😂

@donald
Copy link
Member

donald commented Sep 24, 2021

I'm rather confident that we could do a "/old-path/..." -> "/new-path/..." with keeping the "..." in code. However, this would be kind of ugly as this should be content not code....

There is https://github.com/themotleyfool/wagtail-automatic-redirects which I understand adds redirects for a page and all its child pages when a url is changed (slug and/or page moved). Would need to be tested, of course.

@donald
Copy link
Member

donald commented Sep 24, 2021

The calendar cannot be moved as it seems.

We can make it moveable. However, the current the model would be, that a calendar at another location would be another calendar. See #110 (comment). This might be okay, if we move the events with it, so that the content at the new place would be the same. You'd still need redirects for the events if you want to make sure that deep links to individual events continue to work.

@donald
Copy link
Member

donald commented Sep 24, 2021

I think most sites wouldn't be to concerned with deep links stored by the user if the rearrange things. So the lazy approach would be to just restructure as see fit and let people rediscover the content at the new location.

@donald
Copy link
Member

donald commented Sep 27, 2021

"Wichtige Weiterleitungen"? What is it in English? Switch.... "Import Redirects" joyjoyjoy

Oh dear. They manage their translations via a translation platform... https://www.transifex.com/torchbox/wagtail/dashboard/ . I've update the translation there and maybe this will be in the next release, but I'm not 100% sure if I did it correctly on that platform.

Hacked it into the life server

cd /project/intranet/mpicms/venv0/lib/python3.7/site-packages/wagtail/contrib/redirects/locale/de/LC_MESSAGES
vi django.po
msgfmt -o django.mo django.po
apachectl restart

@ballaschk
Copy link
Collaborator Author

The calendar cannot be moved as it seems.

We can make it moveable. However, the current the model would be, that a calendar at another location would be another calendar.

Would this break all the subscriptions?

@ballaschk
Copy link
Collaborator Author

I think most sites wouldn't be to concerned with deep links stored by the user if the rearrange things.

Maybe you are right. I should not overthink things and just talk to the secretaries who are taking care of these few pages.

Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants