Page 1 of 1
Logon Bug
Posted: Mon Mar 15, 2021 7:49 pm
by Wm.Ince
Even after I check the "Remember Me" box, after leaving the SportPilotTalk.com and navigating to another site, each time I return, it requires me to logon again.
Is anybody else experiencing this anomaly?
This is contrary to the prior behavior on the site.
Bottom line . . . I cannot stay logged on.
Re: Logon Bug
Posted: Tue Mar 16, 2021 11:14 am
by RV12Heal
Yes! The Logon process has changed recently. I now have to Logon every time I visit the site -- annoying. Never had to do that before.
Re: Logon Bug
Posted: Tue Mar 16, 2021 11:47 am
by Wm.Ince
Here's the odd part. SportPilotTalk.com is the only forum I belong to that exhibits that behavior. The other 5 sites I participate in WILL remember I am logged in, using Apple mobile devices.
Re: Logon Bug
Posted: Tue Mar 16, 2021 12:23 pm
by 3Dreaming
It is an Android tablet that I am having issues with, so not an Apple thing.
Re: Logon Bug
Posted: Wed Mar 17, 2021 8:49 am
by JimParker256
Looks like Bill resolved his issue by ensuring he was using "https" (rather than "http" - note the trailing "s" in the first one) in front of the URL for the site. That might work for you as well.
To the forum admin: If this is in fact the issue with "sticky" logins, you might want to consider de-listing the non-secure version (http) of the site, so that when people just type in "sportpilottalk.com" the browser search engine doesn't succeed with "http" first, then get redirected to the secure version (https).
Re: Logon Bug
Posted: Wed Mar 17, 2021 9:30 am
by Wm.Ince
JimParker256 wrote: ↑Wed Mar 17, 2021 8:49 am
Looks like Bill resolved his issue by ensuring he was using "https" (rather than "http" - note the trailing "s" in the first one) in front of the URL for the site. That might work for you as well.
To the forum admin: If this is in fact the issue with "sticky" logins, you might want to consider de-listing the non-secure version (http) of the site, so that when people just type in "sportpilottalk.com" the browser search engine doesn't succeed with "http" first, then get redirected to the secure version (https).
Excellent idea.
Thanks for contributing to the resolution.