Search results

In https://github.com/litespeedtech/lscache_wp/commit/a3cb0f39ca8b06bc9e530a518fbb8a54eb6e35fe we added `get_option` cmd. Is that ok to use this cmd? Or if you want to get whole options, please let us know. Thanks.

Do you mean to retrieve a single value by CLI? Currently we don't have option. We can add it in v3.0 if needed.

Thanks for your feedback. We noted this and will see in future how to improve it.

Yes this is in our todo. Thanks for your suggestion. As this is related to LSCWP, for further discussion please visit https://wordpress.org/support/plugin/litespeed-cache/ .

Images in extra css files won't be replaced. That is to say, currently there is no way to replace it with CDN by LSCWP. For further LSCWP questions, please ask in https://wordpress.org/support/plugin/litespeed-cache/

Please try again. Best regards.

Just fixed the compatibility for destroy unfinished action. Please try again. Apologize for the inconvenience.

Do you mind to join our GLS slack to chat me directly? https://join.slack.com/t/golitespeed/shared_invite/enQtMzE5ODgxMTUyNTgzLWVhZDNhZDNmYWRhZmIwNzUxN2Y2ZDRjZGUwZjFiMDk1ZTNjZDJmMDg5NTcyZjFiZDM4MDY1NjkwYjkzM2E5YmE Thanks.

Hi, for future WP issues, plz come to https://wordpress.org/support/plugin/litespeed-cache/ to post. For this one, we improved the compatibility on our server side as that DBI_Error is an error happened on our server side. Please try it again.

BTW, the fix is already in github: https://github.com/litespeedtech/lscache_wp/commit/d5afabd08ea2f1fd76083240ee93d9778af6c99f

Thanks for your report. This compatibility issue is just confirmed. Will fix in next release.

That window is just an ajax monitor window. It won't affect the crawl process.

You can check your media list, see the latest one which is not optimized yet, if it has a long src, try to remove it.

This is because the latest attachment record in your postmeta table has a long src. We will improve this compatibility in next couple releases. Should be in v1.9.2

Yes that is true. Preloading will conflict with Analytics scripts.

That min/xx.css is stored in cache. Did you turn on async css? Not sure if it will help non-Render Blocking. Yes we can add that feature ( different rules for different pages ), but may need more suggestion on this point. For each page path, do you want to use any rule matching in setting? We...

The second one is because you deferred JQ but in your theme you have jQ used directly. Please either move it to document.ready wrapper or exclude jQ from defer

Bug confirmed. Will release a fix today. Thanks for your report.

Yes you can use LSMCD on server level. On script level, you can search `object cache` plugins. We are supposed to support this in couple weeks soon.

At this time, this week, correct ;)