Login problems on mobile devices

What kind of caching do you have enabled? If you're using browser caching, you shouldn't be. Various extensions, templates or the System - Page Cache plugin that comes with Joomla can enable this. Browser caching should not be used on any site where authentication is performed.

If that doesn't help, do you see the same issue if the use logs in with Joomla credentials as well, or is this just with social authentication?

Thanks,
Melissa

Your site absolutely has some sort of browser caching enabled. If you go to the site and click the refresh button in a browser, a 304 response code is being returned:

A 304 code tells the browser that it should load it's previously cached HTML for the current URL. So, even if a user has just authenticated, the non-authenticated HTML will be displayed by the browser. We can't fix that in JFBConnect. Conservative caching in Joomla will *not* return 304 headers. You must be using something else, either from a Joomla extension (like the Joomla - Page Cache plugin) or in your server itself (nginx looks to be your server software, which can implement browser caching on it's own).

I hope that helps narrow things down, but if you get the 304 response codes removed and still have issues, just let us know.

Thanks,
Alex

It's not caching of PHP files that's the problem. It's the directive to tell browsers to cache the content and respond with 304 codes telling the browser to use that cached data. That's different than optimizing and caching the execution of PHP files.

The issue will present itself on various pages, regardless of where they are redirected. For instance, if the user comes to your home page and navigates through 4 different pages.. then decides to log in, all the pages the user has already viewed will still be shown as if they aren't logged in. Feel free to try yourself and see the behavior.

You cannot use browser caching on sites that allow authentication *and* change the content of pages based on if the user is logged in or not. That's simply a fact of browser caching and we can't do anything about it.

I hope that helps explain. There is nothing in JFBConnect that can be done to get around this.

Alex

Andreea24 ,

Please create a separate thread for your issue. This thread is dealing with login via Facebook or other social networks. Since I don't see a subscription associated with your account, I'm assuming that your issue is with logging in via the SCLogin module. In general, you will also need to provide more details, as reproducing your issue is impossible without more specific details on which URLs, which mobile devices you are using, the problem behavior and any error messages that you are seeing.

-Melissa