After upgrade to 5.6.0.1 I now need to login twice
Permalink
I upgraded from 5.4.1.1. to 5.4.2.2 to 5.5.2.1 and lastly to 5.6.0.1. A weird thing now occurs: when I login to the first time, it does not redirect me to the dashboard, but it reloads the login page. Only when I login again am I redirected to the dashboard. Sometimes I even have to login a third time.
C5 *does*, however authenticate and authorize me correctly upon the first login, because when I navigate manually to the dashboard URL after the first "failed login", it gladly takes me there.
Is this a bug or is there something I can do?
C5 *does*, however authenticate and authorize me correctly upon the first login, because when I navigate manually to the dashboard URL after the first "failed login", it gladly takes me there.
Is this a bug or is there something I can do?
Bump. Anyone?
Can't help, but noticed the same on a Beta install I did on one of my sandbox/dev sites.
( Hasn't irritated me enough yet to look for the issue )
( Hasn't irritated me enough yet to look for the issue )
Same problem here :(
Hello,
Has anyone found a solution on this?
I have the same on two different servers, with 5.6.1.2. Disabled full page cache for login page in the full sitemap, system pages. No result.
Best wishes,
Nick
Has anyone found a solution on this?
I have the same on two different servers, with 5.6.1.2. Disabled full page cache for login page in the full sitemap, system pages. No result.
Best wishes,
Nick
I haven't found a solution for this highly annoying bug either. My customer now knows she has to manually navigate to the dashboard after logging in, but this is obviously not a structural solution. It would be great if anyone from the C5 team would have a look at this.
Has anyone found a solution to this yet. Any site I upgrade has this problem. It does not occur on a fresh install just if I upgrade from an earlier version to 5.6.1.2 using the correct upgrade sequence.
It is really bugging my clients who have to log in multiple times or manually navigate to the pages to edit. It is not helping the C5 reputation.
Regards Ian
It is really bugging my clients who have to log in multiple times or manually navigate to the pages to edit. It is not helping the C5 reputation.
Regards Ian
Disabling Wincache did the trick for me, give that a try if you're using it.
Allowing guest access to login page (full sitemap -> show system pages) did the trick for me. After upgrading from very old concrete5 version (5.4.2 -> 5.6.2.1) site access was set from public to private and permissions were reset in pages and files. I had to manually grant view permissions to guests and edit permissions to sub-admins.
Permissions did the trick for me too!
Thank you!
Thank you!
Yes! This worked for me too. Thanks solinet!
I don't want to resurrect this issue necessarily, but I notice that this happens from time to time on only this particular website (http://www.azselfstorage.org) that I manage running 5.6.2.1. I seem to have narrowed it down, based on this thread and a couple others to the following 3 potential culprits... 1. Full Page Caching, 2. Permissions/Access, 3. Browser version (particularly older IE browser versions). For things within my control, I disabled all caching on the Login page and checked every box under "who can view this page". I have since not been able to replicate the issue. However, we have 650 members/users, and as we all know, any number of them could be running a severely outdated version of IE and that's entirely their problem at the end of the day as far as I see it because this isn't an issue on updated and current browsers!
