Forum Replies Created

Viewing 15 replies - 121 through 135 (of 221 total)
  • Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi greencode,

    This depends on how your blog is accessed.

    The setting you are looking for is litespeed cache -> settings -> do not cache rules -> do not cache URI
    If your blog is accessed like example.com or sub.example.com, you could just enter /$.

    Else, if your blog is accessed like example.com/blog/, you will need to enter /blog/$

    If you are not sure, just post a link and I’ll give you something to try 🙂

    Cheers,
    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Good to know that it works!

    Yes, it will be in the next release, thank you 🙂

    Cheers,
    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Apologies, apparently my replacement bit did not actually contain the replacement bit 🙂
    Replacement bit:

    
    		$params = $_GET;
    
    		if (!empty($params)) {
    			if (isset($params['LSCWP_CTRL'])) {
    				unset($params['LSCWP_CTRL']);
    			}
    			if (isset($params['_wpnonce'])) {
    				unset($params['_wpnonce']);
    			}
    			if (!empty($params)) {
    				$prefix .= http_build_query($params) . '&';
    			}
    		}
    
    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi Jared,

    I am not sure about the other _GET members, but I think I have an idea as to where _wpnonce is removed.

    In litespeed-cache/admin/class-litespeed-ccache-admin.php, there is a function add_quick_purge(). Try replacing $_GET with a new variable.

    Chunk to replace and the replacement are listed below.

    Kevin

    Original bit:

    
    		if (!empty($_GET)) {
    			if (isset($_GET['LSCWP_CTRL'])) {
    				unset($_GET['LSCWP_CTRL']);
    			}
    			if (isset($_GET['_wpnonce'])) {
    				unset($_GET['_wpnonce']);
    			}
    			if (!empty($_GET)) {
    				$prefix .= http_build_query($_GET) . '&';
    			}
    		}
    

    Replacement bit:

    
    		if (!empty($_GET)) {
    			if (isset($_GET['LSCWP_CTRL'])) {
    				unset($_GET['LSCWP_CTRL']);
    			}
    			if (isset($_GET['_wpnonce'])) {
    				unset($_GET['_wpnonce']);
    			}
    			if (!empty($_GET)) {
    				$prefix .= http_build_query($_GET) . '&';
    			}
    		}
    
    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi linusgr,

    Sorry about the lack of response! With the changes to the support forum, we missed your prior message.

    Glad to hear everything is working now. Let us know when you encounter any issues!

    Cheers,
    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi @richireo2016,

    I did not encounter any issues when trying this plugin.

    Only thing to note is that if you change the css/js in any way, Autoptimize will refresh the files. Currently, LiteSpeed Cache pages will not update with that, so if you change your css/js in any way, make sure to manually purge the litespeed cache.

    Cheers,
    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    @futtta: That’s the thought. The way our cache works is through response headers. These are currently set in the shutdown hook with 0 priority, so if I have no requirement of being at 0 priority, I should be able to hook into autoptimize_action_cachepurged.

    I’ll be sure to create a support thread when I get back to it.

    Cheers,
    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi Dennis,

    You are getting the error message because the define in the advanced-cache.php did not trigger. It is possible that BPS Pro prevented us from writing that file.

    Please check your /wp-content/advanced-cache.php file. Does it match /wp-content/plugins/litespeed-cache/includes/advanced-cache.php?

    Regarding minification, I recently tested W3 Total Cache and Autoptimize and personally have had no issues (but another user mentioned trouble setting autoptimize, so YMMV).

    I suggest trying Autoptimize first. You should only need to select ‘optimize javascript code’ and ‘optimize css code’.

    One important thing to note with this is that if you change your css/js contents, you need to manually purge the litespeed cache. This will be added in the next version.

    If you’d rather try w3 total cache’s minify, I could provide instructions for that.

    Cheers,
    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    There are multiple possibilities, all depending on how your server was installed.
    The first place to check is your where your wordpress’s index.php file is, so if it is at /home/user/public_html/index.php, look for /home/user/public_html/error_log.
    Else you could have your own error log, /home/user/logs/error_log.
    Else it could be at /usr/local/apache/logs/error_log or /usr/local/lsws/logs/error.log

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    So I believe that you might have something updating during the cron job. For whatever reason, everything gets purged when the cron job hits.

    If you are comfortable editing code, please go to our file litespeed-cache/includes/class-litespeed-cache.php
    Inside, there is a function add_purge_tags. At the top of the function add the following:
    error_log('purge tags ' . $tags);

    So that it looks like:

    	private function add_purge_tags($tags, $is_public = true)
    	{
    error_log('purge tags ' . $tags);
    		//TODO: implement private tag add
    		if (is_array($tags)) {
    			$this->pub_purge_tags = array_merge($this->pub_purge_tags, $tags);
    		}
    		else {
    			$this->pub_purge_tags[] = $tags;
    		}
    		$this->pub_purge_tags = array_unique($this->pub_purge_tags);
    	}

    Once this line is added, an error log should be printed out every time something is purged. You can test this by pressing the purge front page button in the litespeed cache management page. Once confirmed, wait for the cron to activate, and check the error log – there should be new messages. We’re interested in what tags are purged.

    Thanks,
    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi longnha,

    What actions do you take during your cron jobs? I’d like to know which options you have checked in the purge rules settings as well.

    Thanks,
    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Thanks for the kind words! If you have any questions or issues, just let us know and we’ll be happy to help 🙂

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Glad to hear that it’s working well for you! Let us know if you have any issues with the plugin.

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Hi wwwolf,

    We’re sorry to hear that you had such a negative experience using our cache plugin.

    We do strive to make this plugin as ‘plug and play’ as possible, so we apologize for the time you had to spend fixing it.
    If you are still willing to work with us, which plugins did you encounter issues with?

    As for the automatic installation, we do not automatically install this plugin ourselves. We do have a plugin in WHM/cPanel that is intended to make it easier for hosts to mass install this plugin, so that may be what you are referring to.

    Once again, we apologize for any inconvenience we caused. If you are still interested at all in using our plugin, please email me at kfwu at litespeedtech dot com and I will personally assist you in resolving any/all issues that you encounter.

    Best,
    Kevin

    Plugin Author LiteSpeed Technologies

    (@litespeedtech)

    Just replied. If you are able to, please contact your server admin to see if they can upgrade your server. If that doesn’t fix the issue, we will probably need elevated access to the servers to determine what the issue is.

Viewing 15 replies - 121 through 135 (of 221 total)