Join GitHub today
PLIP: Merge Products.RedirectionTool into core #1486
Proposer : vangheem
Seconder : ?
Allow users to manage redirects on their site and aliases to content.
Managing aliases and redirects on your site is a very important feature that should be handled OOTB.
Proposal & Implementation
yes please. I added a risk about "Current use of the word "Alias" in redirection tool is confusing". Most of my users when asking for this talk about creating short urls, extra urls, alternative urls for content.
Also I suspect the UI for this could be combined with the UI for adjusting the shortname. Currently the UI for changing the short-name is buried in rename, which is also not that intuitive. It makes sense if you get the folder metaphor, but people coming at CMS from a public website point of view are thinking of adjusting their urls.
The PLIP has been approved. See https://community.plone.org/t/framework-team-meeting-minutes-2016-04-12/1943
There is a usability issue with exposing/managing the redirection storage to end users which I seen a few times in the past, curious if others have the same experience. Or did this already change in Plone 5?
There is no distinction between manually added redirects by users and automatically added redirects when you move/rename content. In a large site you would want to clean up those automatic redirects after a certain period because they clutter te redirect list, sometimes also cause confusion, etc.
But as soon as you open the redirects to end users there are also explicit redirects that you shouldn't delete or at least be able to distinguish from.
For me this is a reason not to install redirectiontool by default, only when users request it and I can explain this caveat.
It would be great as a first step if the stored aliases/redirects would have a datetime atrribute and a label to indicate if the redirect as created automatically by the system or through redirectiontool by the user.
I think rewriting the product might be the better option:
Testing the product I found a severe usability problem: If a redirect exists and another redirect is created with the same name no feedback is issued. I would expect a message: There is a redirect with this name/URL already. You have the following options: Use new redirect, Keep current redirect
thanks for the heads up! I had it on the list to document it. Question: I was skimming the docs to see where it would fit, but I did not find a place. I was looking for a section where all the other controlpanels are documented. Did I miss to find it? If not, any suggestions where to put it?
@staeff good point !
When it get merged into CMFPlone it should go into the /docs dir of the repo.
Currently the /docs repo of CMFPlone is using 'old style' and not following best practices.
IMHO it's time to change that :)
Long answer short put into /docs of CMFPlone, and after that I will create a PR which cleans up /docs and moves files to places where they belong.
Later we will 'fetch' /docs and will place it under the other docs on docs.plone.org, IMHO this should go under 'working with content'
@polyester what do you think ?
@svx here is a list of things, that are needed or would be nice to have from my perspective.
This is one is needed for der Freitag: