• My website was not monitored for a month and the cache grew excessively that my provider had contacted me.

    450GB cache on a small webshop with 50 products. 3Mil files.

    I couldn’t even delete the cache as WP FP was stalling and I had to completely uninstall it.

    I do have dozens of product tags which might contribute to many combinations of catalog pages. How can I limit the cache?

Viewing 7 replies - 16 through 22 (of 22 total)
  • Plugin Author Emre Vona

    (@emrevona)

    Please let me know.

    I am having the same problem with 2 of our websites. One has a 273GB cache and the other a 174GB cache. For the past few months I’ve been able to just delete them every few weeks, but they seem to be filling up faster each time and this is becoming unmaintainable. Is there a solution to keep the problem from coming back?

    FYI, it’s not just an issue with the caches themselves not clearing, if you try to open up a cache file to inspect it the file paths are massively recursive.

    public_html/wp-content/cache/tmpWpfc/1718827076/category/galleries/category/news/category/news/category/… etc.

    I think something is recursively concatenating the file path until it gets so long that it overflows and can no longer be properly deleted which is why the tmp files are not deleting properly.

    • This reply was modified 2 months, 4 weeks ago by csidev. Reason: additional bug details

    I still have not been able to find the source of the problem, but at least I’ve been able to find a work-around that fixes it. NOTE: you will need FTP, cPanel, or comparable access to file management. Depending on your hosting environment, you may need to get your hosting company involved in the cleanup.

    Step 1: Using FTP or your file manager, go to /public_html/wp-content/cache/. If you see a folder called tmpWpfc, it means that your file system can not delete your temp cache files because the file path is too long.

    Step 2: Open up tmpWpfc and start digging down into the file structure of the pages. If you see that the folders start to follow a repeating pattern of names like /category/news/category/page/4/news/category… etc. then you are experiencing this bug.

    Logically, you should just be able to turn off Preloading so that only good pages get indexed… but this also does not work. As soon as you enable the caching system at all, the bad temp files start to generate.

    Step 3: Find a part of the repeating pattern that is big enough to not exclude any pages that matter to you like “/category/news/category/”. Depending on the layout of your site, you may need to use multiple patterns to get everything.

    Step 4: Go to WP Fastest Cache Options > Exclude > Exclude Pages > Add New Rule.

    Step 5: Set If REQUEST_URI to “Contains” and paste your pattern into the text input. Then press Save.

    Step 6: Using FTP or your file manager, go back to /public_html/wp-content/cache/ and delete everything. Using the Clear Cache feature in WordPress will not delete the temp files that are burning up your disk space; so, this has to be done from the backend.

    Step 7: Wait a few seconds and then refresh your view on the folder. You should start to see folders like “all”, “wpfc-minified”, “wpfc-mobile-cache”, and “wpfc-widget-cache” start to general but you should not see “tmpWpfc”. If this is the case, you are done. If “tmpWpfc” still generates, then go back to step 2 and continue to look for additional recursion patterns and keep doing this until they are all blocked.

    Plugin Author Emre Vona

    (@emrevona)

    somehow cache is cleared too often and the problem occurs.
    https://www.wpfastestcache.com/tutorial/clear-cache-process/

    Do you publish articles very often?

    That should not be the case since they are both for low activity clients. The one with the?273GB cache only published about 50 articles since 2014, and the cache does not have any Timeout Rules set that would cause it to frequently regenerate. IIRC, I first started to notice the problem on one of the websites shortly after doing a theme replacement and the other website I think started to have issues when we upgraded the backend from PHP 7.4 to PHP 8.2. It’s hard to say exactly because it takes a while for these guys to fill up enough to start throwing warnings, and none of our other sites had the same problem from doing the same things.

    Oh, one thing both sites have in common is that they both use the theme Kallyas. We have at least 1 other Kallyas site that is not having this issue; so, I’m not 100% sure if its related, but it may be possible that it is a problem that this theme simply makes possible.

    • This reply was modified 2 months, 4 weeks ago by csidev.
    Plugin Author Emre Vona

    (@emrevona)

    any plugin can clear all cache via our hook system. you can disable the hook system of wp fastest cache.

    https://www.wpfastestcache.com/features/how-to-disable-clear-cache-hook-system/

    Thanks @csidev, I recently had this issue too and came to the same conclusion about adding a repeating URL pattern to the exclude pages setting. So far this seems to be working but I would also like to understand what is causing this. Perhaps it’s something to do with custom pagination code or custom permalink rewrites. If you ever find out the cause, please tag me. Thanks

Viewing 7 replies - 16 through 22 (of 22 total)
  • You must be logged in to reply to this topic.