-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node-Selector for target field #30
Comments
Feature makes sense, thx. To implement this correctly one also has to keep multi-site installations in mind and how to deal with the domains etc. when creating absolute uris which the user can select. |
yes! i specially thought about multi-site installations.. |
And to make things harder: Also the dimension selection would be necessary. |
+1 for this feature. Our editors achieve this with shortcuts now, and I wanted to make them use the redirect UI, until I discovered that it's not possible to select pages from the document tree. The added benefit would also be that if the page moves or is renamed, the redirect stays in place, I think. |
The missing node-selector keeps me away from using the redirecthandler-ui for every client. |
One would need to integrate the node selection similar to what was done in the ACL editor https://github.com/sandstorm/NeosAcl/tree/master/Resources/Private/react-acl-editor Storing the url of the node at the moment of selection is easier. Storing the actual node and resolving the uri at runtime is much harder, because then the whole mechanic has to be adjusted. But either way it's some work. |
The "target field" currently suggests entering a uri or path, what is perfect for external redirects.
For internal redirects (to a DocumentNode of this neos installation) it would be awesome, specially for non-technical user, to search for DocumentNodes instead of copy pasting the url.
Some of our editors like to use the redirecthandler-ui to generate short-urls (like domain.tld/shortcut/) and redirect to a DocumentNode on the same website.
The text was updated successfully, but these errors were encountered: