WordPress.org

Ready to get started?Download WordPress

Forums

Facebook Comments
[resolved] FB July 2013 Breaking Changes app compliance (9 posts)

  1. hunter44
    Member
    Posted 1 year ago #

    I just got an email from The Facebook Team regarding the app I use for the Facebook Comments plugin (I'll call it "My FB comments App"). The email says my app:

    "has not enabled the migration for the July 2013 Breaking Changes.
    Once you have confirmed your app is compliant or unaffected by the July 2013 Breaking Changes, set the migration setting to "Enabled" in the Advanced section of the App Dashboard. This will apply the July 2013 Breaking Changes to your app and prevent you from receiving future alerts about these changes.

    "My FB comments App", is currently using the following deprecated features:
    Social Plugins (Like Button, Like Box) without absolute URL's in their href parameter.
    These changes will be permanently enabled for all apps in 72 days on Wednesday, July 10, 2013.
    You can view this and other Developer Notifications related your app, "My FB comments App", in the App Dashboard.
    Thanks,
    The Facebook Team

    What do I need to do?

    Thanks so much!!

    Emily
    http://roadslesstraveled.us

    http://wordpress.org/extend/plugins/facebook-comments-plugin/

  2. photoMaldives
    Member
    Posted 1 year ago #

    Hi Emily

    I've just received this exact same thing, too - googled for info and ended up here ! Any (simple) advice would be gratefully received because I haven't got a clue what to do !

    The message comes with the words FIX NOW, which look tantalisingly like a button to take you to a wizard to fix the problem ... but alas it's just highlighted text and not a button !

    The EDIT MIGRATIONS button takes you to the normal Apps - Advanced Settings page, with no clue on what to do, and the text within the message does not help in identifying the changes needed.

  3. photoMaldives
    Member
    Posted 1 year ago #

    Well, a bit more googling to find the answer is in fact incredibly simple !

    Have a look here for a useful screenshot (thanks, Gautam Doddamani)-
    http://www.revthatup.com/resolve-facebook-app-february-2013-breaking-changes-issue/

    This is from February, so just look for "July 2013 Breaking Changes" and click the ENABLE radio button - sorted ! :)

    Bit weird that FB doesn't automatically apply this though.

  4. hunter44
    Member
    Posted 1 year ago #

    Thanks for all that googling, photoMaldives!!! Very helpful.

    I'm also hoping for confirmation from Alex Moss, the author of this awesome app, that nothing further is needed for July 2013...

  5. theSarayiahpost
    Member
    Posted 1 year ago #

    Hi
    I am not so sure the answer is that simple (but if it is then great!)
    I use the FB Like and Share button on my relationship and lifestyle blog http://www.theSarayiahpost.com and am geting the same message when I log into FB.

    It says I am using the following deprecated features:

    "Social Plugins (Like Button, Like Box) without absolute URL's in their href parameter.

    But that implies we need to change the url to absolute to make it work after July 2013. Just telling FB that you have enabled the changes needed in the Advanced settings is not going to make the Like and Share buttons work if we need to actually change something in the code.

    So help would be most gratefully received and if we need to change the code how and where do we do this?

    Thank you.
    Kind regards

    Isaac

  6. Jamesdf5
    Member
    Posted 1 year ago #

  7. Jamesdf5
    Member
    Posted 1 year ago #

    In fact you just have to do what it says. Click the enable option. The facebook plugin doesn't use relative URLS. It will still work

  8. theSarayiahpost
    Member
    Posted 1 year ago #

    Thank you Jamesdf5. Much appreciated.

  9. Alex Moss
    Member
    Plugin Author

    Posted 1 year ago #

    as Jamesdf5 mentioned the plugin uses the_permalink() so the plugin is (and always has been) compatible with the July 2013 update

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic