First of all I just looked at the demo and boy has cms ms come a long way! Much better looking admin guys!
It's been a while since I updated (obviously).
I followed the steps with backups etc, all went well enough until I tried to login to admin.
If I use the wrong login details, it says so in red. If I use what I'm sure is the right login details, it doesn't say so, but it just won't let me in which may be because of the other thing that happens on the admin page...
This error appears below the login box:
Warning: Unknown(): open(/tmp/sess_7be3d75b4b9b15564d3db2943861e364, O_RDWR) failed: Permission denied (13) in Unknown on line 0
Warning: Unknown(): Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0
Any other info needed?
Thanks,
Brad.
Upgrade from 1.3 to 1.5.2 login weirdness
Re: Upgrade from 1.3 to 1.5.2 login weirdness
Looks like there the system saves the session cookie is write protected or not accessible for cmsms.Warning: Unknown(): open(/tmp/sess_7be3d75b4b9b15564d3db2943861e364, O_RDWR) failed: Permission denied (13) in Unknown on line 0
Warning: Unknown(): Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0
Look at your /tmp directory and verify its 0777 or at least 0775
ReneH 
A search will save you hours waiting for an answer!

A search will save you hours waiting for an answer!

Re: Upgrade from 1.3 to 1.5.2 login weirdness
Thanks but I'd tried that. Changed from 755 to 777 and still no dice.
Re: Upgrade from 1.3 to 1.5.2 login weirdness
Did you manualy try to clean the /tmp , /tmp/cache and /tmp/templates_c folders?
all index.html files and folders can stay. Else you can delete everything in there...
all index.html files and folders can stay. Else you can delete everything in there...
ReneH 
A search will save you hours waiting for an answer!

A search will save you hours waiting for an answer!

Re: Upgrade from 1.3 to 1.5.2 login weirdness
Thanks reneh - I just deleted the tmp again - re-uploaded - I'm in.
One question: How come it doesn't look as glossy and gorgeous as the demo here? http://www.opensourcecms.com/cms/cmsmad ... admin.html
One question: How come it doesn't look as glossy and gorgeous as the demo here? http://www.opensourcecms.com/cms/cmsmad ... admin.html
Re: Upgrade from 1.3 to 1.5.2 login weirdness
Now everything was sailing along fine until I tried to edit a page.
Thats when I got the following on all pages (not in admin):
Warning: fopen(/home/neurovis/public_html/tmp/cache/contentcache.php) [function.fopen]: failed to open stream: Permission denied in /home/neurovis/public_html/lib/classes/class.contentoperations.inc.php on line 556
Warning: fwrite(): supplied argument is not a valid stream resource in /home/neurovis/public_html/lib/classes/class.contentoperations.inc.php on line 557
Warning: fclose(): supplied argument is not a valid stream resource in /home/neurovis/public_html/lib/classes/class.contentoperations.inc.php on line 558
EG here: http://neurovision.com.au/portfolio.htm
Anyone?
Thanks.
Thats when I got the following on all pages (not in admin):
Warning: fopen(/home/neurovis/public_html/tmp/cache/contentcache.php) [function.fopen]: failed to open stream: Permission denied in /home/neurovis/public_html/lib/classes/class.contentoperations.inc.php on line 556
Warning: fwrite(): supplied argument is not a valid stream resource in /home/neurovis/public_html/lib/classes/class.contentoperations.inc.php on line 557
Warning: fclose(): supplied argument is not a valid stream resource in /home/neurovis/public_html/lib/classes/class.contentoperations.inc.php on line 558
EG here: http://neurovision.com.au/portfolio.htm
Anyone?

Thanks.
Re: Upgrade from 1.3 to 1.5.2 login weirdness
Hello,
1.5.2 => System Info please.
Have you talked with your hosting provider ? Security policy too hard ?
Pierre M.
1.5.2 => System Info please.
Is there something corresponding to this in your logS ? Is this the error.log ?herbshirt wrote: Warning: fopen... [function.fopen]: failed ...: Permission denied in ... on line 556
Have you talked with your hosting provider ? Security policy too hard ?
Pierre M.