From: kat <meo...@ya...> - 2005-07-27 17:11:29
|
If I set $proon_site_min_interval = '/1', should it automatically prune once right after I login and then 1 hour later and so on? That's what I understand from the documentation. Apparently that's not the case with me. It doesn't do anything right after I login and I suppose it waits until 1 hour after I login. If I set $proon_site_min_interval = '/0.0167' which is 1 minute, it'll prune right after I login, considering it's already 1 minute by the time it's done with the login process. |
From: WJCarpenter <bil...@ca...> - 2005-07-27 18:24:19
|
> If I set $proon_site_min_interval = '/1', should it automatically prune once right after I > login and then 1 hour later and so on? That's what I understand from the documentation. > Apparently that's not the case with me. It doesn't do anything right after I login and I > suppose it waits until 1 hour after I login. If I set $proon_site_min_interval = '/0.0167' > which is 1 minute, it'll prune right after I login, considering it's already 1 minute by the > time it's done with the login process. Yes, prooning is done at login time, no matter what, for anybody who has any proon-related settings at all. The mechanism for the recurring prune depends on a proon-specific session variable. Right after login, that variable is not set, making its value zero. Maybe that last assumption is not true in all PHP environments. You can see the code for this in the function proon_is_hook_active in hook.php. PS:- I see now there is a bug in that method which prevents the login pruning if you don't have a personal recurring prune interval. That's a serious goof (a failure in my QA department :-), which I'll correct, but it doesn't sound like that's what's affecting you. Are you getting the recurring pruning even if you are not getting the login pruning? (It takes more than a minute to logon at your site?) |
From: kat <meo...@ya...> - 2005-07-27 20:58:31
|
>> If I set $proon_site_min_interval = "/1", should it automatically prune once right after > I > > login and then 1 hour later and so on? That"s what I understand from the documentation. > > Apparently that"s not the case with me. It doesn"t do anything right after I login and I > > suppose it waits until 1 hour after I login. If I set $proon_site_min_interval = > "/0.0167" > > which is 1 minute, it"ll prune right after I login, considering it"s already 1 minute by > the > > time it"s done with the login process. > > Yes, prooning is done at login time, no matter what, for anybody who has any proon-related > settings at all. The mechanism for the recurring prune depends on a proon-specific session > variable. Right after login, that variable is not set, making its value zero. Maybe that > last assumption is not true in all PHP environments. You can see the code for this in the > function proon_is_hook_active in hook.php. > > PS:- I see now there is a bug in that method which prevents the login pruning if you don"t > have a personal recurring prune interval. That"s a serious goof (a failure in my QA > department :-), which I"ll correct, but it doesn"t sound like that"s what"s affecting you. > > Are you getting the recurring pruning even if you are not getting the login pruning? (It > takes more than a minute to logon at your site?) Actually the login pruning is more important for me, as most of my users won't hang around long enough to do the automatic pruning and I don't want to set the time interval to be very short. I now recall that when it did login pruning is actually the time I set a personal recurring prune interval of 1 minute and my assumption that it takes more than 1 minute to login may be wrong. I installed auto-prune-sent plugin before but for some unknown reasons most of the time it's not working and I don't know enough PHP to see what is wrong. By the way, I've to remove the line "include_once(SM_PATH . 'include/validate.php');" from hook.php for this plugin to work. I've the multilogin plugin installed and include/validate.php has to be modified. Do you think that's the reason? |
From: WJCarpenter <bil...@ca...> - 2005-07-27 21:29:30
|
>> PS:- I see now there is a bug in that method which prevents the login pruning if you don"t >> have a personal recurring prune interval. That"s a serious goof (a failure in my QA >> department :-), which I"ll correct, but it doesn"t sound like that"s what"s affecting you. > short. I now recall that when it did login pruning is actually the time I set a personal > recurring prune interval of 1 minute and my assumption that it takes more than 1 minute to OK, sounds like you are definitely hitting the bug I described for this part of your problem. I should be able to fix that overnight, so watch for an updated proon. > way, I've to remove the line "include_once(SM_PATH . 'include/validate.php');" from hook.php > for this plugin to work. I've the multilogin plugin installed and include/validate.php has to > be modified. Do you think that's the reason? I don't know what the problem is that you hit with validate.php, but it's almost certainly completely unrelated to the login pruning thing. |
From: WJCarpenter <bil...@ca...> - 2005-07-28 17:22:05
|
> PS:- I see now there is a bug in that method which prevents the login pruning if you don't > have a personal recurring prune interval. That's a serious goof (a failure in my QA > department :-). I have corrected this bug and uploaded a new proon. Anybody with v1.0.0 should discard it and get the new one. Very sorry for the inconvenience. |
From: Paul L. <pa...@sq...> - 2005-07-28 22:23:10
|
>> PS:- I see now there is a bug in that method which prevents the login >> pruning if you don't >> have a personal recurring prune interval. That's a serious goof (a >> failure in my QA >> department :-). > > I have corrected this bug and uploaded a new proon. Anybody with v1.0.= 0 > should discard it and > get the new one. Very sorry for the inconvenience. FYI, please avoid removing previous plugin releases. Although in this case it may be true that the only difference is a minor but very importan= t bug, we like to keep the older releases archived as a general rule.=20 Thanks! |
From: WJCarpenter <bil...@ca...> - 2005-07-28 22:38:02
|
> FYI, please avoid removing previous plugin releases. Although in this > case it may be true that the only difference is a minor but very important > bug, we like to keep the older releases archived as a general rule. I realize all that. The reason the first version was removed in this particular case is because the flaw was serious enough that nobody should use the previous version. There is no circumstance other than idle curiosity for anyone to want the previous version. |