• So I do need further help with getting preload working!

    The site I’m working on has Divi 5, Woocommerce and Filter Everything as well as a few plugins that have never caused trouble before.

    Preload works fine with this configuration but the cache that is built includes files for every permutation of the category, tag (etc) options for the filter. So there will be thousands of cache files with prefix _category, _tag, _accessories etc. Preload very happily processed these over one night and I ended up with a GB of cache files with more to come.

    I used the exclusion rules to attempt to limit cache files associated with the filter, adding a number of rules to exclude if request_uri contains _category etc.

    But his just brings the whole preload process to a halt, and everything gets a bit crazy. I had a cron job set up to manually push the process along but this no longer works.

    I’d appreciate and tips or ideas about how to handle this.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Emre Vona

    (@emrevona)

    is Filter Everything a wordpress plugin? if so, can you tell me the plugin url plesae?

    Thread Starter richardjb62

    (@richardjb62)

    Yes it is both a free and premium wordpress plugin.

    https://ww.wp.xz.cn/plugins/filter-everything/

    I’ve got the pro version and have had some response from the plugin developers who have initially suggested using wildcards to exclude – which I had already explained that I had done!

    They also suggested something about turning off permalinks in their plugin using a custom function but this sort of broke the site. The crazy thing is that these cache files get created at an extraordinary rate, much faster than the usual preload rates suggested in your documentation.

    The format of the file name ends up something like…

    _category-valvetype-or-accessory-or-brand-or-color-or-country-of-origin etc

    I used an exclusion rule of *_category* (and three others similar) which seemed to stop preloading altogether.

    I also tried a different caching plugin and had similar problems so I suspect the filter developers could be taking a harder look at how their plugin is interacting with cache.

    Regardless, if there are any suggestions to just get WPFC to ignore these I’d be grateful!

    Cheers

    Plugin Author Emre Vona

    (@emrevona)

    I will check it and let you know.

    Thread Starter richardjb62

    (@richardjb62)

    A bit more info…

    I’ve got WPFC set up to preload based on sitemaps. Two sitemaps specified, one for pages(about 7) and one for products.

    Regardless of this, the filter (Filter Everything) on the shop page is resulting in thousands of cache files being generated. I can see these in a folder on the server for the shop page. Despite the preload being set to 4 per minute, I can also see that up to 10 sets of cache files are being created every minute.

    An example of what I’m seeing is /shop/category-amp-components-or-matched-pairs-or-rectifier-or-valve-sockets-and-adaptors/.

    Is there a way I write an exclusion rule that allows /shop/ to be cached but nothing else further under this page? If not I’ll just have to exclude the shop page from being cached

    Plugin Author Emre Vona

    (@emrevona)

    I could not replicate the issue. Can you show me a sample filter please?

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.