Auto Tune not working

Regarding Autotune:
1. Go into Autotune and click on the 'Facebook App' tab. At the top click the refresh button and then go back to the Start page to see if the subscription is still listed as expired.
2. Double-check on sourcecoast.com > My Account > My Profile page to verify that the subscriber ID is the same one that you have entered.

My major problem is that after the update it's not possible to login to my website with Facebook account... it just redirects to index.php?option=com_jfbconnect&task=authenticate.login&provider=facebook&return=(some token) and hangs there forever

I just tried logging in on Facebook on your page and received a white page. This is usually caused by a fatal error in PHP. Can you turn on error reporting in the Global Configuration so that we can pinpoint the cause of the error?

-Melissa

thank you for your reply but there's something weird with the Subscriber ID. If I login to your website with a username/password I'm getting one Subscriber ID... then if I login again via my Facebook account (this is how I was registered here) I'm getting a different Subscriber ID (shorter) and that one is working fine for me. Both logins lead me to the same profile and the same subscribtion says active... Anyway this is solved now.

That is very, very bizarre. We haven't heard of that before and if you're logging into the same account, there should be no difference in the subscriber ID created. Additionally, all IDs should be 32 characters. One may look shorter though if it's using smaller letters lll vs OOO.

I'm glad you found the 'right' way to get your ID, but if you want us to investigate more, we gladly will.

My second issue is also solved. Seems that you're using __DIR__ variable from PHP 5.3 but my website is running with PHP5.2 - so far it seems that this is the only 5.3 specific feature that you're using so I fixed that. The Facebook login is working as expected now

Wow! That is crazy! We had no idea that that was a 5.3 specific feature. We definitely mean to support 5.2, as that's all that's required for Joomla 2.5. I'm shocked that no one else has run into that issue since we added __DIR__ to that file in a release in September last year. Either many more hosts have upgraded from 5.2 than I thought, or some sort of shim is available to make it work.

Either way, I'll look into getting that fixed for the next release.

Thanks for the feedback, and glad you got things going,
Alex