Twitter stream module breaks homepage loading

Tiago,
First off, I sincerely apologize for my delayed response. We've been very busy finalizing and releasing JFBConnect v7. I've also been out due to some personal reasons.

With that said, I had some time to investigate further today and will be working on this much more readily going forward. On your site now, if I try to login with Twitter, I get the same error you mention above:

The request token for this page is invalid. It may have already been used, or expired because it is too old. Please go back to the site or application that sent you here and try again; it was probably just a mistake.

You mention above that you did see a user in the Usermap area at one point. The authentication isn't working for you anymore now, and no users are showing up in the usermap area, correct?

I did try to take your Twitter API & Secret key and use them in a development site of ours. The keys worked just fine on that site, so the keys and setup of your Twitter Application are correct. It's something more on-site that we need to narrow down.

With that said, I was unable to FTP into your server. When I tried, I'd always get the following error:

Status: Connection attempt failed with "ETIMEDOUT - Connection attempt timed out".

That means I can't even connect. It's not a credentials issue. Without FTP, it's difficult to narrow things down further.

Once thing I would recommend is trying to upgrade to JFBConnect v7. There are quite a few updates in that release, and it can't make things worse I tried to install on your site, but got an error about the PHP file upload size being too small, so I couldn't.

Please try moving to JFBConnect v7 and/or help me understand what's wrong with the FTP connection, and we'll gladly work to get you going. I'll definitely be more responsive going forward.

Thanks,
Alex

Alright.. I re-read your Private Message and missed that FTP was over SFTP/SSH. With that, I was able to login and do some deep investigation. What I found is something I've never seen before. Ultimately, it seems like there's some sort of outgoing proxy that was adding additional information to the responses from Twitter. I was ultimately able to fix the issue with a minor code change and now Twitter authentication does work on your site.

I've added the fix to our bug tracker and it should be in the next release (v7.0.1). v7 did just come out, but it does not have this fix. If you want to upgrade to take advantage of some of the features in that release, we can provide you with the minor code snippet you'd need to add.

Please test and let us know how it goes. I really hope things go smoothly for you now and thanks for your patience!

Alex

I'm very happy to hear that seems to have resolved your problem. It was a very unique issue we hadn't heard of. Without FTP access, we wouldn't have ever found it.

As noted, this should be in the 7.0.1 update. If you want to upgrade to 7.0 now, you should make the following change in the /components/com_jfbconnect/libraries/joomla/http/transport/curl.php . Around line 167, you'll see:Right *before* that line, add the following lines:I hope that helps,
Alex