MikevHoenselaar

I like to have this as well. Some way of having profiles. So attach plugins to a profile and just enable and disable profiles. This way makes debugging WAY faster ;).

Ajax loading is active. Doesn’t make a difference.

Video of Console: https://monosnap.com/file/az25ar7ufiIDUwAu6FzXA9sJV7sfOR

It worked. Great stuff! Thanks.
You probably can add this config also in an update of the plugin so WPML can scan it itself right?

I hope someone can get back to me about this. Thanks.

We have all the latest version of WordPress, WooCommerce, WPML and Mailchimp for WooCommerce.

“Mailchimp says: API Request Error – API Key InvalidYour API key may be invalid, or you’ve attempted to access the wrong datacenter. on 1861 in wp-content/plugins/mailchimp-for-woocommerce/includes/api/class-mailchimp-api.php”

This is what I am getting as well.
Not sure what is causing it.

“Testing is done before release, but impossible to test all instances without others that contribute.”

The last ‘quick fix’ updates are all notices. So this is a matter of variable declaration to me.

Just test with things like this active:
error_reporting(E_ALL);
ini_set(‘display_errors’,1);

So you catch those notices as well before pushing it to directory :).

Good luck with building it further.
Thanks a bunch.

Notice: Undefined index: strip_comment_author_links in /wp-content/plugins/zero-spam/integrations/comments/comments.php on line 205

Notice: Undefined index: strip_comment_links in /wp-content/plugins/zero-spam/integrations/comments/comments.php on line 212

Notice: Undefined index: verify_comments in /wp-content/plugins/zero-spam/integrations/comments/comments.php on line 221

Same here.

Please check the Notices as well before pushing the plugin to the directory.
Thanks a bunch!

Luckily plugin devs are lightning fast with updates lately :).

I fixed it myself.
Hopefully this gets added to the plugin.

https://codeshare.io/TvhoH

The problem was the plugin didn’t do anything with the inputName variable. This is the variable GF uses for population.

Have fun with it! ??

Any more news on this issue? I’m having the same problem. This way the dynamic populated fields option isn’t working and therefor useless.
Love to get an update on this.

As far as I know it could break if there are POST requests being done by AJAX.
That way they can’t be cached by CloudFlare/W3TC.
So I have heard.
I am searching for a solution to have Google Tag Manager work with CloudFlare.
Any tips welcome.

Still unresponsive here with 4.0.7.
Only on homepage.
Strange stuff.
I deactivated it now and am looking for alternatives.

Love to hear if you problem still exists Nick so I can help you fix it.
Thanks.

Did you get this to work, I see the domain isnt working anymore.