Purge on CLI not working properly

  • Resolved inception12

    (@inception12)


    3 years, 7 months ago

    When updating the plugin “Featured Image From URL” it causes a caching issue of images that is fixed by purging LiteSpeed Cache. The problem is, it doesn’t fix the site when the site is purged using the CLI. It works properly when purged logged into the site. We have 2,000 wordpress sites that will eventually require the updated version of this featured image plugin. We update our sites using the CLI and we are not going to go into each site manually to update it properly. Not exactly sure why “wp litespeed-purge all” isn’t working to fix the issue. I’ve talked to the creator of the plugin that is causing the issue to happen and they said that it is a caching issue. Please help. An example is the broken images on this site: https://www.livepainfreeocala.com/

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Support qtwrk

    (@qtwrk)

    Hi,

    due the way LiteSpeed Cache engine works , it has to have a targeted domain to know which vhost’s domain to purge

    when you use WP CLI to purge , it will store the purge call into the database, and then on next request that hit PHP in browser , will fire that purge , so this way the webserver knows which domain’s cache to be purged

    e.g. 

    <?php
require( './wp-load.php' );
if ( defined(LSCWP_V)) {
  do_action( 'litespeed_purge_all' );
  echo 'done';
}

    if you access it by browser as https://domain.com/some.php , it purges immediately

    if you access it by SSH command line as php /path/to/some.php , it will store the purge call until the PHP on that domain has been hit again

    you can use above code to create a PHP file , then , instead of using wp litespeed-purge all , you can use curl -I -XGET https://domain.com/some.php for immediate purge

    Best regards,

Viewing 1 replies (of 1 total)
  • The topic ‘Purge on CLI not working properly’ is closed to new replies.