I have one ghost user currently and I've set the option to clean it up for seven days, so theoretically, that should expire tomorrow. I'll let everyone know if that doesn't happen.
I have another mod that cleans out users "awaiting email" responses set to delete them after 14 days of them not validating, which is why I set this mod to 7 days so the other didn't interfere with the "do not delete" function of Lancerforhire's mod.
I also run vbMail Pro by Dragonbytes, which has a bounced mail handler and I notice that my ghost user shows up in their bounced email list, but I'm hoping they don't do anything to screw up this mod's handling of that ghost user email address and account. I think they simply use a field in the user record to set if there's bounced emails, so they don't send additional newsletters to users who have previously had an email bounce.
Regards
Doug
The problem is not the ghost buster not working; the ghost buster running fine, but there are no ghost users to delete. When this happens, the script halts execution as I coded it to. The problem with this is that the ghost buster is running on one of vBulletin's cron hooks; it is not in it's own PHP file as I initially intended. So, it is theoretically possible for ghost buster to prevent any cron jobs on the same hook with a succeeding execution order from functioning. I believe this is what is happening.
The problem is not the ghost buster not working; the ghost buster running fine, but there are no ghost users to delete. When this happens, the script halts execution as I coded it to. The problem with this is that the ghost buster is running on one of vBulletin's cron hooks; it is not in it's own PHP file as I initially intended. So, it is theoretically possible for ghost buster to prevent any cron jobs on the same hook with a succeeding execution order from functioning. I believe this is what is happening.
Understood ...
Should we disable the mod until you find a solution?
I have one ghost user currently and I've set the option to clean it up for seven days, so theoretically, that should expire tomorrow. I'll let everyone know if that doesn't happen.
For clarification, when does the cron job run and where is it? I can't find it in the scheduled tasks list?
My only ghost entry is 7 days old as of today August 13th (see attached pic), so when does it disappear from the site? Is there some way of manually running the cron job to make sure it works?
Thanks ...
Regards,
Doug
ps: any further ideas on the concept modoption of offering an "early bird" discount subscription that only appears when people register and not after they have?
For clarification, when does the cron job run and where is it? I can't find it in the scheduled tasks list?
My only ghost entry is 7 days old as of today August 13th (see attached pic), so when does it disappear from the site? Is there some way of manually running the cron job to make sure it works?
Thanks ...
Regards,
Doug
ps: any further ideas on the concept modoption of offering an "early bird" discount subscription that only appears when people register and not after they have?
It probably has not been exactly 24 hours yet; check to see if it's still there tomorrow. Don't worry about the other stuff.
It probably has not been exactly 24 hours yet; check to see if it's still there tomorrow. Don't worry about the other stuff.
Ok, checked, at 10:00 am EST this morning, August 14th and the "Pending Subscription 1" user from August 5th is still there, with the mod option cleanup for these entries set to "1 Week" ....
Anything else I can do get rid of that entry without screwing up either your mod or our database?
Pay to Register Details »»
About Developer
Visit Web Site
Uses Plugins 
No support by the author.
08-12-2011, 10:47 PM
