NGFB warning messages appear at the top of pages / posts after update

  • Resolved n1ck0

    (@n1ck0)


    9 years ago

    Hello,

    We are using NextGEN Facebook (NGFB) Version 8.1 (free version) on a WordPress 4.2 website.

    I updated the NGFB plugin on 23/4, and then again to 8.1 with another update on 24/4.

    Ever since the 23/4 update, 15 NGFB warning messages appear at the top of pages and posts as per below:

    • NGFB Warning: Possible conflict detected – your theme or another plugin is adding a meta name=”description” HTML tag to the head section of this webpage.
    • NGFB Warning: 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 Warning: 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 Warning: 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 Warning: 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 Warning: 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 Warning: 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 Warning: Possible conflict detected – your theme or another plugin is adding a meta property=”article:section” HTML tag to the head section of this webpage.
    • NGFB Warning: Possible conflict detected – your theme or another plugin is adding a meta property=”article:published_time” HTML tag to the head section of this webpage.
    • NGFB Warning: Possible conflict detected – your theme or another plugin is adding a meta property=”article:modified_time” HTML tag to the head section of this webpage.
    • NGFB Warning: 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 Warning: 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 Warning: 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 Warning: Possible conflict detected – your theme or another plugin is adding a meta itemprop=”name” HTML tag to the head section of this webpage.
    • NGFB Warning: Possible conflict detected – your theme or another plugin is adding a meta itemprop=”description” HTML tag to the head section of this webpage.

    I haven’t seen this warning before and I am not aware of changing anything that might bring on such a warning.

    We are not using another SEO type plugin that inserts this data on the page in the front end.

    When I look into the page source in the front end, I can only see one instance of each of the above NGFB fields.

    Any ideas what might be happening?

    Thanks in advance.

    The website address is: agilityproperty.com

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

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

    (@jsmoriss)

    9 years ago

    Hm. Try clicking on the “Clear All Cache” and “Check for Update” buttons on any NGFB settings page. That should clear out any old transients objects (from previous versions). Let me know if that fixes the problem.

    Thanks,

    js.

    Thread Starter n1ck0

    (@n1ck0)

    9 years ago

    Thanks for the help. The “check for update” on NGFB settings pages was greyed out so I couldn’t press that – but I did press “Clear All Cache” on those pages. It said it cleared the cache. But when I went back to a page or a post those 15 errors still appear though.

    So then I thought maybe its to do with the caching plugin W3 Total cache that we use so I deactivated that – and whalah – the 15 NGFB warning messages disappeared. Reactivating the cache plugin brings a return to the 15 NGFB warning messages. So perhaps we have a conflict between the 2 plugins? Do you think that could be the issue?

    I have kept the caching plugin on as we need that to help with website performance.

    Do you know of any tricks on how to get NGFB and W3 Total cache to play nicely together?

    Thanks for your help.

    Plugin Author JS Morisset

    (@jsmoriss)

    9 years ago

    Try clearing the W3TC cache — that should clear up the duplicate meta tag errors. I’ve also added some code in the next version to clear the cache automatically when activating the plugin (including the W3TC cache). 😉

    js.

    Thread Starter n1ck0

    (@n1ck0)

    9 years ago

    Thanks for the continued help JS.

    I clicked the “empty all caches” button in the W3 Total Cache dashboard this morning – and W3TC said “All caches successfully emptied.”.

    But when I go back in to edit a page I still see those 15 warning errors at the top of the page.

    I think I must be doing something wrong / be missing something.

    Any other ideas?

    That new code addition sounds great.

    Thanks JS.

    Plugin Author JS Morisset

    (@jsmoriss)

    9 years ago

    Can you provide a permalink URL to an example post/page?

    Thanks,

    js.

    Thread Starter n1ck0

    (@n1ck0)

    8 years, 12 months ago

    Thanks JS. I can but I think it appears to be sorted now.

    In between your much appreciated follow-ups I reactivated the Cloudflare extension of W3 Total Cache (I turned it off while I was waiting on an answer to a dns related question) – and low and behold now that Cloudflare is active again, the warning messages are no longer appearing. Wierd but wonderful news. So I think its aok now. I will keep an eye on it.

    Thanks for the excellent service.

    Plugin Author JS Morisset

    (@jsmoriss)

    8 years, 12 months ago

    Ah, yes, the cached info on CloudFlare must have been outdated. Glad to hear everything is working well now. 😉

    js.

    Thread Starter n1ck0

    (@n1ck0)

    8 years, 12 months ago

    That’s a trap for a WP / CDN caching novice like me! Thanks again.

    Plugin Author JS Morisset

    (@jsmoriss)

    8 years, 12 months ago

    No problem. 😉

    js.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘NGFB warning messages appear at the top of pages / posts after update’ is closed to new replies.