Skip to content
Snippets Groups Projects
Commit 8f1c5372 authored by catch's avatar catch
Browse files

Issue #2910181 by sarvjeetsingh, anmolgoyal74, apaderno, pameeela, jcalais:...

Issue #2910181 by sarvjeetsingh, anmolgoyal74, apaderno, pameeela, jcalais: Update hook_node_grants docs to remove role ID reference, since it is no longer an integer

(cherry picked from commit 8d2e4880)
parent 04f2121f
No related branches found
No related tags found
6 merge requests!8506Draft: Issue #3456536 by ibrahim tameme,!5646Issue #3350972 by nod_: [random test failure]...,!5600Issue #3350972 by nod_: [random test failure]...,!5343Issue #3305066 by quietone, Rename RedirectLeadingSlashesSubscriber,!3603#ISSUE 3346218 Add a different message on edit comment,!3555Issue #2473873: Views entity operations lack cacheability support, resulting in incorrect dropbuttons
......@@ -22,11 +22,8 @@
* "realms". In hook_node_access_records(), the realms and grant IDs are
* associated with permission to view, edit, and delete individual nodes.
*
* The realms and grant IDs can be arbitrarily defined by your node access
* module; it is common to use role IDs as grant IDs, but that is not required.
* Your module could instead maintain its own list of users, where each list has
* an ID. In that case, the return value of this hook would be an array of the
* list IDs that this user is a member of.
* Grant IDs can be arbitrarily defined by a node access module using a list of
* integer IDs associated with users.
*
* A node access module may implement as many realms as necessary to properly
* define the access privileges for the nodes. Note that the system makes no
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment