JS minify Fatal Errors in logfile

I have been struggling 2 days to find out why we have several thousand Google Webmaster Tools “500 not found” errors, and googlebot could not fetch anything from our site.
When I found these Litespeed Errors in the logfile, I disabled the plugin, and now all our urls can be instantly fetched.

I assume that google cannot fetch your urls if there’s a JS issue.
In fact, google did not even index our site since we last updated the plugin, if I do a “site:xxxxx.com” test.

I did not know google relies so much on JS to be working. We love your plugin, but we’ll be turning off any JS optimizations permanently to avoid it in the future.

Can you give a report number? need to check which js caused this exception.

I did a few tests. Google cannot reach our site if these options are enabled:

Unreachable + Temporarily unreachable:
JS Minify – ON
Inline JS Minify – ON
JS Combine – ON

Complete + Working:
JS Minify – OFF
Inline JS Minify – ON
JS Combine – ON

So the issue seems to be only with JS Minify.

Report number: ZIWRQAOY

When you turn on JS Minify, did you see any error when you visit? Or it just came from Google only?

I see these in my apache log file if JS minify is turned on:

PHP Fatal error: Uncaught Error: Class ‘JSMin\Exception’ not found in xxxxx/wp-content/plugins/litespeed-cache/lib/js_min.class.php:211
LiteSpeed_Cache_Optimize->_build_hash_url( in xxxxx/wp-content/plugins/litespeed-cache/lib/js_min.class.php on line 211

I saw another user also posted it 2 days ago:

https://www.ads-software.com/support/topic/fatal-php-error-in-wordpress-log/

Yes you two should be the same issue.

Now there are two things we need to figure out:

1. Which JS caused this issue. Can you turn on minify but no combine, and see which js is empty or caused this issue when you visit it? Purge JS cache first.

2. That exception not found issue should be avoided. We will fix it in next release.

If you like we can discuss the first issue on slack.

Hi, yes i’ll look into this a bit further and do better testing and let you know.

If you can turn off JS Combine, we can manually check which js caused this issue. If it’s ok for now, please let us know when you turned off.

This is fixed in https://github.com/litespeedtech/lscache_wp/archive/9631b482895f7731ce42f81f91fd6d2cb4510ae9.zip

which included 3 commits up to https://github.com/litespeedtech/lscache_wp/commit/9631b482895f7731ce42f81f91fd6d2cb4510ae9

Will include in next release.