LiteSpeed Optimization column missing in Media

The condition to show the column in LSCWP is check the need pull status exists or not. If you used to delete record in wp_options table, the column in Media will not show anymore.

To check if the record exists in database, run below in your database tool e.g. phpmyadmin:
select * from xxx_options where option_name like '%need_pull' and see if there is any data shown.

Hi @hailite,

As I’ve said, this issue doesn’t happen with version 2.9.7.1 (which I am currently reverted to for this matter). It only happens from 2.9.8 onwards.

And yes, the %need_pull% option is autoloaded in my wp_options.

That is strange. I may need to debug further. Do you mind to join our slack and @ hai or send an email to [email protected] ? Thanks.

I’ve just sent an e-mail.

Thank you.

Hello

Same issue here… I’m using v2.9.8.2
> The LiteSpeed Optimization column does no longer appear in Media.
> On front-end, the optimized versions are served properly though (including .webp).

I just run the SQL and yes, the %need_pull% option is also set to autoloaded in my wp_options.

The issue is not on 1 site but all of my 30 websites…

Thanks

Just debugged and found the const LITESPEED_BYPASS_OPTM is defined. That is why the media funcs are bypassed. Please search this string LITESPEED_BYPASS_OPTM in your plugin folder and theme folder and see which file made it.

How exactly do we search for that and where?

(And how come versions of LS Cache prior to 2.8 don’t have this issue?)

We are investigating this issue now. That is a good question. We will fix it in a new release v2.9.8.3 this week.

The issue comes from you:

[~/public_html]# grep -d recurse 'LITESPEED_BYPASS_OPTM' .
./wp-content/plugins/litespeed-cache/inc/litespeed-cache.class.php:                     ! defined( 'LITESPEED_BYPASS_OPTM' ) && define( 'LITESPEED_BYPASS_OPTM', true ) ;
./wp-content/plugins/litespeed-cache/inc/litespeed-cache.class.php:                     ! defined( 'LITESPEED_BYPASS_OPTM' ) && define( 'LITESPEED_BYPASS_OPTM', true ) ;
./wp-content/plugins/litespeed-cache/inc/litespeed-cache.class.php:             if ( ! defined( 'LITESPEED_BYPASS_OPTM' ) ) {
./wp-content/plugins/litespeed-cache/inc/litespeed-cache.class.php:             if ( ! defined( 'LITESPEED_BYPASS_OPTM' ) ) {
./wp-content/plugins/litespeed-cache/inc/litespeed-cache.class.php:             if ( ! defined( 'LITESPEED_BYPASS_OPTM' ) ) {
./wp-content/plugins/litespeed-cache/includes/litespeed-cache.class.php:                        ! defined( 'LITESPEED_BYPASS_OPTM' ) && define( 'LITESPEED_BYPASS_OPTM', true ) ;
./wp-content/plugins/litespeed-cache/includes/litespeed-cache.class.php:                        ! defined( 'LITESPEED_BYPASS_OPTM' ) && define( 'LITESPEED_BYPASS_OPTM', true ) ;
./wp-content/plugins/litespeed-cache/includes/litespeed-cache.class.php:                if ( ! defined( 'LITESPEED_BYPASS_OPTM' ) ) {
./wp-content/plugins/litespeed-cache/includes/litespeed-cache.class.php:                if ( ! defined( 'LITESPEED_BYPASS_OPTM' ) ) {
./wp-content/plugins/litespeed-cache/includes/litespeed-cache.class.php:                if ( ! defined( 'LITESPEED_BYPASS_OPTM' ) ) {
 [~/public_html]#

Hi,

Could you please submit a ticket here ? we will investigate it further.

Best regards,

Hi guys,

This is still not fixed in v 2.9.8.3.

Hi,

Yes, we were planning to debug this , but we would need assistance in order to debug it.

It’s postponed as we can’t get the environment that can reproduce it.

Could you please submit a ticket here for further assistance ?

Best regards,

Hi this is fixed in https://github.com/litespeedtech/lscache_wp/commit/a7561f1146845806497db5dd27e2651ca01dbf5c and will be in v3.0

Thanks.

Hi @hailite,

Thanks for letting us know (I’m still on v2.9.7.1 because of it).

Best regards

Hi @hailite,

I know you said that this was going to be in v 3.0, but it was supposed to be a minor change, why wouldn’t you guys fix it in any version following v 2.9.7.1?

Nevertheless, please note that the above solution is not working.

I’ve just tried it on version 2.9.8.5 of the plugin.

It’s a bit awkward how such a small issue can remain unresolved for such a long time.

Because of it, I am still running on v 2.9.7.1 on my live website.

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