While publishing a content (Alert that uses scheduler to publish its content) manually using Views bulk operation I am encountering an strange behavior.

When I selects a single or multiple Alerts to publish (Publish time has been passed ) the first Alert is not getting the right access permission in node_access table i.e.

select * from node_access where nid= 11713;
+-------+-----+-------------------+------------+--------------+--------------+
| nid   | gid | realm             | grant_view | grant_update | grant_delete |
+-------+-----+-------------------+------------+--------------+--------------+
| 11713 | 990 | nodeaccess_author |          1 |            0 |            0 |
+-------+-----+-------------------+------------+--------------+--------------+

due to that after content published successfully message, when I am opening the published node from any user other then author and admin, it is showing "You are not authorized to access this page.". But once I rebuild all the permission node_access table is filled with right permission as following

select * from node_access where nid= 11713;
+-------+-----+-------------------+------------+--------------+--------------+
| nid   | gid | realm             | grant_view | grant_update | grant_delete |
+-------+-----+-------------------+------------+--------------+--------------+
| 11712 |   1 | nodeaccess_rid    |          1 |            0 |            0 |
| 11712 |   2 | nodeaccess_rid    |          1 |            0 |            0 |
| 11712 |   3 | nodeaccess_rid    |          1 |            0 |            0 |
| 11712 |   4 | nodeaccess_rid    |          1 |            1 |            1 |
| 11712 |   5 | nodeaccess_rid    |          1 |            0 |            0 |
| 11712 |   6 | nodeaccess_rid    |          1 |            1 |            1 |
| 11712 | 990 | nodeaccess_author |          1 |            0 |            0 |
+-------+-----+-------------------+------------+--------------+--------------+

and all authorized users are now able to access this node.

This issue is only happening when node is published as bulk operation and only for first selected item. Otherwise if page is published automatically by Cron run or it is in any position other then 1st in the list of bulk operation then its access permission are setting correctly and everything is working fine.

Comments

rajeevnith’s picture

Issue summary: View changes
jonathan1055’s picture

Hi,
Can you edit your post, to wrap the two table prints in <pre> or<code> tags so that the column headers line up and it is easier to read?
Thanks

jonathan1055’s picture

Issue summary: View changes
Priority: Major » Normal
Status: Active » Closed (works as designed)

The second select is not showing the nid as given in the example (11712 not 11713), so it is hard to see what is actually going on.

It does not sound like a scheduler bug anyway, as no scheduler functionality interacts with node access. Closing this as it is more than one year with no response from the user. You are welcome to re-open if you have more info and this is still a problem.