afonseca08

@brianmcculloh when is 1.6 going to be available? The plugin page still shows version 1.5 as the latest.

Thanks for letting me know. Hopefully the developer follows-up as I’m still looking for a fix.

I’m getting the same messages in my logs, any update on this?

Hi @qtwrk, I submitted a ticket but never heard back. Are you able to check on your side if it was received?

@qtwrk thank you, I just submitted a ticket.

@lclarke Thank you, I turned off lazy loading for the logo and it helps avoid that “pop” but I still see some ares of FOUC. Is there an e-mail or place I can send you some screenshots without posting here publicly?

@lclarke thank you for the prompt reply and troubleshooting link. I verified the CCSS was not being inserted as you pointed out. I then turned off Generate Critical CSS in Background and it is now being generated in the source. However, I still see FOUC when navigating between pages. Would you be able to take a second look?

Thanks!

Hi @lclarke, I am also having the same issue where I see what appears to be the nav menu appear as FOUC on the home page, service landing pages, and blog. I am using the Divi theme and have configured the LiteSpeed cache plugin to generate critical css as you described and verified there no pages listed in the queue for generation. Please take a look at report ATBTJJXR and let me know if I missed something.

Thank you!

I decided try it myself but only the backup feature for now. After resolving a minor issue with Google Storage bucket permissions I was able to get that part working.

However, I ran into an issue in that LiteSpeed’s image optimization feature allows for the output of webp images which I am using. This image format is not supported by wp-stateless so I’m going to have to disable it for now until support is added.

Just a quick follow-up, I added this required step to the manual setup instructions on the github wiki in case others run into this.

@bzadmin Thank you! This was the issue in my case as well and enabling the acl for objects fixed it. Now I see my images backed up to the bucket.

I agree, this type of error should be surfaced in the UI and written to a log file as currently this is failing silently.

Furthermore, I had already made the whole bucket public so I’m not sure why it needs object level permissions. However, if these are needed for the plugin to work as designed, then this step should be added to the manual setup instructions as it won’t work without this.

@gioni Yes, I had tried it both ways several times with the same http error result.

I’m just researching plugins for responsive images and this is also a feature I would need as I’m also using Divi. Is this supported or are there plans to add this?

Hi, I’m just checking to see if any progress has been made to figure out this issue? Also, is anyone else experiencing this? Maybe we can share more information to try and isolate this?

@gioni Sorry for the delay in getting back to your request. It’s been very intermittent for me to reproduce this so am not sure it has to do with the image itself. Here is what I discovered looking through the WP Cerber traffic inspector activity logs (note, I do have traffic inspection disabled).

https://mydomain.com/wp-admin/async-upload.php
GET?HTTP 404 Not Found?3701 ms?Details

Referrer
https://mydomain.com/wp-admin/post-new.php
User agent
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

This log was for one of the site’s administrators attempting to upload this image to a new blog post:
https://www.dropbox.com/s/vsa8toh1h11dj3b/Motivating%2520Yourself%2520for%2520the%2520NPTE.png

I then tried to upload the image myself logged in from my administrator account and the same result, time-out and http error fails to upload.

Disabling WP Cerber and uploading works as expected.

Any help would be greatly appreciated.