Skip to content
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

Open
paavo opened this issue Sep 23, 2019 · 6 comments
Open

Node-Selector for target field #30

paavo opened this issue Sep 23, 2019 · 6 comments

Comments

@paavo
Copy link

paavo commented Sep 23, 2019

Screenshot 2019-09-23 at 11 22 27

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.

@Sebobo
Copy link
Member

Sebobo commented Sep 23, 2019

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.

@paavo
Copy link
Author

paavo commented Sep 23, 2019

yes! i specially thought about multi-site installations..

@Sebobo
Copy link
Member

Sebobo commented Aug 14, 2020

And to make things harder: Also the dimension selection would be necessary.

@TheLalaMan
Copy link

TheLalaMan commented Mar 25, 2021

+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.

@paavo
Copy link
Author

paavo commented Apr 27, 2021

The missing node-selector keeps me away from using the redirecthandler-ui for every client.
Its still easier for the Editor to create a Shortcut and "search" for a Target Node instead of copy the final URL.
Also if a node gets renamed the Link will be dead.

@Sebobo
Copy link
Member

Sebobo commented Apr 27, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants