Permissions after upgrade

Next topic

Author	Message
cliffp pratt	Monday 04 October 2010 9:19:41 pm I've upgraded a site from 3.8 stepwise as recommended by the documentation. All now appears OK, but no one, not even the admin user has permissions to documents and folders! Has anyone any idea where I can start looking for the solution to this please? Cheers, Cliff
Jean-Luc Nguyen	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
Marko Žmak	Wednesday 06 October 2010 5:00:16 am And some basic things: - did you clear the cache after upgrade? - did you regenerate the autoload arrays after upgrade? - do your folders have appropriate filesystem permissions? And how did you do the upgrade? When upgrading from 3.8 you have to split upgrades into several steps. My suggestion is: - upgrade it to the latest 3.9 and test it - upgrade it to 3.10.1 and test it - upgrade it to the latest 4.0, switch PHP version and test it - continue the upgrade steps to the latest 4.x version -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth
cliffp pratt	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
Quoc Huy Nguyen Dinh	Thursday 07 October 2010 6:16:08 am I'm not sure but if you don't regen the autoloads some classes that have been added since 3.8 till 4.2.0 won't be loaded. So you need to regen the extensions and kernel arrays. And clear all caches again. I usually clear cache with ezcache.php --clear-all and with additionnally rm cli if the first doesn't work.
cliffp pratt	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
cliffp pratt	Monday 01 November 2010 2:41:52 am It now appears that it is something in the upgrade from 4.0.7 to 4.1.4. Has anyone got any ideas? I've repeated the upgrade multiple times and when I go from 4.0.7 to 4.1.4 all permissions appear to be lost. Authentication seems OK, as I can login and logout. Cheers, Cliff
cliffp pratt	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.