• Resolved cybmeta

    (@cybmeta)


    Hi!!

    I’m trying to minify HTML but it is not working on main domain, while same configuration is working in a subdomain. I can not find what is happening.

Viewing 4 replies - 16 through 19 (of 19 total)
  • Thread Starter cybmeta

    (@cybmeta)

    Thank you!!

    I hope you can find the issue, so you or the dev of the other plugin can fix the incompatibiliy. I’ve been relying in “wp-cron crontrol” for a long time and it is a great plugin to be combined with HTML caching; it also helps to highly reduce the server resources used by normal wp-cron execution if there is not HTML caching (only one time every few minutes in the background, against one time for every visit and every user).

    • This reply was modified 6 years, 10 months ago by cybmeta.
    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    If that is your need for it , you can set up LSCWP crawler to do pre-cache.

    Best regards,

    Thread Starter cybmeta

    (@cybmeta)

    Yes, I know, but when you have the site cached, wp-cron is not trigered at all until the cache expires, this is a limitation: or you set a low expire time to have wp-cron executed often enough, or you execute wp-cron independently from the site visits/hits and don’t care about how site caching impacts over wp-cron.

    I tried before a system cron without the plugin “wp-cron control”, not as good as with it. wp-cron is a mess, I know, I tried a lot fixes and combinations, “wp-cron control” is by far the best I’ve found.

    Anyway, I’ve tested other optimization plugins (Autoptimize and W3TC specifically) and they work beside “wp-cron control” with no problem, so I guess you will find the issue.

    Thanks again.

    Thread Starter cybmeta

    (@cybmeta)

    Any update on this?

    I’ve found out that “wp-cron control” plugin set DOING_CRON constant to true to disable wp-cron.php and spawn_cron() execution, and also set WP_CRON to false to disable wp_cron() call.

    It seems that the conflict with LiteSpeed is the DOING_CRON constant. If it is true, then LiteSpeed evaluates HTML checking as false. (litespeed-cache.class.php), making the minification feature stop working.

    private function _check_is_html( $buffer = null ) {
    
         // ....
    
         if ( defined( 'DOING_CRON' ) ) {
    	LiteSpeed_Cache_Log::debug2( '[Core] CHK html bypass: doing cron' ) ;
    	return ;
        }
                    
        // ....
       
    }

    Any reason you do/need that?

Viewing 4 replies - 16 through 19 (of 19 total)
  • The topic ‘Minify HTML not working’ is closed to new replies.