Was trying to get both field_permissions and content_access modules to work, and discovered this node_access business for the first time. I've realised that most modules dealing with this have used Drupal's role rid as the gid when writing access rules, which is logical because it maps roles to grants simply, but the gid column is INT. Backdrop no longer has a rid, so to get his to work, I've had to write a doubtful function which maps each role to an INT, stored in config. Not fun.
Can that column be changed to simply accept the role's name rather than a rid? What would be the implications of this?
GitHub Issue #:
1396
Recent comments
"why are these tags only relevant for admins?" I'm allowing the editor as well. That being said, Ruby Text can be a bit of a hassle to edit... easy to accidentally delete a tag or part of a...
Specific tags to work in CKEditor 5
Out of curiosity: why are these tags only relevant for admins? Don't "regular" editors on that site also need them under circumstances? Yes, the editors play nicely, no problem to...
Specific tags to work in CKEditor 5
Worked like a charm! Exactly what I envisioned... now I can edit the ruby text right in the editor, sweet:) Thank you! For those who may have a similar issue, try TinyMCE, create a new "text...
Specific tags to work in CKEditor 5