rudolfl

I was advised to exclude the file from lazyload as this affects how image is processed. Playing with it at the moment. I think, it is working, but only tried one scenario. Will need to run more tests

Lazyload is only enabled in optimole for CSS background. Theme has lazyload disabled.

If I run page with ?LSCWP_CTRL=before_optm, everything loads up OK.

Report ID is EIQKWEPX in case you need one

Rudolf

Are you sure?

Purge control is set to off when WP or plugin is upgraded, but every time LS Cache plugin is upgraded, I get a popup bar from LS Cache saying all QuickColud caches were successfully cleaned. I will try to record a video when I do upgrade next time

Rudolf

Thank for replying.

The problem is that LiteSpeed plugin was also upgraded which, for some reason, always results in automatic clearing of all caches (that is super annoying in itself!). So, any credits I would apply now will be immediately put toward the re-generating cache of all pages and will be wasted

Rudolf

Hi,

Any timeframe on the fix? It is a quiet time for us, so I am upgrading themes/cores. etc.. on all sites and it will require UCSS re-generation

Thanks

Thank you,

Looks ok at the moment, but will keep an eye on it as cache builds up.

Any reason HTML minify can behave in this way? I pretty much duplicated LiteSpeed settings across all of my sites and only one exhibit the problem.

UCSS does NOT work out of the box! It requires extensive tweaking.

It simply can not detect all the CSS you need.

I spent hours fixing pages (link to the quite is posted in previous reply), but it certainly worth the result. Page speed improves dramatically!

I actually came to this forum to ask same question. My feed has same problem.

I adjusted the batch size and, looks like, it is fixed

Rudolf

My apologies for late reply — I, for some reason, not getting notifications on relies to this thread.

Thank you for replying.

In the last week I had no issues and nothing was changed in our system. As a precaution, I now disabled the plugin in question just in case. Will monitor and see.

I am currently unable to do any upgrades due to high season in our store. All upgrades will be applied in Nov, as load easies.

Rudolf

My apologies,

Here it is:

https://pastebin.com/SUumFbLh

Thanks

Hi,

Thank you for replying.

I did search for “fatal errors” logs and yes, found it!

Here it is:

[ Here it’s deleted ]

• This reply was modified 1 year, 6 months ago by Jan Dembowski.

Dough!

Me and my lousy fingers… Fixed, testing now

Rudolf

Thank you,

I was not sure if Fruugo in different countries have different requirements, so, being a geek, I modified plugin code to change case in relevant places. Waiting for Fruugo to check the feed at the moment.

Once they are done, I will switch to other country to keep codebase intact.

Rudolf

Just to add — I was looking at the code and it appears that code is NOT processing Fruugo Australia. Only Fruugo UK and NL are taken care of, Australian one is left to defaults.

I am using Fruugo Australia

Rudolf

You have to go through the code and add missing classes to the “UCSS Selector Allowlist” in options (Page Optimization->Tuning CSS)

It is a tedious process and a pain in the backside, but you do it once and then everything works fine.

https://docs.litespeedtech.com/lscache/lscwp/ts-optimize/