Facebook-for-woocommerce: Strange dot in bottom of pages

[zzbeck]

Hello,

After the recent update, I have noticed a small (but annoying) problem.
When _Facebook for WooCommerce_ is active, a small piece of code is added to the bottom of the page, adding a dot.

It's the following code:
<div class="pub_300x250 pub_300x250m pub_728x90 text-ad textAd text_ad text_ads text-ads text-ad-links" style="position: absolute;">.</div>

When I deactivate the plugin, it code and dot is gone.

Thank you for you work - really appreciate it.

[citymont]

Hello @zzbeck ,
If you are using an Adblock, this one create a HTML div when it observes a Facebook Pixel.
This is the reason of this "dot" ;)

[zzbeck]

Hello. I am not using an adblocker, the problem only vane after the recent update, and the problem follows across different browsers.

[dmitridr]

Hello,

Our extension does not add this code, a search through our repository confirms this. Therefore, this code must be being added by another extension that you have, or some other behavior. It is likely that there is some conflict with the Pixel being installed by this extension and that other extension.

As @citymont says it could be caused by AdBlock, but it could also be caused by an Anti-AdBlock extension that you may be using. For example this : https://github.com/sitexw/BlockAdBlock/blob/master/README.md

If you search for the string pub_300x250 pub_300x250m pub_728x90 text-ad textAd text_ad text_ads text-ads text-ad-links you will see that this extension uses that.

Hope that helps.

[bfp-zz]

It is happened in my website!
https://connect.facebook.net/en_US/fbevents.js
This js file some lines on 2018/1/12 15:32:05!

But they said their extension does not add this code.

It was fixed now,so the code is disappeared in fbevents.js!

[dmitridr]

Weird. Good point, maybe it was in the fbevents.js, this is not controlled by us but by a separate team. @zzbeck did the problem go away for you?

[dmitridr]

I assume it went away and this was an fbevents.js bug. If it happens again please open a new issue and reference this one.