ibertrix

sorry, I forgot to ask…in github rodrigo mentions that wp_options stores the tax settings. How can I delete those entries to see if that fixes the issue?

for everybody having this issue of not being able to add the url for the privacy page, once created the text in the contact form itself shows up a shortcode for wpgdprc plugin in the contact form 7 form tab:

[your contact form fields]

<p>[wpgdprc “your text..blah blah…You can read my”] privacy policy

[submit “Send”]</p>

I suggest you to open a ticket with Woocommerce @mojote.

I was suggested to update to 2.2.16 when I did raise a ticket myself and It worked. The worst part is that we had to get a Woocommerce subscription to be able to update it.

I am helping a friend who is having exactly the same issue with Woocommerce 3.2.6 and woocommerce-gateway-stripe 3.2.3

Since March subscriptions created by him that were working before stopped sending the payments to Stripe and the purchase was labeled as Pending instead of Processing (also I don′t understand why purchases that worked before were left as Processing instead of Complete).

I followed the link sent by @petervandoorn but that plugin has not been tested for WordPress 4.9.1

@robjh did you find a solution?

Anyway, I am going to raise a ticket in Woocommerce support as suggested by @melindahelt

Many thanks!

Ok, I have solved it within the script:

#!/bin/bash

WP="/usr/local/bin/php -d suhosin.executor.include.whitelist=phar /usr/local/bin/wp --allow-root"

array=($(find /home -maxdepth 6 -type d -name '*wp-content*' -exec dirname {} \;))

for x in ${array[@]} ;do
 echo "Chequeando:" $x
 $WP --path=$x core version
done

I do have Cpanel with EasyApache 4 but I don′t have suhosin installed:

php -v
ea-php-cli Copyright 2017 cPanel, Inc.
PHP 7.0.25 (cli) (built: Nov 7 2017 04:14:18) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies
with Zend OPcache v7.0.25, Copyright (c) 1999-2017, by Zend Technologies

Do I still need to set it?

Ok, I found out a solution that doesn′t need to change the plugin code.

This is the thread in the Varnish mailing list:

https://varnish-cache.org/lists/pipermail/varnish-misc/2017-August/026083.html

and the article that shows it:

https://info.varnish-software.com/blog/step-step-speed-wordpress-varnish-software

I found that article in this article where a warmer plugin is mentioned:

https://michaelshadle.com/projects/varnish-http-purge-warmer

Hope this helps others

Sorry, My concern is not this status thing anymore. I have asked in the correct question, about clear cache button which is trying to purge and doesn′t work in Varnish 4, while banning might be the way to go and might work in all versions of Varnish

Is it not possible to use banning instead of purging? That would work in any version of Varnish

I have seen there are new updates recently. Has the plugin been tested with Varnish 4?

Apparently your plugin works with Varnish 4, at least I haven′t found anything odd.

I have performed a quick search on the description of the plugin and I don′t find any reference of not supporting Varnish 4. From the top of my head, Varnish 4 was released in 2014-2015, when do you expect to fully support version 4?

I have a similar issue, Varnish is working and Varnish http purge plugin seems to detect it at some extent.

We did not find Varnish active for this domain.

Your sever IP setup looks just fine. If you are using a proxy (like Sucuri or Cloudflare or Fastly) please double check that configuration and make sure to add a custom Varnish IP .

Your site is compressing content and making the internet faster.

However I noticed that since version 4 of the Varnish http purge plugin, when I hit purging the varnish cache I had to manually purge the cache from command line or even worse, had to restart Varnish.

And adding anything on functions.php?

This code doesn′t seem to work with your javascript added:

function _remove_script_version( $src ){
$parts = explode( ‘?’, $src );
return $parts[0];
}
add_filter( ‘script_loader_src’, ‘_remove_script_version’, 15, 1 );
add_filter( ‘style_loader_src’, ‘_remove_script_version’, 15, 1 );