Posted on: 09/25/06 02:02pm
By: PWR
No replies to my post
here[*1] yet, maybe because I posted to an existing thread, but this is becoming more problematic.
I'm now getting this problem. I doubt if it's related to CAPTCHA, but it started at about the time I installed CAPTCHA a few days ago. As root, I will be logged in doing things, all is going well, and then I'll get the error message along the lines of "you must be logged in to do that". Looking around, I discover the login box is visible in the sidebar. After logging back in, all goes well for a while, then the cycle repeats. This has happened several times over the past few days, never happened before.
Frustrated, but determined.
TIA
Randomly (?) logged out without request, without notice, without reason
Posted on: 09/25/06 02:34pm
By: mevans
pwr,
I doubt the logout problems have to do with the CAPTCHA installation, as it really only touches anything when new user registers, but you never know...
Has there been any changes on your client (workstation) side recently? I'm wondering if the cookie is being deleted in the browser or something? Any new utilities installed on your computer?
Also, any changes to Geeklog's config.php file recently? There are some variables that deal with the cookie's any chance any of them were changed?
Last, double check your account (Account Information) and see what you have selected for 'Remember Me'.
Thanks!
Mark
Randomly (?) logged out without request, without notice, without reason
Posted on: 09/25/06 05:47pm
By: PWR
Thanks for the ideas, but it's not just me having the problem. It's all my admins, and users too, so it's not client side. I didn't realize it was affecting all users when I wrote earlier.
I made the required changes to config files to install CAPTCHA, and recently added a new user group, but no other changes.
I hate to back CAPTCHA back out for a test, but it may come to that if this doesn't otherwise get solved.
And I agree it doesn't seem likely CAPTCHA would be the cause, it's just time related.
Randomly (?) logged out without request, without notice, without reason
Posted on: 09/25/06 05:52pm
By: mevans
I took a quick look at your site and saw only one thing that I don't know much about. You call a javascript called:
<!-- for Pop-Up Politician -->
<script type="text/javascript" src='http://www.sunlightlabs.com/popuppoliticians/sunlightpopups.js'></script>
<!-- end Pop-Up Politician -->
I'm wondering if this could be the culprit? I'm not sure what its purpose is, so I don't know what exactly it is doing. Maybe comment it out for a test just to rule it out?
Or, I may be completely out in left field and this has nothing to do with the issue, how is that for helpful
Thanks!
Mark
GIANT STEPS: Re Randomly (?) logged out without request, without notice, without reason
Posted on: 10/03/06 06:35pm
By: PWR
I eventually discovered that all users and admins' "Account Information / Remember Me For" had been mysteriously reset to "don't", so it seems all users were being logged out after expiration of session cookie, which is defined in config.php I believe.
And then, a minute ago, I found this
http://www.macosxhints.com/article.php?story=20061003084806436
which says there's a missing "where" clause on a database call in Geeklog that occurs when using a custom registration screen, such as CAPTCHA.
My problem, now, is that the author didn't say how/where to fix the clause. Anybody know?
Randomly (?) logged out without request, without notice, without reason
Posted on: 10/03/06 06:44pm
By: asmaloney
It's in
[geeklog_dir]/system/lib-custom.php in
custom_usersave().
It should be:
DB_query("UPDATE {$_TABLES['users']} SET cookietimeout='{$_POST["cooktime"]}' WHERE uid='$uid'");
- Andy
Randomly (?) logged out without request, without notice, without reason
Posted on: 10/03/06 06:52pm
By: Anonymous (PWR)
Thanks!
Whew, I've been bothered by this for too long.
Randomly (?) logged out without request, without notice, without reason
Posted on: 10/04/06 01:54am
By: Dirk
Yeah, that's an unfortunate bug in the sample code in lib-custom.php. It has been fixed in 1.4.1b1 but didn't make it back into the 1.4.0 branch. Sorry about that.
bye, Dirk