fishbottle

I had the same problem!

You need to go to: Woocommerce > No Captcha
in the Admin menu.

Then enter your Site and secret keys (which you can get from Google via the link on that page)

See screenshot here:

View post on imgur.com

It’s the oddest thing, but 90% of plugin makers don’t tell you where to find the settings for their plugin after it is installed. Hope that helps.

Thank you Luciamarinescu.
I have now tried everything I can think of. For the last two days I disabled every single plugin except yours, I deleted and recreated the import, I disabled and reinstalled the plugin but the duplicate posts keep showing up, more than ever. I am getting multiples of every post now, sometimes each one up to 6 or 7 times. Im heartbroken but I can’t think of anything else to try.
Screenshot here Can you think of anything else I can try?

Yes, the Remove Duplicates is on (green)
I am manually deleting all the duplicate posts but let me know if it is important for troubleshooting and I can let the next batch of duplicates get published, but it looks terrible to visitors on the site so I’d rather not.

If it helps, they are like this (I replaced my site base url below)
https://mywebsitename.com/making-sense-of-opensea-at-a-13b-valuation/
https://mywebsitename.com/making-sense-of-opensea-at-a-13b-valuation-2/
https://mywebsitename.com/making-sense-of-opensea-at-a-13b-valuation-3/

Thanks!

It started approximately a week ago I think. I don’t think anything changed but my WordPress and plugins are set to update so I don’t know which plugins were updated in that time.
I only have one feed and one import setup.
This is the feed
https://contentgems.com/feeds/v2/filters/UXX8DfWJWDcRF3GlR5nf

THANK YOU @poonam9 !
That is perfect. I was able to install “Featured Image in Content” plugin and now its working great in my original theme.

Hi @poonam9
Yes, certainly. Here it is:
https://contentgems.com/feeds/v2/filters/UXX8DfWJWDcRF3GlR5nf

Thank you!

Fantastic! Thanks for the sample CSV file. I can’t tell if it supports HTML or not? I hope so. I guess I’ll find out.

Thank you so much for your excellent debugging suggestions.
That was great advice and great to have a recipe to follow. I thought perhaps one of the services I was firing by tag might actually have it’s own pixel script.

I paused all of the tags one by one until there were none, I cleared caches, tried different browsers, completely removed some scripts but it still showed 2 pixels. Eventually I gave up out of frustration and re-enabled the tags and left it with the error (my data in Facebook never seemed off by the way!)

A couple of weeks later I couldn’t remember if I had tried the fake container ID test or not, so I went back to test that but by some miracle the pixel helper no longer showed the 2 pixel error, even though I hadn’t touched anything in the intervening 2 weeks.

Maybe it was a bug in the pixel helper. It will probably forever be a mystery, but at least its no longer a problem and I have a great set of debugging instructions to follow should it happen again.
Thanks Thomas!

• This reply was modified 4 years, 9 months ago by fishbottle.

I think this is the issue, it’s reporting the users full name https://i.imgur.com/Pw3RuR4.png
I turned off advanced tracking and cleared the cache in case it’s coming from there but I am still getting the warning

Ok, sounds good. Thanks for the link, I’ll look into but essentially it’s working well now.
Thanks for all the help with your Wonderful plugin.

Reporting is correct now!
I changed a few settings, including adding ‘don’t track value’ to all events except for purchase (https://goo.gl/PbYpdS) I guess this is what I did that made it work as the purchase value tracking is now correct in Facebook’s reporting.

I wonder, does this mean that now it won’t track the amount of ‘add to carts’ or ‘view content’ etc or is the ‘value’ strictly for currency transactions?

• This reply was modified 6 years, 9 months ago by fishbottle.

I tried to wing it, (guessing which version of Oauth to use for example) but it didn’t go so well. Purchases weren’t able to be completed and I got this error:

Fatal error: Cannot declare interface Psr\Log\LoggerInterface, because the name is already in use in?/wp-content/plugins/sip-mautic-integration-for-woocommerce/admin/mautic/Psr/Log/LoggerInterface.php?on line?20

Confusing, but reassuring that you don’t see anything wrong. I have a call booked with someone from Facebook tomorrow I will see if they have any ideas. I’ll follow up here if I find anything more from them or a url in the admin. Thank you!

Ok, will do.
I will try to get around it with on page notices and an entry on my help page.
Thanks Richard!

Until you hear back from the author…This video tutorial helped me a lot.