I've done all the required steps in Twitter Dev tools to set my blog up as an app to use Twitter tools. When I post it's still not sending my posts to Twitter. I made the access level read-write, inserted the consumer key and secret, and access token and access token secret, and updated the plugin settings. Still nothing. I consider myself an advanced WordPress user who knows code very well. What am I missing here?
Twitter Tools
can't seem to get it to work (32 posts)
-
arwen54
Posted 1 year ago # -
aban
Posted 1 year ago #same here... when I upgraded to version 2.4, latest tweets didn't show up (remains the last tweet before upgrade)...
-
spidermann
Posted 1 year ago #I have found that if you send a Tweet from the blog backend interface before publishing your post, it will then tweet it.
Backwards, but it seems it needs that extra authentication sent before it will read again. Really hope the devs get back into it and fix this one issue. I know it is most likely the new oAuth from Twitter causing the issues.
-
Sivanesh
Posted 1 year ago #the error seems to be because of wordpress 3.0.1
-
wphelpcenter
Posted 1 year ago #Sivanesh -- Twitter Tools 2.4 is working fine on 3.0.1
Spidermann -- That's interesting, we'll keep that in mind when testing to see if it can lead us to a bug.
aban - Have you tried the Reset Tweet Checking button located under Settings -> Twitter Tools?
-
The plugin is NOT working. It shows my recent posts in the sidebar, but that is it. If I try to make a tweet from the backend or from the sidebar, I get this error: "Oops, your tweet was not posted. Please check your blog is connected to Twitter and Twitter is up and running happily."
I am connected to twitter and it is up and running 'happily'.
I loved the idea of having it say the tweet came from my own 'app', but if it won't work, then there is no point in me keeping this plugin when there are others out there that will work, despite not having that lil feature. :/
please fix.
-
could this be due to the new rules Twitter has enacted for apps?
-
Rev. Voodoo
Posted 1 year ago #I'd definitely think so
This plugin has worked perfectly for me for a long time now, it quit after the upgrade that was made for that purpose
-
Yeah, Twitter just set a new rule so that all apps must use OAuth, etc. I don't know what the plugin uses. All I know is that I have the most recent version of WordPress and this plugin and the plugin is not working. So it looks like the dev needs to make an update to the plugin soon to keep users.
-
Posted 1 year ago #The plugin just had an update to work wit the new twitter rules.
It's working for some people.
It half works for me. I can post to twitter from sidebar. And My new posts go to twitter.
But nothing comes in. No tweets are getting pulled into my database since the upgrade.
So yeah, it definitely looks like it has some kinks to be ironed out
-
I too am having problems with the tweets coming in and showing in the sidebar. They were showing. I deleted a test tweet I made via twitter itself and that deleted tweet still shows in my sidebar. I did go into the settings and told it to refresh the tweets, etc.....still shows the deleted tweet.
-
Posted 1 year ago #Yup...something is blocking the database from getting any updates from twitter
-
morrisondon
Posted 1 year ago #Like others here, I followed all the steps to use OAuth, but disappointingly, TwitterTools no longer works.
When I click on "Connect to Twitter" on the TwitterTools Options page, I get this error meessage:
Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /content/StartupHostPlus/i/t/it4arts.org.uk/web/WP/wp-content/plugins/twitter-tools/twitteroauth.php on line 19
-
Posted 1 year ago #okay, I didn't want to give up on this great plugin so I'll tell you what I did. Initially when I set the app up I only gave it read access and when I updated it to read-write access I didn't know that I needed to generate a new consumer key and secret and a new access token and secret. So today I deleted the app and started over and I'm pleased to report that Twitter Tools now works perfectly!
So for those of you having trouble...start all over again...make sure you assign read-write access to it!
-
Just wanted to state that version 2.4 works fine in my blog running version 3.0.1. I simply followed the directions provided to get OAuth working.
I was using the old Twitter PHP API for some other scripts on my website and I had to change those over to the newer OAuth method as well. Apparently August 31st was the cut-off date for the older method to still work.
-
brianpurkiss
Posted 1 year ago #When I click on "Connect to Twitter" I get this error
Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /homepages/29/d293799614/htdocs/boldperspective/tweets/wp-content/plugins/twitter-tools/twitteroauth.php on line 19
-
Posted 1 year ago #@wphelpcenter: I did but nothing's happened. Well, I don't have a problem while I had OAuth (I followed the instructions and doing fine), but the tweets still won't show up on my blog...
-
eladear
Posted 1 year ago #I've retried, resetting tokens. It says "Yay! we connected to Twitter, " but no post is retrieved on twitter.
-
Posted 1 year ago #Resolved the problem too. I did exactly as arwen54 said. Delete the Access Token app (http://dev.twitter.com/apps/...), register anew and it should work.
-
veronicamae
Posted 1 year ago #I don't know what I'm supposed to put in the Application Name or Description box when registering the app. Every Twitter Tools-type name I put in has been used. The "easy" step-by-step instructions don't say what to put in every field, so, I'm completely lost.
-
mattwalters
Posted 1 year ago #Verionicamae -- This should help explain the application name for you -- http://tinyurl.com/ttappname
Kahil -- The latest version of Twitter Tools was released specifically for the Oauth change that Twitter.com put in place. If it's still not working for you after following the other possible fixes mentioned in this thread (such as deleting the app and recreating it making sure read/write access is enabled, etc), then I suggest you contact Twitter. Their API doesn't really return very useful error messages with this so it's been difficult tracking things down. I will say though that it is working for MANY other users, so running around the forums screaming it isn't working at all and that the dev needs to update it is false and neither accomplishing much nor helps anyone.
-
hm2k
Posted 1 year ago #I too am seeing this error:
Oops, your tweet was not posted. Please check your blog is connected to Twitter and Twitter is up and running happily.
Do we have a fix yet?
Cheers.
-
Posted 1 year ago #I see this:
$connection->[http_header][status] => 401 Unauthorized
Although, there is no explanation for this.
-
cybersnac
Posted 1 year ago #I am still unable to get this to work and have done all of the following.
1. disabled the plug-in, un-installed it and confirmed that the folders on my web server were deleted. Then re-installed the plug-in.
2. Deleted my registered application on dev.twitter.com/apps and confirmed when registering a new app that the settings were all configured properly and that I received a new set of consumer key/secret and access token/secret.
3. re-entered these new sets of keys into the plug-in configuration page.
I still get the error: Authentication Failed. Please check your credentials and make sure Twitter is up and running.
-
theduna
Posted 1 year ago #Im not sure about your problem guys, but for me problem was with tweet length. It was worked with <140 and did nothing with >140. I think you guys should try to activate bit.ly posting and it might work for you. Just check if your tweet more than 140 symbols.
-
Posted 1 year ago #Length isn't a problem here. I tried simply "testing" and it didn't work either.
I am on the understanding that the issue is with oauth which is why it's returning an unauthorised error 401.
-
47ford
Posted 1 year ago #@morrisondon & @ brianpurkiss you guys may have found this already but for someone new maybe it will still be relevant.
If you get this error:
Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /{your local server path}/wp-content/plugins/twitter-tools/twitteroauth.php on line 19
It has been reported to a PHP4 issue and upgrading to PHP5 will fix it. I have found also that while your host may list PHP5 as available/installed some host (Lunarpages for example) are running PHP4/PHP5 both and you need to verify your .php files are being processed under PHP5.
For Lunarpages customers this can be done by logging into cPanel and choosing the "PHP Configuration" near the bottom. Make sure to choose "PHP 5" in the drop-down box on the resulting page (mine was set to "System Default").
If your host is unwilling/unable to upgrade to PHP5 I would recommend finding a new host. FWIW, I have over all been happy with Lunarpages YMMV.
-
ajeeshag
Posted 1 year ago #Oops, your tweet was not posted. Please check your blog is connected to Twitter and Twitter is up and running happily.
pls fix it this error -
Posted 1 year ago #After updating everything today I'm still seeing this error when trying to submit a tweet:
Oops, your tweet was not posted. Please check your blog is connected to Twitter and Twitter is up and running happily.
I've checked and confirmed that the blog is connected and twitter is up and running.
Can the author please advise further?
I have attempted to contact alexkingorg/crowdfavorite yet I don't seem to get a response.
Has this project been abandoned?
-
tommybiro
Posted 1 year ago #Hello
I also installed Twitter Tools but I dont know why my blog posts are not sent to twitter. I have the actual WP version in German and the actual version of twitter tools installed. I also set up and checked again the Access and Consumer numbers at the settings in Twitter and WP. Is somebody here able to support me with the setup? I can also provide printscreens or more informations if needed. Thanks in advance for your help
Tommy
Topic Closed
This topic has been closed to new replies.
