I have it installed. but nothing is ever sent to twitter.

I have it set to read, write and direct message

any ideas?

I cannot seem to get this to work. I have run the diagnostic plugins, and both come back with the result "NULL".

Any ideas on how to resolve this?

Thanks in advance.

To both previous: Just remember two things when setting up for the first time.

1. Make sure you can tweet manually.
2. Don't try to use any shortening until it's working well.

hey Mosh u have time migrate this plugin to new api? this community will greatly appreciate it.

OMG is that why Trillian isn't connecting to Twitter today? a "point" release that breaks all prior versions???

Mosh clearly doesn't get around here much, so if this has stopped working we might be in big trouble. Maybe someone can track him down at his own forum. If nothing else, at least maybe convince him to mark this code "reusable" so someone else can fix it.

PS Confirmed broken. I see no tweets from my forum since yesterday though there have been new threads posted. :(

I sent a message to Mosh and do the same message, to update this excellent plugin and whether to donate to the person to do the update, I'll be the first to make my donation. and yes, this is not working today! hope some coder who can do the job and also give back through donations.

is confirmed, the plugin from the day yesterday stopped working on my forum, please someone make update the creator so I too would make my donation to this worthy cause.

I thought it was just me.

Don't think Mosh will be supporting this anytime soon

This is in his sig:
Get well soon Mosh!!

Anyone else able to migrate this???

You can get the two updated OAUth modules from https://github.com/abraham/twitteroa...r/twitteroauth

Place them in includes\twitteroauth.

Also, in the vBulletin 2 Twitter: Thread To Twitter plugin, you will see four lines near the end as follows:

// if ($twitterApiLimitCheck->remaining_hits > 0)
// {
$twitter->post('statuses/update', array('status' => $tweet));
// }

Comment the three lines out as I have above.

Warning, I do not know PHP. I just guessed that this would work, and it does.

hi QFIT I have done what you have stated in your post and I have not worked. Maybe you did something more or not?

do you have cURL enabled on your server?

Simon Lloyd Yes CURL is Enable in my server everytime.

Nice Work again! Thank very Much QFIT I reinstall the new files and modifying with your steps and now it works, at first I worked for was editing across the plugin, now it works, Thank you!

Thanks.
Will give it a try tonight!!

Not for us. No tweets have gone out since I did this, though a manual tweet just worked. Also, when my co-admin tried to "check the box to post simultaneously to facebook", he was taken to the github page for oauth.

Mine didn't work either.
I was taken to the this page: https://github.com/abraham/twitteroa...itteroauth.php
but with the new thread url.

Hey guys, mine took 24hrs but is now posting again!

Not ours. Still nothing. Almost fooled me though when my co-admin manually tweeted a thread, but it wasn't shortened and he admits to doing it manually.

I also made the changes but still not posting. Has anybody a working solution? using vb4.2.1

work on my forum vb 4.1.12

Works perfect, many thanks!! :)

Mine now works.
Not sure if you've done the same thing I did, but my attempt to download the two twitteroath files failed. I ended up with a HTML code of the page instead of the php code.
i copied and pasted the php code into the 2 files and it now works.

Thanks QFIT

Worked for me when I used http://example.com/forum/ but after I changed to https://example.com/forum/ it stopped working. I have SSL certificate.

Any help?

I have just tried but it takes me to the github page :(

Fixed it, make sure you copy and paste the raw code from github rather than right clicking and saving.

:)

Are you saying the file names are different? What should it/they be?

its not working anymore. it does not post to twitter anymore.

You really aren't paying attention. :)

But I just confirmed that a right-click save saves some odd HTML file, not the correct PHP file. So I've copied and pasted and re-enabled the mod. I'll post back if it's working.

Edit: Yes, it's working and no redirects to github.

I tried to get it to work just making changes. That wasn't good enough. When I finally realized I should just make a new app on Twitter Dev, it worked flawlessly.

So for those still having issues after the great updates provided in the last page or two, try it with a brand new app (not just editing) and you will hopefully get better results.

Thanks for posting the fixes everyone. It took about 24 hours but is now posting again.

I did the same process from the other day on my racing forum now to the offroading forum, but not getting the same results.. I made the 2 auth file changes, commented out the code, and setup a new app just for the sake of argument.

Last time it worked instantly. Posted a thread 30 seconds later and it was good. This time, nothing.

Strange as hell since they've both on the same dedicated server and running similar builds of plugins and whatnot.

Not quite understanding how to get this working again after reading the last couple pages of this thread.

I'm using 4.2.1, and this mod isn't posting to twitter anymore.

What exactly do I need to do to get this working??

So I cleared the tokens a second time in the new app, presto.. So strange.

go back a page, follow the post with the github link.
update those 2 files.
go into your plugins settings (not manage, the one where you can edit stuff) and comment out the 3 lines mentioned.

if that's not enough i ended up.
making a new twitter app
connecting vbulletin to the new app

i made all the changes stated above its still not posting to twitter for vb 4.2.1

You are sure that there are not special characters in the title?

I'm using it on v4.21 and it's working on plain title posts

Worked like a charm.

I'm having the same problems,

Plus I get error messages and duplicate post warnings.

That's pretty vague. What error messages and from whom? What warnings and from where? Was yours working before the recent oauth change?