Not much changed in the plugin: https://plugins.trac.ww.wp.xz.cn/changeset?sfp_email=&sfph_mail=&reponame=&new=1179220%40varnish-http-purge&old=1148543%40varnish-http-purge&sfp_email=&sfph_mail=
Seriously. It was a change to add in a schema and default to http if it wasn’t already set.
WP-cli was not impacted whatsoever. This version of the plugin doesn’t touch it. That command is a default WP cli command.
What happens when you run it?
wp --allow-root --path="{}" option add vhp_varnish_ip xx.xx.xx.xx \;
I was able to resolve the wp-cli issue, which is working. Instead I use:
wp –allow-root option update vhp_varnish_ip XX.XX.XX.XX \;
Success: Value passed for 'vhp_varnish_ip' option is unchanged.
However, with the varnish-http-purge.php (in mu-plugins), my websites are still displaying inside of a box. I have no idea how it would even effect the sites. If I remove the plugin, everything is displayed correctly again.
I figured out what happened….
My cron job to fetch the latest versions for my mu-plugins from:
wget -O varnish-purge.zip http://downloads.wp.xz.cn/plugin/varnish-http-purge*.zip
After I examined the varnish-http-purge.php file, it’s actually 3.8-beta.
So I’m actually having problems with 3.8-Beta. The sites that are still using 3.7.3 doesn’t have any issues.
Good to know about the beta at least. That’s why it wasn’t released yet 😉
So I tested this on Varnish 3 and it worked fine.
I wonder if you can do some debugging?
To see every request made to varnish, use this:
varnishncsa -F "%m %U"
If you want to grab the last purge requests, it’s this:
varnishlog -d -c -m RxRequest:PURGE
And this will show you if the WP button was used:
varnishlog -d -c -m RxURL:.*vhp_flush_all.*
So what I would do is that first command and then leave it open while you press the button, see if the cache is flushing and what URLs it’s passing through.
FOUND IT!
*omg* Okay, it explains everything and especially why the beta blew up wp-cli. If you want to test the beta, it’s up as trunk on SVN.
