WordPress.org

Ready to get started?Download WordPress

Forums

WPBook
Exceptionerror in WordPress by publishing posting (15 posts)

  1. rhelms
    Member
    Posted 3 years ago #

    WP-Bookversion 1.5.6

    I have build up an new facebookapplication that you suggested in the other ticket "pageview loops". When I publish a new post in wordpress I get this exceptionerror:

    Caught exception: Incorrect signature Error code: 104

    In the blogfanpage I have links that your plugin produces in earlier time.
    This links apps.facebook.com/badengospelt/2010/06/eine-hochzeit-schaut-ins-land-freiburg-gospel-choir-singt-bei-hochzeit-horben/
    actually redirects to the following:
    http://www.baden-gospelt.de/wordpress/?auth_token=b46c3965aa43f4da5b64851bf0ebb4db&next=http%3A%2F%2Fwww.baden-gospelt.de%2Fwordpress%2F2010%2F06%2Feine-hochzeit-schaut-ins-land-freiburg-gospel-choir-singt-bei-hochzeit-horben%2F%3Ffb_sig_in_iframe%3D1%26fb_sig_iframe_key%3De45ee7ce7e88149af8dd32b27f9512ce%26fb_sig_locale%3Dde_DE%26fb_sig_in_new_facebook%3D1%26fb_sig_time%3D1280825101.0681%26fb_sig_added%3D1%26fb_sig_profile_update_time%3D1267260185%26fb_sig_expires%3D1280829600%26fb_sig_user%3D100000774829898%26fb_sig_session_key%3D2.90BwMREVFqbzQ2bKsu1udw__.3600.1280829600-100000774829898%26fb_sig_ss%3D80aCHVgdQpLkrlJ4c0SIsg__%26fb_sig_cookie_sig%3Dfd5a5f2e1c48940eacba5f2aa27a8e04%26fb_sig_country%3Dde%26fb_sig_api_key%3De0251e97fd4bdb4583bd904a120da1f7%26fb_sig_app_id%3D136534616382539%26fb_sig%3D5e0f4ec1a629683d6326860d5469a3e4

    The result is that the blog is shown from the beginning like you type http://www.baden-gospelt.de. The loading doesn't break down yet.

  2. rhelms
    Member
    Posted 3 years ago #

    the testposting that I tried to post was not published in facebook. In the blog itselves it was published. Because it was only a test I've deleted it in the meantime.

  3. johneckman
    Member
    Plugin Author

    Posted 3 years ago #

    The incorrect signature code would suggest that you haven't updated your API Key and Secret to match your new FB application.

    Not sure why the redirects are sending you outside the FB iFrame, but it looks like you have a "post-authorize" url set up somewhere in your FB application settings.

    Want to add me as a developer on this new FB app so I can look at the settings, and update your WordPress WPBook settings with the new API Key and Secret?

  4. rhelms
    Member
    Posted 3 years ago #

    Now you are an additional developer of the new facebook-app called simply "Baden gospelt". I mean that in wordpress there is only requested for the apikey. The "post-authorize"-URL is empty.

    I'm a little bit confused because the error seems to be like the same that I have before I build a new facebook-app that you suggested some time ago. The only changed is the exeption 104-error and the fact that the redirected URLs doesn't break up loading yet while displaying the frontpage of the blog.

    If you want I can send you a screenshot of the wpbooksettings in wordpress.

  5. rhelms
    Member
    Posted 3 years ago #

    possible I have to activate the facebook-app. I found that the secretkey was wrong. I corrected that and now I get this error by publishing a post in wordpress:

    Caught exception in stream publish for user: The user hasn't authorized the application to perform this actionError code: 200

  6. rhelms
    Member
    Posted 3 years ago #

    Ok in the meantime I granted permissions for the facebook-app. In Facebook I was told to click on the link grant for userID. The link I've clicked on. Now in wordpress I get this error when I want to publish a new blogpost:

    Caught exception in checking extended permissions for page: User must have accepted TOS Error code: 200

    I don't find any key that enables that I can get tos-errors. I looked into the wordpress-settings and looked into the settings of the facebook-setting. I'm woundering and confused.

  7. johneckman
    Member
    Plugin Author

    Posted 3 years ago #

    Rupert - it seems like the new Facebook app has eliminated whatever issues you were having with the redirect loop.

    If I visit the Facebook application: http://apps.facebook.com/badengospelt/

    I see a set of recent posts. Clicking on the title of one of those posts loads its permalink, like: http://apps.facebook.com/badengospelt/2010/07/chormitglied-seiner-hochzeit-begospelt/

    Which loads perfectly well in FB, as expected - no weird redirects.

    The problem you're facing now, the "Caught exception in checking extended permissions for page: User must have accepted TOS" is because the app has not been added to the page in question - the page has not authorized the app.

    When you load the "check permissions" page - http://apps.facebook.com/badengospelt/?is_permissions=true - what do you see?

    Does it say something like:

    You are also listed as the admin of these pages:

    * Page name (numeric id), This page has NOT granted stream.publish permissions to this app. Grant stream.publish for this page.

    You can use the page IDs of any of these pages in the WPBook settings to publish to that page's wall.

    If you are the administrator of pages which do not show up in this list, you need to ensure you have added the application to the pages first.

    Does it list the FB page you are trying to publish to?

    If not, then that is the problem - for some reason adding apps to the page seems to have changed. It used to be that from the Application's profile page (https://www.facebook.com/apps/application.php?id=136534616382539) you could click on Add to My Page, and it would take you to the page and do the add.

    Now it seems to get stuck at the point of "add to my page" and stop there - that's something I will need to look into.

  8. rhelms
    Member
    Posted 3 years ago #

    Error seems to be a communicationproblem with facebook or within the wordpressplugin. I found a new backlink ceated on the personal wall and after clicking on it the blogpost was well embedded into the facebooklayout.

  9. johneckman
    Member
    Plugin Author

    Posted 3 years ago #

    Actually, that's not true - it just worked fine for me.

    Going to the Applications profile page: https://www.facebook.com/apps/application.php?id=136534616382539

    Clicking on "Add to my page" in the left column under the "Go to Application" button results in a popup listing pages to which I could add the app.

    I clicked on one of those pages (https://www.facebook.com/pages/WPBook/44062579871) and then "close."

    Then I went to that page, and went into "Edit page" mode.

    I see "Baden Gospelt" listed there as one of the applications on the page, and click the "edit" button associated with that app, which takes me to a url which looks like this: http://apps.facebook.com/badengospelt/?fb_page_id=44062579871

    That page loads with a message that says something like "you've now added the application to your page" - basically a success message.

    Have you done this process for the page to which you are trying to publish?

  10. johneckman
    Member
    Plugin Author

    Posted 3 years ago #

    rhelms - any update here?

    If you're still having trouble, please try updating to WPBook 2.0.2 and following the detailed instructions for settings in it.

  11. rhelms
    Member
    Posted 3 years ago #

    I've just updated to wpbook 2.02. Backlinks in the personal wall are not the problem. But with the fanpage I've still problems inside wordpress (TOS-error)

  12. rhelms
    Member
    Posted 3 years ago #

    That is the message I get back in wordpress after publishing a new post:

    Caught exception in checking extended permissions for page: User must have accepted TOS Error code: 200

  13. rhelms
    Member
    Posted 3 years ago #

    After updating to 2.0.2 I've in addition warnings for wrong headerinformations relating to wpbook.php. I tried granting new permissions in facebook for wpbook 2.0.2 and also in the facebookgrantingpage I was informed about headerproblems in wpbook.

  14. rhelms
    Member
    Posted 3 years ago #

    plugin is disabled now because of possible blogcrashes.

  15. johneckman
    Member
    Plugin Author

    Posted 3 years ago #

    rhelms - sorry, late night hacking on weekends got the better of me.

    There's a 2.0.3 now, 2.0.4 later tonight or tomorrow.

    2.0.3 fixes the header information bug, 2.0.4 will fix the "publish meta was yes" referred to in another thread on this forum

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags