Viewing 5 replies - 1 through 5 (of 5 total)
  • I agree.. shouldn’t Fb update their own plugin?

    Got the same issue. I went on to FB dev and check page source and url is correct so not sure why this notice is coming up in the console. The messenger pop up is no longer visible on our website.

    This is due to a conflict with another plugin that uses Facebook SDK.

    Thing is they discontinued support for chat using the sdk.js file and now you have to use xfbml.customerchat.js file instead.

    The xfbml.customerchat.js file is the exact same file as sdk.js + the code needed for chat.

    What is happening is when another plugin loads the older sdk.js, the conflict causes the new one not to load.

    I had a similar problem, all I had to do is to edit the plugin that was using sdk.js to use xfbml.customerchat.js instead so both the chat and the other plugin (in my case WP Save to Facebook) use the new file.

    Let me know if you need further explanation.

    Thread Starter Jacob Dubail

    (@jacobdubail)

    Thanks @yward!

    I’ve updated the code so only the xfbml.customerchat.js file loads. My challenge is that now I don’t get our fb-like button or customer chat loading. We no longer load sdk.js anywhere on the site. Any ideas? The fb-like code looks like:

    <div class=”fb-like” data-href=”<?php the_permalink(); ?>” data-layout=”button_count” data-size=”large” data-action=”like” data-share=”false” data-show-faces=”false”></div>

    Can you tell me which other plugin are using with this one?
    You should leave this one unedited.

    Tell me what’s the name of the other plugin, and I’ll tell you what to do exactly.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘No longer part of the main FB SDK’ is closed to new replies.