Support » Plugin: Twitter posts to Blog » Plugin is dead – twitter api killed

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author badbreze

    (@badbreze)

    Twitter api 1.1 require oauth, i’m trying to implement oauth on my plugin, sorry for the inconvenience

    Great!

    Sorry I didn’t realize the search api required oath.

    I leave this topic open so others will know instead of reposting the same problem again.

    Plugin Author badbreze

    (@badbreze)

    Update your plugin and follow new installation instructions

    I got this error in the log:

    PHP Fatal error:  Cannot use object of type stdClass as array in /../wp-content/plugins/twitter-posts-to-blog/functions.php on line 24

    Perhaps the oauth is not configured properly.
    The only thing i can see is it shouldn’t be “Read Only’ or maybe the app requires a callback url? I double checked all the tokens and keys.

    Plugin Author badbreze

    (@badbreze)

    you have configured all 4 tokens?

    Yes – re-entered
    Consumer Key
    Consumer Secret
    Access Token
    Access Token Secret

    BTW in your config page, Access Token Secret is mislabeled Consumer Secret.

    Do I need a callback url or to change the app from read only?

    In a quick look at the hooks from this in your code I didn’t see any errors.

    Yes – re-entered
    Consumer Key
    Consumer Secret
    Access Token
    Access Token Secret

    BTW in your config page, Access Token Secret is mislabeled Consumer Secret.

    Do I need a callback url or to change the app from read only?

    In a quick look at the hooks from this in your code I didn’t see any errors.

    Plugin Author badbreze

    (@badbreze)

    fixing bugs and finding solution for you

    Plugin Author badbreze

    (@badbreze)

    My application is in “read and Write” and is working for me.

    this is my configuration
    http://i39.tinypic.com/ohv91l.png

    try update the plugin to 1.0.2 and set read and write

    Yes, great and thanks. It’s working.
    Just changed read to r-w, no callback or sign in with twitter.

    You should add the above image to your plugin!

    Clarifying 3rd party configuration to users will save you lots of support time.
    Configuring a twitter app is now the barrier to someone enjoying your plugin.
    You want to make it as easy as possible to do it.

    Thanks again.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Plugin is dead – twitter api killed’ is closed to new replies.