Topic-icon Logging Out issues

Active Subscriptions:

None
14 years 4 months ago #18133 by fb_506903577
Hi

I have recently upgraded my site from Joomla 1.5 to 1.7 and re-purchased JFBC as it's always been a really useful part of my site.

Unfortunately I'm having issues with the automatic login function - when I set it to "Auto-Login of Facebook Users: Yes / Logout of Joomla Only: No" it's impossible to logout if you're logged into facebook as the logout button sends you back to the homepage with "Automatically logging you in with your Facebook credentials" displayed. If you log out of facebook from the facebook site, or you are just logged in without using facebook, you get a 500 error on attempting to logout and the message "View not found [name, type, prefix]: jfbconnect, html, jfbconnectView" from the page /index.php?option=com_jfbconnect&task=logout&return=Lw==

When I set it to "Auto-Login of Facebook Users: No / Logout of Joomla Only: Yes", it seems to allow you to logout with no problems.

I'm not using any login or logout redirection, I have the latest version (4.1.1) and I'm using the SCLogin module with the Joomla registration component (I have Community Builder on my site, but I've not yet set it up to work with the JFBC CB plugin). Site address: www.mkfm.com

Any help would be greatly appreciated.

Chris
The topic has been locked.
Support Specialist
14 years 4 months ago #18137 by alzander
Replied by alzander on topic Logging Out issues
Chris,
There's currently a bug with Facebook's Javascript library that we include, and utilize heavily for functionality. It's not properly erasing the user's cookie upon logout, and therefore, they appear to remain logged in (even when they are actually logged out of Facebook). We're following the bug-report for this and it's in the "Fix Ready" state. Hopefully, they'll push out the fix over the next few days and it will fix this problem.

Until then, we recommend disabling the Auto-Login feature of JFBConnect.

We're also investigating some changes we can make for a possible 4.1.2 release. However, they're still being evaluated and are more of a 'if-necessary' approach, but will push it out if their fix doesn't work and we're able to test our changes without issue.

Sorry for the problems, and thanks for being a long-term supporter!
Alex
The topic has been locked.