Litespeed Cache v3.0.8.4 Broke My Sites

Hi,

May I know what is your PHP version ?

And also please go to Toolbox —> Best test , click “Use latest GitHub commit” and “Upgrade” , and see how it goes ?

Best regards,

I’m using PHP 7.2. I’ll give it a try. I did generate a report for you: EIALQZTN

• This reply was modified 4 years, 10 months ago by Jacob Hill.

Lite speed was working fine, but with the last update my site breaks, I can’t minify or combine js or css because yes I do it breaks. Help please, is there a way to go back to a previous version? The plugin worked excellent. I use elementor.

Also had critical errors with v3.0.8.4, had to rollback to previous

2020-05-01T00:19:27+00:00 CRITICAL Uncaught Error: Call to undefined method WooCommerce::get_instance() in /var/www/html/wp-content/plugins/litespeed-cache/thirdparty/wplister.cls.php:23
Stack trace:
#0 /var/www/html/wp-includes/class-wp-hook.php(287): LiteSpeed\Thirdparty\WPLister::detect()
#1 /var/www/html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters()
#2 /var/www/html/wp-includes/plugin.php(478): WP_Hook->do_action()
#3 /var/www/html/wp-content/plugins/litespeed-cache/src/core.cls.php(297): do_action()
#4 /var/www/html/wp-includes/class-wp-hook.php(287): LiteSpeed\Core->load_thirdparty()
#5 /var/www/html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters()
#6 /var/www/html/wp-includes/plugin.php(478): WP_Hook->do_action()
#7 /var/www/html/wp-settings.php(562): do_action()
#8 /var/www/html/wp-config.php(136): require_once('/var/www/html/w...')
#9 /var/www/html/wp-load.php(37): require_once('/var/www/html/w...')
#10 {main}
  thrown in /var/www/html/wp-content/plugins/litespeed-cache/thirdparty/wplister.cls.php on line 23

Apologize for this issue. We got the report this morning, and fixed it in latest v3.0.8.5 release. The WooCommerce is a different issue. Separate topic can help us get notified of the issues faster.

The O_CRAWLER_MAP_TIMEOUT error will disappear after you refreshed the page. Its a potential one time error. It could happen bcos you are having cron running at the moment upgrade. This new setting is for the crawler cron.