wohnhirsch

Morning,

seems to work again – thx!

cheers,
Markus

• This reply was modified 5 years, 5 months ago by wohnhirsch.

Morning Stanley,

just tried on my dev site – no change, CCSS is still not available.
I still see:

Failed to post via WordPress: Our Critical CSS server is under heavy memory load and cannot process your request. Please try again later.

cheers,
Markus

any update on that matter?

as it seems I have the same issue. last time critical css was generated was on the 4th of June.
since ever then nothing happens anymore and when i try tu run the queue manually

i get this message:
Failed to post via WordPress: Our Critical CSS server is under heavy memory load and cannot process your request. Please try again later.

cheers,
Markus

• This reply was modified 5 years, 5 months ago by wohnhirsch.

yes i did

actually after the latest update i now was able to destroy all and redo the optimization.

apart from a few hickups it seems to work fine now – in the media library the litespeed column has gone missing ? but as long as the output is what I want I don’t care so all is fine.

and that one i find interesting after destroy all : Images previously optimized: 546 groups (634 images)

cheers,
Markus

i hope you bring it back soon !
cause i tried to destroy optimized images but nothing happens, no credit reset nothing. and therefore i obviously can’t start to re-optimize.

So for now it seems that my only chance is to wait for your refactored image module.

cheers,
Markus

Ok,

thx for the update – in this case i’ll have to redo the entire media library – pity there ain’t no rescan function ??

anyway case closed!

cheers,
markus

hi,

no i had to choose replace and update file and links

cheers,
markus

Hi,

I replaced the images with the Enable Media Replace plugin, for the thumbnails i used Regenerate Thumbnails. for the rest of the issues i used Fix Media Library plus that i had to copy some “lost” images back manually.

now my media library shows for a good part of the images no optimization by litespeed however lscwp shows all done ?

the in your documentation i read about that Send new Thumbnail requests but as said I just cant find that button ..

any other ideas on how to motivate lscwp to rescan the DB are welcome

cheers,
Markus

Hi Lisa,

the images have always been there and no i did not yet enable the debug log.
today i upgraded the plugin once again, disabled WebP and Lazyload to start with.

currently it looks good but i’ll have to check first from other devices too.

cheers,
Markus

Ok – looks like latest update fixed the issue!

thx

Hi,

you guys found any solution yet cause I have exactly the same issues on plaettlimaxx.ch:

Failed to push to LiteSpeed server: Too many errors when try to fetch image source files from your previous request, please contact LiteSpeed.

on wohnhirsch.ch get messages like this:
SAPI Error cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received

and so on: any suggestions?

@mymail748, @bentanner,

In my case i figured that just saving alone will fix the issue without any additional steps.
This however is no fun when having multiple / many products with variations as one would have to open & save each of them.

I found that article too – just this function never was activated on my site : so that won’t fix the issues ??

I much more think that WordPress SEO does not like Visual Composer some how, since only when the two together are activated, woocommerce starts to screw.

@ ddgarton – more or less exact same issue as you describe. Additional in some cases it even tries to change the permalink of the product.
In my case its so that I either deactivate Visual composer (which is no good idea on a live site) or deactivate WordPress SEO Premium – took i while till I figured that WordPress SEO Premium is causing all the trouble.

Hope for a fix is coming soon

Update – looks like Visual Composer is causing the issue(at least for some Part). If I hit edit on published products – exactly the same thing happens until i switch of VC. Did not see that happening before Wp 4.2.2.