Twitter docs updated?

Twitter has updated the look of their app area, but all the settings are pretty much the same. If there's a setting you are confused about or can't find, please let us know what it is.

As for the Bad Token message.. there's a couple odd things going on. First, when I click the login with Twitter or LinkedIn, the JFBConnect code calls a link on your site like:The t=1, return=null and nullindex.php are all incorrect values. I'm unsure where those are coming from.. but LinkedIn actually still works (strangely) yet Twitter throws the Bad Token error.

I see a lot of 'optimization' stuff running in the code to minimize and re-arrange Javascript. I'd recommend trying to disable that to see if it fixes things. There is a certain order that our Javascript code needs to be placed on the site to ensure it executes properly and it's possible the optimizations are causing issues there.

Beyond that, normally, a Bad Token Error indicates a couple other server problems, primarily that your servers' time is way off. That's something to look into if you still have issues after testing with the optimizations turned off.

I hope that helps,
Alex

Sorry or the delay. You should be able to run JFBConnect with optimizations enabled. However, while debugging, we absolutely recommend disabling them to ensure that they aren't causing issues as it removes one more possible problem area.

As for debugging, the steps we'd recommend are:
* Verify that the time on your server is accurate to GMT/UTC time. Twitter is extremely picky in making sure that requests are sent within a very short timespan of the current time. If your server time is off by a few minutes from UTC time, then those requests will get rejected.
* Double check that you have followed all steps of the Twitter configuration guide, with special attention to step 4, for the OAuth Callback URL(s)
* Disable SEF URLs (temporarily) to see if authentication works.

Please let us know how that goes, and if you still have issues, we'll gladly help further.

Thanks,
Alex

The Twitter documents are as up to date as we can make them currently. The issue with Twitter, and all social networks, is that they roll out new admin interfaces regularly and they usually do it in a staged process by rolling it out to waves of accounts at a time. It's very possible that you are seeing a different interface than what is in our documents. Unfortunately, because you see it, doesn't mean we do in our development accounts.

Our guides always strive to give field names and details to help guide you through any inconsistencies. However, if there's any particular place you are getting stuck, please let us know what that inconsistency or inaccuracy is and we'll gladly help provide an answer.

Finally, your developer should not have to place any Javascript anywhere. JFBConnect handles this by interfacing with Joomla itself and has your template render the Javascript in the correct place. This is why we recommend disabling optimizations that may be moving things around. Then, test and verify things work, and then re-enable those optimizations and check again.

Thanks,
Alex