Menu Content

Support

> Forums, FAQs & Paid Support
Welcome, Guest
Username Password: Remember me

"Warning cache...spc is not writeable.." error
(1 viewing) (1) Guest
Support forum for customers who have purchased paid JoomSEF extension. Archive only, no new post can be added.

NOTE: This category has been locked. If you have purchased paid version, please, use our Support Ticket system instead. If you are using free edition, please see the Community Support section.
  • Page:
  • 1

TOPIC: "Warning cache...spc is not writeable.." error

"Warning cache...spc is not writeable.." error 13 years, 10 months ago #20459

When I go to the JoomSEF Control panel page, I get these two error lines:

Warning: ./cache/84b083723ff96a2ba1e61ac2bb7bb7dd.spc is not writeable in /home/mysitename/public_html/libraries/simplepie/simplepie.php on line 1623

Warning: /home/mysitename/public_html/administrator/cache/84b083723ff96a2ba1e61ac2bb7bb7dd.spc is not writeable in /home/mysitename/public_html/libraries/simplepie/simplepie.php on line 1623

I'm not sure when this error first appeared, but it was fine for a long while, I think until I clicked on the option to upgrade one of the components (I should have tested first, silly me).

So not sure what to do.

Anyone recognise this error message?
The topic has been locked.

Re: "Warning cache...spc is not writeable.." error 13 years, 10 months ago #20460

Just to add, I have now also tried updating on my test site to v3.7.6 and I get a similar error but slightly different line number:

...libraries/simplepie/simplepie.php on line 1779

But when I install an old version from last year (something like v3.5.6) , it works fine without the error.

Thanks
The topic has been locked.

Re: "Warning cache...spc is not writeable.." error 13 years, 10 months ago #20461

OK I guess it was self explanatory really.

I went into my cpanel software, and reset the permissions on the administrator/cache folder to be read / write / execute for "User" and "Group" (rather than just "User").

Not sure exactly why that was needed but it worked!
The topic has been locked.
  • Page:
  • 1
User Login Empty