usabe

@adrianb

I think I know what you mean. Basically after every like purge action there will be the administrator notification. Currently we are not providing such specific settings due to the development priorities. But maybe you can find some wp settings or some plugins for this purpose?

Mark as resolved. Moved to litespeed internal ticket system.

mark as resolved due to inactivity : )

Hi @andreag007

In the past we once had some problem like this. Didn’t remember exactly but it seems like related to some plugin called WP Asset Cleaning (or something like that) which will duplicate the ESI blocks. If you are also using it then you can try to disable it first to see. You may need to tune its settings once verifying this.

@rudolfl This is kind of interesting. Please open a ticket by emailing to [email protected] with further details. Remember to reference this topic and ask to assign your ticket to Abe.?

Yes, this type of issue normally comes from css or more specifically ucss if in use. User needs to find out the corresponding css rules and add them to the UCSS Allow list. You may refer to this: https://docs.litespeedtech.com/lscache/lscwp/ts-optimize/#incomplete-ucss

Due to inactivity of this topic, mark it as resolved

@mattthomas-photography

Could you please provide more information how you experienced WP Rocket’s database clean up function to achieve this? Theoretically we may be able to do such thing, but different plugin had different design philosophies and priorities based on their majority user needs : )

@joy0114 @serpentdriver Thanks for your input and the help on this issue.

@thejojk This type of issue is not quite generic for us at this moment. We don’t often hear about polylang from our users in the past. So if it’s a compatibility issue, please open a ticket by emailing to [email protected] with further details. Likely our team member needs to access your site admin to investigate on this.

Hi @popseries

Just checked your live site. From the header it seems the cache is not setup right. Instead of getting x-litespeed-cache hit or miss header, we got “x-litespeed-cache-control: no-cache” for the homepage. You may need to check from this direction to solve the “initial server response time” problem.

Hi @aljuk

We got several such reports from the forum but our team internally haven’t been able to reproduce it yet. Coud you please open a ticket by emailing to [email protected] with further details? Remember to reference this topic and ask to assign your ticket to Abe.?

Hi @petehawk

If the Advanced presets gives you the problem, then maybe you can try starting from the Essentials presets. This will isolate the problem further and you will know which option may have caused this problem.

Looks like something got stuck in the database. Could you please open a ticket by emailing to [email protected] with further details? Remember to reference this topic and ask to assign your ticket to Abe.?

Hi @umbrellaweb

Could you please create a ticket with litespeed by emailing to [email protected]?with further details? This type of compatibility issue normally requires closer working together with the user to figure them out.

This looks like a quite site specific case. You’d better create a ticket in litespeed by email to [email protected] with further details. We may need to check into your site admin to investigate.

• This reply was modified 1 year, 10 months ago by usabe.