Use another approach to avoid 403/404 pages on entity save

Created on 6 May 2023, about 1 year ago
Updated 12 May 2023, about 1 year ago

Problem/Motivation

In #2944049: Saving a node without "rabbit hole bypass {entity_type_id}" redirects to an error page (403, 404) β†’ we addressed the following issue:

When editing a node without the "rabbit hole bypass {entity_type_id}" permission and e.g. Page not found enabled for that node, redirects the user to a 404 page.

It was done as a redirect on custom form submit. Now we'd like to get rid of entity plugin system, and eventually remove rabbit_hole_form_alter, which depends on the plugins.

We're looking for a solution that will be suitable for all content entity types without a need to define locations of form submits or anything like that.

πŸ“Œ Task
Status

Fixed

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡¦Ukraine Matroskeen πŸ‡ΊπŸ‡¦ Ukraine, Lutsk

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.69.0 2024