Quote:
Originally Posted by pete_brady
check CurlSSL is installed, and also make sure your twitter app was set up R&W enabled from the start rather than read only then enabled for read write - seems strange, but appears to have made a difference for me. Set another up from scratch to test if necessary.
|
I would advise that you heed pete's advice, as we spend a couple of fun-packed days over at Wolfshead Solutions tracking his issue down (he is a current vBulletin.org Hacks Support subscriber).