Loss of Simultaneous "Member" Login with Admin Console Close

Whatever was "stale" when it blew up (two different logins), it is OK now, and yes, the "fix" seems to be working too, in that I did not loose my "member" login when I played around with membership management, made changes, closed it and admin console
etc. Thanks a lot for the fix and your patience with whatever stale coffee or such caused the previous blowup.

Once again thanks for the fix of that annoying little glitch. Yes, I am aware that you can 'get anywhere you need to be" as developer, but in my own long history of debugging I have encountered bugs that not only showed up only when a "user" was logged in, but believe it or not, the bug was triggered by the 7th character of that user's PASSWORD! Hence the volunteered use of our actual site admin login and password earlier. Sometimes even the most unlikely circumstances can blow software sky high, which is certainly the case with code based on C or C++ and to a lesser extent, Java ... all three of which languages are often their own best enemies as being bug generators!

Well, we will not settle for C or C++ or even Java when comes to bug generators...

Nooooo, we use Perl on the server for the "full-tilt bug generation experience". I do not know what drugs Larry Wall was doing when he created the Perl language, but I hope he is in recovery now. My brain neurons are starting to turn into hashes. (pun intended)

SteveTheTechie wrote: Well, we will not settle for C or C++ or even Java when comes to bug generators...

Nooooo, we use Perl on the server for the "full-tilt bug generation experience". I do not know what drugs Larry Wall was doing when he created the Perl language, but I hope he is in recovery now. My brain neurons are starting to turn into hashes. (pun intended)

Some do say that Perl stands for Pathologically Eclectic Rubbish Lister...