Support » Plugin: RSS Aggregator by Feedzy - Powerful WP Autoblogging and News Aggregator » Warning: ./cache is not writeable Error

  • Resolved albie2011

    (@albie2011)


    Plugin working great but getting error at the top of the page that says:

    Warning: ./cache is not writeable. Make sure you’ve set the correct relative or absolute path, and that the location is server-writable. in /usr/www/users/albish/IHB.com/wordpress/wp-includes/class-simplepie.php on line 1404

    I’m not a techie but looked into line 1404 and that just says to show an error. I found other references to this including with regard to another plugin but am not sure where to implement a fix https://w3guy.com/fix-simplepies-warning-cache-writeable/

    Any help would be appreciated as it is a great little plugin.

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 16 total)
  • Thread Starter albie2011

    (@albie2011)

    This was resolved, it turns out the error display was showing on theme generally.

    I have the same error. The cache is not writable. The w3guys answer is not clear about where or how to put the code. I tried various places and combinations and removing the plugin was the only thing I found that resolved the issue. Will someone please help clarify the resolution? I really like this plugin and would like to stay with it.

    THIS IS JUST ONE OF THE ERRORS

    Warning: ./cache is not writeable. Make sure you’ve set the correct relative or absolute path, and that the location is server-writable. in /home4/eandgter/public_html/autoareanews/wp-includes/class-simplepie.php on line 1404
    Array ( [0] => http://news.google.com/news/rss/local/section/geo/Denver [1] => %20CO [2] => %20United%20States/Denver [3] => %20Colorado?ned=us&hl=en&gl=US )

    Thread Starter albie2011

    (@albie2011)

    Hello @rohittm can you clarify this situation? The instructions are to modify the theme to not show the error. But does this mean that the plugin’s caching functionality is working? Or is hiding the error just doing that, hiding the error visually but the plugin is not caching? We hid the error and that worked visually but one day had a lot of traffic to the page and it caused our server to crash. So, we believe that the plugin is actually pulling the feed with each page load instead of caching, which is what the error seems like it is indicating. Any clarification on your part would be appreciated. We submitted this through premium support and we were told to go to our host to attempt to resolve the issue which to me seems to indicate that there is an issue with non-caching. Thanks in advance for any clarification.

    Thread Starter albie2011

    (@albie2011)

    @rohittm Does this webpage shed any light on the issue? In searching Google it seems that others have had the trouble with SimplePie and the cache location – this person seems to be saying that he figured out how to define the location so that SimplePie would be able to deposit the cache so that the caching works:

    https://w3guy.com/fix-simplepies-warning-cache-writeable/

    In my WordPress installation, I have a folder /wp-content/cache/ that is used by other plugins to hold their cache. Maybe this is where the plugin should also be putting its cache?

    Thread Starter albie2011

    (@albie2011)

    @rohittm @uriahs-victor – not having any luck with my host as they are unable to determine where Feedzy is trying to put the cache. (see earlier messages above). Check out this link:

    http://simplepie.org/wiki/faq/i_m_getting_cache_error_messages

    That makes it sound like SimplePie would in theory be trying to put that ./cache in the same directory of the page calling it (i.e. https://www.inhouseblog.com/general-counsel-jobs/) although they do make mention of a hook that could change it to place it elsewhere (i.e., wp-content/cache, where all the other plugins put it).

    Does this page help? Could a hook to point the cache to wp-content/cache do the trick?

    @albie2011 I believe we’ve solved this via our ticketing system, @tkaret please send us a ticket here so we can have a closer look at your setup: https://themeisle.com/contact/

    Thread Starter albie2011

    (@albie2011)

    Yes @uriahs-victor that is correct. Will the fix be rolled into the plugin the next time it is updated?

    Sarah

    (@sarahwhitelyaolcm)

    I’m getting the error message…really to bad as it is a pretty nice plug in…anyone having any luck with this?

    Sarah

    (@sarahwhitelyaolcm)

    just deleted it…gave up

    This fixed the issue for me!

    Editing file class-simplpie in wp-includes directory

    line #546

             /**
    	 * @var string Cache location (relative to executing script)
    	 * @see SimplePie::set_cache_location()
    	 * @access private
    	 */
    	public $cache_location = ABSPATH . WPINC . '/SimplePie/Cache/cache';

    And must create cache folder in wp-includes => SimplePie => cache manually on the server! it doesn’t created automatically, needs fix too!

    And line #870

    	/**
    	 * Set the file system location where the cached files should be stored
    	 *
    	 * @param string $location The file system location.
    	 */
    	public function set_cache_location($location = ABSPATH . WPINC . '/SimplePie/Cache/cache')
    	{
    		$this->cache_location = (string) $location;
    	}

    All changed from

    './cache'

    to

    ABSPATH . WPINC . '/SimplePie/Cache/cache'

    Checked and verified that cache folder contain md5 hashed cache file for rss feed in admin dashboard!

    I hope this help!

    • This reply was modified 3 years, 4 months ago by egycode.
    • This reply was modified 3 years, 4 months ago by egycode.

    egycode: you’re awesome!!

    Is it possible to add the solution as a snippet-code (I have a snippet code plugin) to prevent the class-simplepie.php file to be overwritten during upgrade? I’m not too savvy with PHP and behind-the-scenes editing with WordPress.

    @egycode:

    Thank you! It Works!

    Thanks @egycode

    Works for me. No more error message (although no files created in wp-includes/SimplePie/Cache/cache)

    I have the same error, but all of my feeds are showing.
    Warning: ./cache is not writeable. Make sure you’ve set the correct relative or absolute path, and that the location is server-writable. in /home/myhome/public_html/mysite.com/wp-includes/class-simplepie.php on line 1404

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘Warning: ./cache is not writeable Error’ is closed to new replies.