Purge Home and Categories Page Cache only on post update

apologize for the inconvenience , there is some issue with schedule publish in v5.3 , we are working on it.

Hello @qtwrk,

sorry to intrude here, but I’m suffering the same issue that @khzeshan9 reported. Since 5.3, automatic purge on post publishing doesn’t work anymore. I have to manually purge cache after each published post, otherwise homepage (local news website) shows stale content (doesn’t show last posts). Either that or by manually refreshing posts one by one. Do you have an ETA on this? I’m on a LSWS Enterprise server, CentOS 7.

Thanks!

Could you please try edit file src/purge.cls.php by follow this ?

red menas deleted or be replaced , green means newly added/replaced

see if this helps

Hello @qtwrk,

I’ve tried performing the suggested changes but I’m a bit confused: I don’t have lines 83>86 (which are flagged red/remove). I’ve replaced if ( defined( 'LITESPEED_DID_send_headers' ) || apply_filters( 'litespeed_delay_purge', false ) ) { with if ( defined( 'DOING_CRON' ) || defined( 'LITESPEED_DID_send_headers' ) || apply_filters( 'litespeed_delay_purge', false ) ) {but it throws a critical error. What am I doing wrong?

please try toolbox -> beta test -> copy paste this link https://github.com/litespeedtech/lscache_wp/commit/cc231479bdf3c36712267a82898737fc2fe9a646

then upgrade

use this way it will fetch the files directly , so you don’t have manually edit it

Thanks @qtwrk, I just upgraded, I’ll keep you posted.

Michael

Hello @qtwrk,

I’ve monitored the website for the past 5 days, and I’m sorry to say that something isn’t still working as it should. To be more specific, I’m having random autopurge related issues with programmed posts: sometimes a published post is immediately visible, other times it becomes visible only after a manual purge or an edit. This happens randomly, but it looks like it only affects mobile views. I don’t have mobile cache option active, though. I’m currently using an external cron service (EasyCron), which I tried to deactivate to see if it changes anything, to no avail. I have now reactivated it and disabled wp cron from wp-config. Not sure which further info may prove useful, so in case just ask me.

Thanks,
Michael

please use toolbox -> beta test -> click “dev” , upgrade , and try again

there were some other commits were made in past few days

Ok, just did that. Should I also reboot server/lsws after that or is it useless?

no , no need to reboot/restart anything

Hello @qtwrk,

I’m afraid the bug is still present. I’ve been regularly pulling latest github versions as they became available, but the scheduling purge isn’t working as of now. Any update on this?

Hi @michael-travan

Due to inactivity of this topic, I will mark this topic as “resolved”. If you still have such issues (it looks so), please feel free to open a ticket with further information by emailing to [email protected]. Remember to reference this topic and?ask to assign your ticket to?Abe.?I will check into this further from there.