Support » Plugin: NextGEN Facebook » Possible conflict

  • Resolved malinky

    (@malinky)



    Hi there,

    We are running the free version of NGFB and are getting conflict messages on product pages (see below), posts, and pages. We’re running the Neighbourhood theme and WooCommerce. I have read other posts with similar issues but I don’t understand what exactly we need to do to resolve this issue in a way that won’t be overwritten by theme and plug-in updates. Would very much appreciate your help on this one.

    Cheers,
    Karen

    NGFB Notice:

    Possible conflict detected – your theme or another plugin is adding a meta property=”fb:admins” HTML tag to the head section of this webpage.

    NGFB Notice:

    Possible conflict detected – your theme or another plugin is adding a meta property=”og:url” HTML tag to the head section of this webpage.

    NGFB Notice:

    Possible conflict detected – your theme or another plugin is adding a meta property=”og:type” HTML tag to the head section of this webpage.

    NGFB Notice:

    Possible conflict detected – your theme or another plugin is adding a meta property=”og:locale” HTML tag to the head section of this webpage.

    NGFB Notice:

    Possible conflict detected – your theme or another plugin is adding a meta property=”og:site_name” HTML tag to the head section of this webpage.

    NGFB Notice:

    Possible conflict detected – your theme or another plugin is adding a meta property=”og:title” HTML tag to the head section of this webpage.

    NGFB Notice:

    Possible conflict detected – your theme or another plugin is adding a meta property=”og:description” HTML tag to the head section of this webpage.

    NGFB Notice:

    Possible conflict detected – your theme or another plugin is adding a meta property=”og:image” HTML tag to the head section of this webpage.

    NGFB Notice:

    Possible conflict detected – your theme or another plugin is adding a meta property=”og:image:width” HTML tag to the head section of this webpage.

    NGFB Notice:

    Possible conflict detected – your theme or another plugin is adding a meta property=”og:image:height” HTML tag to the head section of this webpage.

    NGFB Notice:

    Possible conflict detected – your theme or another plugin is adding a meta itemprop=”name” HTML tag to the head section of this webpage.

    NGFB Notice:

    Possible conflict detected – your theme or another plugin is adding a meta itemprop=”headline” HTML tag to the head section of this webpage.

    NGFB Notice:

    Possible conflict detected – your theme or another plugin is adding a meta itemprop=”description” HTML tag to the head section of this webpage.

    NGFB Notice:

    Possible conflict detected – your theme or another plugin is adding a meta itemprop=”url” HTML tag to the head section of this webpage.

    NGFB Notice:

    Possible conflict detected – your theme or another plugin is adding a meta itemprop=”image” HTML tag to the head section of this webpage.

    https://wordpress.org/plugins/nextgen-facebook/

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author JS Morisset

    (@jsmoriss)

    Do you have a URL to an example post/page?

    Thanks,

    js.

    malinky

    (@malinky)

    Sorry, I thought I had included that.

    The site is http://aucklandbeads.com

    Any page, post, or product page will do as they’re all affected.

    Cheers,
    Karen

    Plugin Author JS Morisset

    (@jsmoriss)

    I’ve no idea which page I should be looking at, especially since most of them are products. Could you please give me the URL to an example webpage showing this error, as I requested?

    Thanks,

    js.

    Plugin Author JS Morisset

    (@jsmoriss)

    Can I assume this problem has been resolved?

    js.

    malinky

    (@malinky)

    Plugin Author JS Morisset

    (@jsmoriss)

    Click on the “Clear All Cache(s)” button on any NGFB settings page.

    Then click the “Update” button on any post / page (not a product).

    Are the errors still displayed?

    Your webpages don’t appear to have any duplicates from other themes / plugins — the plugin appears to be unable to remove it’s own meta tags, which is a bit odd — it uses a simple PHP preg_replace() function, which should work just fine.

    Anyway, let me know the results after you’ve cleared / updated a post / page.

    js.

    malinky

    (@malinky)

    Hi Js,

    I cleared all cache(s) but the errors are still showing up in the admin (product pages, posts, pages)

    Plugin Author JS Morisset

    (@jsmoriss)

    Do you use a caching plugin? If so, which one, and could you turn it off to see if the errors go away?

    You also use an HTML optimization plugin / service. Could you disable it as well and see if the errors go away?

    Let me know if that fixes the issue. If so, I can install the same plugins in my test environments and try to reproduce the issue.

    Thanks,

    js.

    EGM.at

    (@egmat)

    Got the same issue: when saving a page or post all these notices are showing up. We are using NGFB Pro 8.7 on WP 4.3
    Seems that the combination with W3 Total Cache 0.9.4.1 causes the errors – if I disable it, the errors are gone.
    A fix would be great – or at least the possibility to show those notices only to admins, not for authors or editors.

    Plugin Author JS Morisset

    (@jsmoriss)

    W3TC is well know for it’s number of bugs, so I’m not surprised.

    The warnings need to be addressed — this could be by admins changing the plugin settings, or authors selecting / adjusting media options in the Social Settings metabox, featured / attached images, etc.

    These warnings are actually a good thing — they make sure you choose the correct image that’s large enough, with a correct aspect ratio, etc.

    js.

    Plugin Author JS Morisset

    (@jsmoriss)

    I ran some test with W3TC, and unless you use its “Line break removal” option, W3TC will insert newline characters while reformatting the HTML. I don’t know why a caching plugin would want to add unnecessary characters, thus increasing the overall page size, but I guess that’s a different kind of issue. 🙂 I’ll modify the NGFB meta tag filter to account for these un-wanted characters and release an update shortly.

    js.

    Hi JS,

    This issue has been resolved for me now. Thank you for your help!

    Cheers,
    Karen

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Possible conflict’ is closed to new replies.