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
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()
The text was updated successfully, but these errors were encountered:
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()
The text was updated successfully, but these errors were encountered: