i recently upgraded to 5.3 and then to 5.5.

i found out later that posts by users without admin roles are not updated into the node_access tables. this means they cannot view their own posts.

appreciate the assistance here.

i am running a multi-site setup with shared user, sequence and sessions tables. the problem only seems to occur only on one of the sites and not on the others.

Comments

TheFazz’s picture

TheFazz commented
Priority: Normal » Critical

i did a manual fix to the node_access table by doing the following:

INSERT INTO `node_access` VALUES(0, 0, 'all', 1, 0, 0);

by doing this, the nodes added could then be viewed even though drupal was not adding to the node_access list*.

* drupal does not add to the node_access tables if a user posts content. without the above 0,0,'all',1,0,0 entry in the table, those users will not be able to view their posts. but this surely is not the right fix. i am changing this issue to critical.

TheFazz’s picture

TheFazz commented

is anybody working on this?

TheFazz’s picture

TheFazz commented

any update on this as i am having problems with the node access and having to give everyone wider access than needed. what modules alters data in the node_access tables?

nsk’s picture

nsk commented
Status: Active » Postponed (maintainer needs more info)

Are you sure you chose the right db version (or left the default) in the drupal update script while you were upgrading to 5.5?

Doesn't sound like a bug report, it probably is specific to your site.

If I want to reproduce this, what should I do? Do you use clean Drupal install or do you use custom modules?

TheFazz’s picture

TheFazz commented

if by right db version, you mean "did i update the mysql db?"... i did. i ran the update.php soon after updating.

i believe this has something to do with the og. without og, the node_access needs only one entry.

in my case, when i activate the og module, the node_access tables stops working for new nodes being created. existing nodes are automatically given the proper node_access settings, but not new ones..

i am not sure what else to do to recreate this.

jscoble’s picture

jscoble commented

Thanks TheFazz for providing the solution. I had been unable to figure out a resolution before you provided the 0 row solution, which I should have thought of.

I was have the same issue with multiple installs. I hadn't noticed it when I was developing the sites until I started adding content so I can't say exactly what precipitated the issue. It is not related to OG because I am not using the OG module. I was using node_privacy_byrole, but I uninstalled it thinking that may be the problem.

I will set up a some test sites using 5.3 tomorrow and upgrade them to 5.5 and 5.6 to see if the problem is with the upgrade to 5.5 or if it lies elsewhere.

Trying to run down this issue also lead to showing the limitations of the devel module, but those are for a different post and a different issue queue.

jscoble’s picture

jscoble commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

I created two test sites using Drupal 5.3. I then upgraded each of the sites, one to 5.5 and the other to 5.6 and the 0 row remained on the node_access table so this is not the cause of the reported issue.

The reported issue is actually related to node access control implemented by other modules. They remove the 0 row from the node_access table because the existence of that row would cause node access rules to be ignored. To test this, I enabled the node_access_byrole module and checked the node_access table. The 0 row was deleted from the table by the module install.

I'm not sure what the source of your issue was TheFazz, but it was not caused by the upgrade. I would check the modules you are using and see which one removes the 0 row from the node_access table and raise the issue with that module.

Since it is not related to upgrading Drupal, I changed the status to closed.

thumb’s picture

thumb commented

TheFazz, thanks for posting this! This fixed the sam issue for me too. I had installed, but then uninstalled OG awhile back. I've also been experimenting with case_tracker. I'd be happy to provide a few more of the modules I've installed, if you'd like to try to come up with some sort of correlation.

ennetws’s picture

ennetws commented

Awesome!

Worked perfectly. Thanks a lot.

alicia’s picture

alicia commented

I used TheFazz's insert query to "fix" the problem I was also having, which I believe is related to og_access...seems like you should be able to use other modules in drupal without a non-core module messing up the drupal core modules...