LiteSpeed Technologies

Hi @hampmir

Thanks for the quick reply, we’ll try to figure out what’s going on. I see the area that’s failing, but not sure why it’s failing there.

A couple questions:

1. Is your WordPress a single site or a multisite?

2. Did you ever have our plugin installed and activated?

If you are willing to help us debug the issue, could you modify the following file:
wp-content/plugins/litespeed-cache/admin/class-litespeed-cache-admin-rules.php

At around line 517, there is a line:

		if ( $input[LiteSpeed_Cache_Config::OPID_MOBILEVIEW_ENABLED] ) {

Could you add the following line above it:

error_log('INPUT IS ' . print_r($input, true));

Then try to activate the plugin again.

This will either create an error log or append to your error log (this is commonly found in /home/youruser/public_html/error_log or /home/youruser/public_html/wp-admin/error_log

but it may vary depending on your setup.

Please let us know what you get!

Cheers,
Kevin

Hi @hampmir

This issue should have been resolved with the latest releases. What version are you using and what problems are you experiencing?

Cheers,
Kevin

Could you provide a list of plugins that are currently active?

An easy way to get a printable list is via LiteSpeed Cache->Environment Report

We think that another plugin has a js validation somewhere and is causing some interference with our plugin.

I wasn’t immediately able to reproduce the issue, but I’m looking for the part in code related to that. In the meantime, could you try hard refreshing the page? This can be done by shift+clicking the refresh button. It may be that you have a cached version of our js file. If it doesn’t fix it, at least we know that you have the latest version.

Cheers,
Kevin

Hi @goodereader

What plugins do you have installed and activated on that site? There may be some interference with another plugin that is causing the issue.

Cheers,
Kevin

Hi @chromasia

Please open the browser’s inspector (ctrl+shift+i) and refresh the settings page. Then try to modify and save settings. Do any errors pop up?

EDIT: Also, for completion, what settings did you try to modify?

Thanks,
Kevin

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

Ah, yes that’s not needed ??

But if you do come across an issue, let us know and we’ll be more than happy to try to make it work!

Cheers,
Kevin

Hi @yoav1987

We usually only add integrations if we get reports about issues with compatibility. Have you encountered issues when using Divi?

Cheers,
Kevin

Hi @amandathewebdev

Those rewrite rules do not look like they belong to our plugin, so we are not sure about where that came from.

That said, looking at those rules, I think it may be fixed if you add a dev/ before all occurrences of wp-content. That said, these rules do not belong to our plugin, so I cannot say for sure if that will fix or break the issue.

If you used a different caching plugin before, that may have been left over from the removal. In that case, you can comment these lines out with a # prefixed to each line.

Cheers,
Kevin

Hi Raul,

Good to know that it’s working! Thanks for your efforts on getting our plugins working together, I’ll be sure to add your plugin to our list of compatible plugins.

As for cache purging, the only issue we would come across would be if your plugin changes the paths in any way. If our cached page is expecting a certain url and your plugin already changed the url to something else, that’s when we’d have issues.

If you need anything from us, let us know!

Cheers,
Kevin

Excellent, thanks for letting us know!

This should be made more permanent in the next release. (possibly with its own file, we will see)

Cheers,
Kevin

Hi Richard,

Is your site correctly updating now?

I don’t think purging should have been required, so my guess is there is still an issue?

Cheers,
Kevin

Glad to hear it, let us know if you run into any more issues!

Cheers,
Kevin

Hi @greencode

If you don’t mind modifying code, we have a fix for the issue.

In the file wp-content/plugins/litespeed-cache/admin/class-litespeed-cache-admin-rules.php:

The modifications need to be made to the path_set function ~ line 224

	                $install = ABSPATH;
	                $access = get_home_path();

Needs to be replaced with:

                $real = trailingslashit(realpath(ABSPATH));
                $install = $real;
                $access = trailingslashit(realpath(get_home_path()));

And later,

	                else {
	                        // they are equal - no need to find paths.
	                        $this->home_path = ABSPATH . '.htaccess';
	                        $this->site_path = ABSPATH . '.htaccess';
	                        return;
	                }
	                $common_path = substr(ABSPATH, 0, -(strlen($install_part) + 1));

Should be replaced with:

                else {
                        // they are equal - no need to find paths.
                        $this->home_path = $real . '.htaccess';
                        $this->site_path = $real . '.htaccess';
                        return;
                }
                $common_path = substr($real, 0, -(strlen($install_part) + 1));

After that, the error should no longer occur.

Let us know if you have any questions about this!
Kevin

Hi Richard,

We’re in contact with WPLister’s developers and are trying to figure out the best way to handle the situation.

Would you be willing to test the fix?

In the file wp-content/plugins/litespeed-cache/thirdparty/class-litespeed-cache-thirdparty-woocommerce.php you will find a detect() function.

Right below the woocommerce_after_checkout_validation add_action, could you add another add_action? It should end up looking like the following:

			add_action('woocommerce_after_checkout_validation',
				'LiteSpeed_Cache_ThirdParty_WooCommerce::add_purge');
			add_action('wplister_revise_inventory_status',
				'LiteSpeed_Cache_ThirdParty_WooCommerce::backend_purge');
			add_filter('litespeed_cache_get_options',
				'LiteSpeed_Cache_ThirdParty_WooCommerce::get_config');

As you can see, the new add action is hooked to wplister’s revise_inventory_status action hook.

Let us know if you have any further questions about how to apply the fix and how it goes!

Cheers,
Kevin

EDIT: I just modified the code. It should be hooking the function backend_purge NOT purge_product.

• This reply was modified 7 years, 6 months ago by LiteSpeed Technologies.