Bug description
The redirect path for the delete-action inside taxonomy and user-group detail view is currently hard-coded to e.g. "/cp/user-groups". See all affected .vue files here. Statamic instances which do NOT use "cp" as the default value for CP_ROUTE inside cp.php will therefore experience a broken redirect.
Expectation: The redirect route should not be hard-coded inside .vue files but be resolved from the globally configured cp route. Basically, a "remove" action should act exactly as in all other core entities (1. delete entity 2. redirect to list view of blueprint).
How to reproduce
- Change value for
route inside cp.php to e.g. "admin"
- Start statamic, log into the control panel at "/admin" and create a new user-group (or taxonomy)
- Inside the detail view of the newly created user-group (or taxonomy) click on "Delete User Group" (or "Delete Taxonomy)
- A modal window pops up showing a 404 error
Logs
Environment
Installation
Existing Laravel app
Additional details
No response
Bug description
The redirect path for the delete-action inside taxonomy and user-group detail view is currently hard-coded to e.g. "/cp/user-groups". See all affected .vue files here. Statamic instances which do NOT use "cp" as the default value for
CP_ROUTEinsidecp.phpwill therefore experience a broken redirect.Expectation: The redirect route should not be hard-coded inside .vue files but be resolved from the globally configured cp route. Basically, a "remove" action should act exactly as in all other core entities (1. delete entity 2. redirect to list view of blueprint).
How to reproduce
routeinsidecp.phpto e.g. "admin"Logs
Environment
Statamic 6.*Installation
Existing Laravel app
Additional details
No response