L_VanDamme → created an issue.
I updated the MR to stop using RouteMatch parameters or request attributes as they are not reliable. Instead, we should use the Route defaults as we can be 100% sure they will be present and correct (as we set them ourselves).
This is needed because we have noticed very rare edge cases where the page entity could not be found in the RouteMatch parameters or request attributes. In our case this was most easily reproduced right after logging in with users that have a certain role. I did not debug what was actually causing this in code.
L_VanDamme → created an issue.
L_VanDamme → created an issue.
I added some lines to the existing patch (the part of the access check) that load the page manager page entity if it is not loaded already. This seems to fix the access issues in our usecase (language switch links).
This does feel a lot like a bandaid for a bigger issue though, more investigation would be nice. Especially by someone more familiar with the routing system and the way parameters are being upcast to objects.
Reuploading patch as I missed the file deletions
Separate patch that applies to 1.0.1 (due to packaging information on info.yml)
I set up a MR with the new code (with some additions and improvements to my previous .zip file)
Uploading a patch I used for a project that implements the second possible solution (updating the database schema), because they specifically wanted to be able to use longer titles.
This patch was made on the 6.0.0-alpha38 version of this module, but should work on later versions as well.
L_VanDamme → created an issue.
L_VanDamme → created an issue.
Added a patch based on the open MR
L_VanDamme → created an issue.
Uploading a patch file based on the open MR
L_VanDamme → created an issue.
L_VanDamme → created an issue.
L_VanDamme → created an issue.
Released in 2.0.0
Released in 2.0.0
Released in 2.0.0
Released in 2.0.0
L_VanDamme → created an issue. See original summary → .