• Resolved davidgeipel

    (@davidgeipel)


    Since Litespeed has an awesome crawler precache (only for dedicated servers), I need to precache several pages in advance on a server that won’t activate this feature – on a shared server. So I reactivated W3TC for both extended minify (there’s is better than LS for some reason), memcache db items (LS doesn’t support this option) and for our sitemap (under the page cache settings) – which is the main reason to use it. I need a precache and can’t seem to find another way to get a basic crawler than with W3TC. Grrrr.

    However, even though the checkbox for “page cache” isn’t checked, I am still getting the LS error:

    Please disable/deactivate any other Full Page Cache solutions that are currently being used. LiteSpeed Cache does work with other cache solutions, but only their non-page caching offerings—such as minifying css/js files. For this scenario only, please uncheck “Check Advanced Cache” in LiteSpeed Cache settings.

    Any chance this is in error?

    My advance cache file reads the following:

    <?php
    
    /**
     * W3 Total Cache advanced cache module
     */
    if (!defined('ABSPATH')) {
        die();
    }
    
    /**
     * Abort W3TC loading if WordPress is upgrading
     */
    if (defined('WP_INSTALLING') && WP_INSTALLING)
        return;
    
    if (!defined('W3TC_IN_MINIFY')) {
        if (!defined('W3TC_DIR')) {
            define('W3TC_DIR', (defined('WP_PLUGIN_DIR') ? WP_PLUGIN_DIR : WP_CONTENT_DIR . '/plugins') . '/a2-w3-total-cache');
        }
    
        if (!@is_dir(W3TC_DIR) || !file_exists(W3TC_DIR . '/inc/define.php')) {
            if (defined('WP_ADMIN')) { // lets don't show error on front end
                echo(sprintf('<strong>W3 Total Cache Error:</strong> some files appear to be missing or out of place. Please re-install plugin or remove <strong>%s</strong>.', __FILE__));
            }
        } else {
            require_once W3TC_DIR . '/inc/define.php';
    
            $redirect = w3_instance('W3_Redirect');
            $redirect->process();
    
            $config = w3_instance('W3_Config');
            if ($config->get_boolean('pgcache.enabled')) {
                $w3_pgcache = w3_instance('W3_PgCache');
                $w3_pgcache->process();
            }
        }
    }

    Hoping for either outcome by LS:

    1) There is a setting I can select that KEEPS LS CACHING… while removing this wraning.
    2) LS would just find a way to incorporate some advance precaching (call it PreCache Lite) that doesn’t scan all the time – just certain sets of files. Again, this is available in W3TC and WP Rocket. Again, without LS support for a basic version of this, I need to use some of these others.

    Of course, open to other options. I really didn’t want to go back to W3TC since LS has solved many of our basic issues. Thanks for your input.

    One of your biggest fans,
    Dave

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support LiteSpeed Lisa

    (@lclarke)

    Hi, Dave

    1) There is a setting I can select that KEEPS LS CACHING… while removing this wraning.

    Yes, you can uncheck the Include advanced-cache.php option under LiteSpeed Cache > Settings > Advanced. That should remove the warning.

    I should point out, though, that LiteSpeed and W3TC store caches in different locations, and are not at all related to each other. Even though you are just “precaching” the pages, there is still potential for conflict and wonky behavior when those pages are served.

    Admittedly, I don’t know much about the inner workings of W3TC, but my gut tells me that even if you crawl some of your pages with that plugin, when you uncheck “page cache”, it probably disables W3TC from serving any of those crawled pages anyway. Have you looked at your headers and verified that it’s working like you expect?

    Thread Starter davidgeipel

    (@davidgeipel)

    Thanks Lisa. The odd thing was that LiteSpeed was working with it checked. Must be that LS didn’t see the file from W3TC – “this file is detected as belonging to another plugin, LiteSpeed Cache will not cache”

    It’s hard to tell if it does precache those sitemap pages – I don’t see anything in the header for our sitemap page either. Hmmmm.

    Anyway, still hopeful your product team can find a way to offer a light weight version of the crawler. I know I am on shared hosting but I would think they would allow a lite version (limited to say 100 pages) because otherwise WP Rocket or W3TC would chew up more server resources. Hope you can keep those other posts alive internally and push to the top. Same with a special AMP cache.

    Dave

    Plugin Support Hai Zheng?

    (@hailite)

    Noted in our dev plan. Thanks.

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    You’re welcome, Dave.

    Yeah, it might still work even with the box checked, but there could be wonky behavior, and you’d keep getting the warning. Better to keep it unchecked ??

    Anyway, like Hai said, the “crawler lite” idea is now on our radar, so hopefully that will prove feasible.

    Cheers!

    Plugin Support Hai Zheng?

    (@hailite)

    Hi @davidgeipel again,

    Is there any particular reason that you want limit the crawler to 100 pages? Did you mean only crawl 100 pages each time?

    How about a server variable to set it? We already have couple new server variables in crawler in v1.9, e.g. CRAWLER_USLEEP.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘W3TC Warning’ is closed to new replies.