You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose the following (which we shortly discussed during the Dresden sprint):
For creating a new redirect we do something like a little wizard.
Option 1 is they want to create a non-redirect status (like 404):
User selects a non-redirect status type(from a dropdown).
We only show the source url and the confirmation button says "Set status".
We check if the source url is a page/resource and go back to step 2 with a warning.
We store the new redirect and show a success message and the updated list.
Option 2 is they want to create a redirect (like 301):
User selects a redirect status type (from a dropdown)
We show the source and target url fields.
We do checks whether the source url is an existing page/resource and go back to step 2 and show a warning if that's the case (as the redirect wouldn't work).
We check whether an existing redirect with the same source url exists and go back to step 2 with a warning.
We check whether the target url actually exits and go back to step 2 with a warning if not.
We store the new redirect and show a success message and the updated list.
The idea is based on some discussion and diagrams I had with the friends from Yoast and how they do it in Wordpress.
Sounds like the way to go!
Just one addition: One big UX improvement would be to hide automatically generated redirects in the default view (#10 (comment))
Current behavior
After I add or update a redirect only that redirect is shown without an explanation.
First I thought this was a bug and only after looking at the code I saw that it "searches" for it after updating it.
It's also a bit hard to guess how to use the search feature.
Idea
actions
instead of the conditions based on the arguments.add
-feature and maybe just use one field which allows searching in all redirect fields.Status Code
with explanations instead of the free inputThe text was updated successfully, but these errors were encountered: