Permissions after upgrade

Tuesday 05 October 2010 5:04:48 am

Hi,

To see what is happening, you may activate the debug on the admin interface, or check the log files.

http://www.acidre.com

Wednesday 06 October 2010 8:46:49 pm

Thanks for the suggestions.

Jean-Luc, I have tried that, but there are no errors. The 'edit' icon for the items are simply all greyed out.

Marko, Yes, I cleared the cache both manually and via the 'rm' command. The folders do have the correct permissions (web server is owner and permissions are '775'). I upgraded stepwise using the (fairly confusing) documentation, from 3.8, 3 to 3.9.5, to 3.10.1, to 4.0.1, to 4.1.4, to 4.2.0. I have scripted it, and I don't have the option of stopping at each step. 3.10.1 is OK though.

Marko, I didn't regen the autoload arrays, but I'm not sure that that will affect anything to do with permissions to objects will it?

Thanks,

Cliff

Thursday 28 October 2010 9:33:50 pm

Has anyone any ideas? It looks like *all* users have lost permissions to nodes (is that the correct word?).

I can't understand what would cause a global loss of permissions like this. I've looked through the database updates between 4.0.7 and 4.2.0 and none seems likely. I've looked at all the other steps. I'm at a loss. The logs show nothing, I don't see anything significant when I turn debugging on on the pages. I'm completely confused.

Cheers,

Cliff

Saturday 06 November 2010 3:56:29 pm

The problem does not appear to be in my upgrade process as I used the 'ezupgrade' process to upgrade and the same problem still exists - content is uneditable. However, content *can* be created.