- Issue created by @GeduR
- 🇪🇸Spain tunic Madrid
I'm wondering if we should keep the old URLs for a while.The module has not so many users so I guess we can skip this part, because is not trivial.
We could use a redirection, but that's implies using the Redirect module (no way) or adding custom code (it feels like an overkill). We could also duplicate menu items with each url and adding a deprecation warning, but it also seems too much effort.
I guess it is enough to comment it in release notes or maybe creating a change record. I would go with the change record just to get more used to them, I have barely used them.
- Assigned to tunic
- Status changed to Fixed
almost 2 years ago 3:45pm 20 April 2023 - Status changed to Needs work
almost 2 years ago 5:03pm 20 April 2023 - 🇪🇸Spain tunic Madrid
Oops, I missed some URLs, I only changed the group plugins URLs.
- Status changed to Needs review
almost 2 years ago 6:00pm 20 April 2023 - 🇪🇸Spain tunic Madrid
Well, is not that simple.
The plugin id is used as-is in the URL. Currently, the plugin ids are like this:
- queries_data_vocabulary
- queries_data
- queries_data_user
- ux_ui_architecture
- ...
We only need to change the plugin ids... but machine names tend to use underscores. We could add code to handle this (transform the id string to use hyphens when it is used for the URL) but I don't think it's worth the effort. Also, the URLs are internal, not to be published, son the biggest problem is they may feel awkward.
I've changed the easy routes (the ones that are in the module's routing file).
- Assigned to lpeidro
- 🇪🇸Spain lpeidro Madrid
Thanks @tunic not problem, I check your commit and try to solve this issue, I think that I know the easiest way to do it.
- Issue was unassigned.
- Status changed to Fixed
almost 2 years ago 9:28am 21 April 2023 - 🇪🇸Spain lpeidro Madrid
I have checked it and you are right, it is not worth the effort.
- Status changed to Fixed
over 1 year ago 8:55am 28 April 2023