Hi Henk-Jan,
The actual permissions are a bit hard to predict because it depends on as which (system) user your webserver is running. Try working your way up from 755 to see when it starts to work.
If it’s still not working with permissions 777 on the file recent-facebook-posts.cache, let me know please.
Good luck!
Danny
Hi Danny, thanks for your swift reply!
Hmmm. Unfortunately, that did not do the trick – even w/ 777
Regards, Henk
Hi Henk.
Strange, are you sure the filename is recent-facebook-posts.cache, and has no hidden extension or something? What about (temporarily) setting the wp-content permissions to 755 (non-recursive) so the plugin can create the file for you?
Hi Danny,
The wp-content folder itself was already set to 755 (per default).
I deleted the recent-facebook-posts.cache file and (temporarily) set the wp-content folder to 777 (non-recursive). That did the the trick: the file was created (w/ 644) and the error message did no longer pop up.
However, setting the wp-content folder back to 755, triggered the error message again. Also, changing the permissions of the recent-facebook-posts.cache file to 755 triggered this error message:
550 CHMOD 755 recent-facebook-posts.cache: Operation not permitted
And, I don’t want to keep the wp-content folder set to 777.
Hi Henk,
Fixed this in the next update which will be available tomorrow morning!
Thanks a lot and looking forward to it!
Hi Henk,
Just pushed out version 1.7 where this can’t happen as I switched the caching mechanism to one of WP’s core functions. 🙂
Hope that helps!
Hi Danny. Thanks again – it works!
