I have exactly the same problem – cant work out how to get rid of the error.
HungryFEED is showing errors that are happening in SimplePie that are safe to ignore, but I’ll need to figure out how to hide them without hiding actually important errors.
For the moment you can go to HungryFEED settings page and there is a template for the error message. You can change that to something like this:
<!-- {{error}} -->
Then the error message will be hidden in the comments of the HTML. If you do that just be aware that you won’t see error messages anymore unless you look at the page source.
Ok, the error at 1780 is due to the cache file not being writable. I’m releasing an update to display that error better in the next few minutes.
Thanks so much for looking after this
Same issue here!!
Error Processing Feed: /home/wish710/public_html/it/wp-content/cache/6d0dd919daf5a814652041f4a640ec02.spc is not writeable at /home/wish710/public_html/it/wp-includes/class-simplepie.php line 1780
I have hungryfeed installed in two blog en/it version of the same domain…
http:// http://www.artphotoasia.net/blog
http:// http://www.artphotoasia.net/it
set two different wp installation.
In one installation no problem at all in the other one got the error.
it generally will be a permission error with the cache folder where you need to allow the web server write permission to the cache folder
Had the same problem, found an easy solution:
Step 1: Create an empty folder in /wp-content/ called /wp-content/cache/
Step 2: Set permissions to /wp-content/cache/ to 755 or 777
Step 3: Open /wp.config.php and insert the following code anywhere below existing definitions.
define(‘ENABLE_CACHE’, TRUE);
The error message goes away and the feed is good to go. Awesome plugin, thanks.
thanks for the post, i’ll add that to the FAQ
Hi there and thanks for the help… for now I have disabled the error message, I want underline that if you modify wp.config.php you have to modify it each time WP will update….
To be totally accurate it’s actually wp-config.php (not wp.config.php)
But when you update WordPress wp-config.php is not overwritten. If it was then you’d have to re-enter your database settings and all that stuff every time. Unless you are blowing away your entire WordPress folder, you don’t lose your settings in wp-config.php.
Hi guys……
I made that cache folder and all is fine!
Thank you.
I just used lonestarseo’s method after migrating an existing WP installation to a new host and it worked perfectly. Thanks.
I wanted to clarify the instructions for step 1 just a bit:
Step 1: Create an empty folder inside /wp-content/ called /cache/ (i.e., not a new folder called in wp-content called /wp-content/cache/
Hope this helps. Thanks verysimple for a great plugin… and thanks lonstarseo for a great answer to this issue.
