• Resolved phloo

    (@phloo)


    To update my site I use the wp cli command to flush the FVM cache
    In return I get “Success: FVM and other caches were purged.”
    But nothing is really changed, instead I have to login to the site and manually flush the FVM cache via the toolbar.

Viewing 4 replies - 16 through 19 (of 19 total)
  • Plugin Author Raul P.

    (@alignak)

    2 things:

    a) it appears that wp cli is working (the directory name changes after you purge it)
    b) The hash, 498bb607109d20c2a937936f4be405b507657e2a is the same (this means, the contents inside the css files may be different, but the css file names are exactly the same).
    c) If it’s wpengine… disable OP Cache. There is an option on wpengine to disable object cache. They use a very aggressive cache method and even options, from wp_content (such as cronjobs) get cached and do not refresh easily. This causes issues with many plugins actually, including woocommerce.

    In regard of b) if the hash name is the same, that means the css files are not changing. FVM is seeing the same exact list of css files (see the status page for the log).

    That means, it’s either cached on OP Cache or the code is incorrectly enqueued.
    Knowing wpengine, it’s likely the first one. Disable it and test.

    Yes, the plugin issues a cache purge request to wpengine… but beware. WP Engine, limits the amount of times you can purge files. It only allows one purge every 5 minutes, so anything between it, will simply be ignored (without feedback).

    Thread Starter phloo

    (@phloo)

    a) it appears that wp cli is working (the directory name changes after you purge it)

    yes, it does generate a new file but not the same when clicking “FVM purge” from the toolbar

    b) The hash, 498bb607109d20c2a937936f4be405b507657e2a is the same (this means, the contents inside the css files may be different, but the css file names are exactly the same).

    Yes, as is should be, from the perspective of the plugin. But here is the problem: it gets the wrong list of files. The generated HTML shows its a redesigned page. But the enqueued scripts/styles seen by FVM are wrong. Without FVM it works correctly.

    c) If it’s wpengine… disable OP Cache.

    Will try..

    Yes, the plugin issues a cache purge request to wpengine… but beware. WP Engine, limits the amount of times you can purge files. It only allows one purge every 5 minutes, so anything between it, will simply be ignored (without feedback).

    I know. But it doesnt matter if I only use it once or multiple times. WP CLI stopped working to flush the cache correctly.

    That means, it’s either cached on OP Cache or the code is incorrectly enqueued.
    Knowing wpengine, it’s likely the first one. Disable it and test.

    What I dont understand is that, if the page is OP cached, why is the html output showing the correct code (with redesign elements) but the enqueued scripts are the wrong ones?

    Plugin Author Raul P.

    (@alignak)

    What I dont understand is that, if the page is OP cached, why is the html output showing the correct code (with redesign elements) but the enqueued scripts are the wrong ones?

    OP cache doesn’t cache html. It caches PHP Objects, which vary.
    It doesn’t cache all objects, only a few it considers important.
    Try to disable it and try, else we don’t know if it’s that.

    yes, it does generate a new file but not the same when clicking “FVM purge” from the toolbar

    The code inside may be different, but the hash is the same.
    That means, the list of files haven’t changed.
    Try the OP Cache off on wpengine. It’s well known to cause issues like these on many plugins.

    If it’s not that, then contact me via fastvelocity.com and I can take a look.

    Thread Starter phloo

    (@phloo)

    Checked the WPengine settings. OP Cache wasn’t active.

    I will contact you as mentioned by you. Thanks!

Viewing 4 replies - 16 through 19 (of 19 total)
  • The topic ‘[2.8.9] wp cli command no more working?’ is closed to new replies.