Closed (fixed)
Project:
Read only mode
Version:
2.0.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
10 Sep 2025 at 09:16 UTC
Updated:
17 Dec 2025 at 11:59 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #3
a.dmitriiev commentedComment #4
sandeep_k commented@a.dmitriiev, I tested this on my Drupal version 11.2 and was able to successfully reproduce the error by following the given steps. The MR “MR !8 mergeable” applied successfully; however, after revisiting the site post-merge, the site broke. I’ve attached the error here.
Comment #5
a.dmitriiev commented@sandeep_k you need to clear the caches, as one more argument was added to service definition.
Comment #6
abarrioReviewed unsing simplytest.me and local env with Drupal version 10.5.4 and still able to delete entities.
Comment #7
abarrioAfter digging into the problem, I discovered that the affected roles that are allowed to continue deleting content with the old approach are those that are admins.
I created a new approach to overwrite the default entity access control to check if the site is in read-only mode and, if not, call the original handler.
Comment #8
abarrioPatch upload to use in a project.
Comment #10
astonvictor commentedworks for me. tested with different entity types including users, nodes, eck.
Also, configured gitlab ci, fixed di, and updated tests.
Comment #11
sharique commentedThere is a merge conflict, please rebase and resolve conflict.
Comment #12
sharique commentedComment #14
astonvictor commented