Hi,
We have tried to make our plugin compatible with the Redis Object caching a few times, unfortunately we did not succeed in doing so. As far as we know this won’t work but we’d love to hear from users who suggest otherwise ofcourse.
Bad news that is – how about cache groups, would that be a future possibility? Or are we too few using that type of cache? Would love to hear if anyone solved this.
Thanks,
Per
You should be able to sort this.
In the meantime, we will solve this by removing the object cache during low traffic hours and reinstate it again when traffic returns.
@labbapo11 and @supportadtribes I am running into the same issues.
I am testing Product Feed PRO for WooCommerce as we speak, and love it so far. So I am ready to buy, but also need to figure out how to deal with the Redis object cache. All these WP caching plugins don’t perform as well as server-based caching, so I’d like to stick with Redis.
Once I purge the object cache the feed is updated. So perhaps a cron job to purge the object cache before the feed will be generated will work.
We have tried this a couple of times and spend many development days on it, even had to roll-back some release of our plugin. We are sorry to say but we are not going to try this again.
@sandervdnd I agree that server caching is superior, so if @supportadtribes says they cannot fix it you need to roll your own mechanism, that is what we are doing right now.
Not sure if flushing the cache is enough but if you manage I would love to hear about it. We currently do a simple turn off cache->update feed->turn on cache. This during low traffic hours. Apparent drawback is of course that feeds are only updated once a day but we can live with that.
Understood @supportadtribes it’s a pity though because e-commerce websites cannot make good use of page caching, and are great candidates for a persistent object caching option such as Redis. Those are the same websites that likely need the feed to Google Merchant Centre and others. Anyhow, I do understand that you cannot support everything. Thanks for the prompt reply, appreciate that.
@labbapo11 I am using SpinupWP to deploy my servers. Hope that I can use WP-CLI with their implementation of Redis and a Cronjob to flush the object cache before the feed-gen kicks in. Since I focus on Europe only, I assume I can run this once a day at 3AM when there are likely no users active.
@supportadtribes is it possible to initiate an update from the command line or wp-cli?
This unfortunately is not possible.
@labbapo11
SpinupWP confimed to me that I can run a WP-CLI command to flush Redis.
wp cache flush
… and that I can schedule this via a cron job.
In the meantime I will test some other feed generators too. Perhaps they support Redis out of the box.
@supportadtribes I would like to set the time when a “once daily” update occurs. I assume the logic is “24hrs after last update”? So, if I enter a timestamp in the wp-options -> woosea_cron_hook db field that marks latest update, would the next update then occur 24hrs after?
@sandervdnd did you manage to work out a solution with wp-cli and flushdb?
The plugin won’t check when the last update was so that won’t work. It will just kick off an update just after 7 o’clock in the morning (local server time).
And where is “just after 7 o’clock in the morning” defined then?
On line 4290 of the main woocommerce-sea.php script.
To come back to your earlier question @labbapo11
I am working on a ton of things right now and have not had the time to create a cron job. I did however run the WP CLI command manually, waited 24 hours, and all seems fine. Products are added to the feed and to Google Merchant Centre.
Since my shop is in the making I am not sure what the performance impact will be for rebuilding the cache each time. What I do know is that Redis makes a massive difference. When disabled, page load times on average increase by a factor of 5.
I have not had the time to test other plugins and their behaviour with Redis / Object Caches.
