Errors appear at top of page?

[scottsgameroom]

Hi i am currently runnig version 1.0 on http://www.swanagestrokeclub.co.uk

The site was going fine until i finished editing a page and since then the following message has been appearing at the top of the page.

Warning: fopen(/home/swanages/public_html/tmp/cache/contentcache.php) [function.fopen]: failed to open stream: Permission denied in /home/swanages/public_html/lib/classes/class.contentoperations.inc.php on line 557

Warning: fwrite(): supplied argument is not a valid stream resource in /home/swanages/public_html/lib/classes/class.contentoperations.inc.php on line 558

Warning: fclose(): supplied argument is not a valid stream resource in /home/swanages/public_html/lib/classes/class.contentoperations.inc.php on line 559

How can i correct this error?

[aota-perez]

Hello !

I have the same problem !

[websjapan]

hey there

i believe this is related to my post about the cpanel patch recently issued. if you try changing the file permissions it may work - did for me, but now i can add content but can see it on the web!!!!

[scottsgameroom]

Does any one actually have any idea how to fix this issue!

I have been waiting for a long time and my client wants the message got rid of!

Any ideas what file permissions need to be changed?

[Dee]

Does any one actually have any idea how to fix this issue!

The warning indicates that the webserver can't write to the file tmp/cache/contentcache.php (Permission denied). Make sure the webserver has write persmissions on tmp/cache (and it's contents).

[calguy1000]

actually, check the permissions on all files and directories below, and including tmp.

[scottsgameroom]

Have checked and played around with the permissions for temp and i am still recieving the error?

Is there anything esle that it could be or should i try an upgrade to 1.02 and see if this helps?

[Dee]

Have checked and played around with the permissions for temp and i am still recieving the error?

Is there anything esle that it could be or should i try an upgrade to 1.02 and see if this helps?

I don't think an upgrade to 1.0.2 will help as this is clearly a permission issue. The webserver must be able to write to tmp/cache/contentcache.php in 1.0.2 also (you won't get those messages if it can, the easiest way to achieve this is to delete tmp/cache/contentcache and make tmp/cache world writable).