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

Expose URLs based on functionality, do not assume wp-admin locations #7136

Closed
mkaz opened this issue Jun 5, 2018 · 1 comment
Closed

Expose URLs based on functionality, do not assume wp-admin locations #7136

mkaz opened this issue Jun 5, 2018 · 1 comment
Labels
[Type] Enhancement A suggestion for improvement.

Comments

@mkaz
Copy link
Member

mkaz commented Jun 5, 2018

Stemming from issue #7095

When Gutenberg is being used outside of wp-admin, for example as a front-end editor for P2, the expected redirect locations may be different than those within wp-admin. The specific case was for after the Move to Trash event, the redirect location is hard coded to edit.php which is the list of posts in wp-admin. However, for the P2/front-end use case, it might make more sense to redirect to the home page.

So a potential solution is to have the granular control to define redirection URLs, for example something like getRedirectURLAfterTrash()

@danielbachhuber
Copy link
Member

Closing for now per #7096 (comment)

It seems like this optimization isn't entirely necessary now, but we can reconsider it in the future if it comes up again.

@danielbachhuber danielbachhuber added the [Type] Enhancement A suggestion for improvement. label Jul 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

No branches or pull requests

2 participants