Version: 2.5.2, by sabret00the
Developer Last Online: Apr 2010
Version: 3.0.1
Rating:
Released: 06-03-2004
Last Update: 04-21-2005
Installs: 36
No support by the author.
although i know this works manually, it's untested via cron
Quote:
Originally Posted by AmyKhar
This hack will email a warning to members who have not activated their account and then delete them. It can run via cron, and is a pretty darn easy hack to install.
Features:
1. Emails users after 3 days and reminds them to activate their accounts.
2. Emails users after 5 days and lets them know their account will be deleted if they do not activate.
3. Emails users after 8 days with a final warning.
4. Deletes un-activated members after 10 days.
it still does exactly the same but this time for vb3
oh yeah, it emails you to tell you who was deleted, emailed so you're always informed.
if you got a big board you can't live without this, it stops the crap from piling up.
anything messes up, i can't take responsibility i'm afraid so back up before you try it.
#########################################
Add-On:
#########################################
if you like your templates in your admin cp neat then do this:
in "includes/adminfunctions_template.php" find
now save and close cos you're done :cheeky: :bored:
[high]wol stuff been removed due to the fact this should now be in the cron directory and thus won't show up anyway[/high]
and now like the days of our youth where everything was free and our mum would have dinner on the table for us, you're done.
[high]this was a fantastic vb2 hack and was made with blood, sweat and tears by Amy, she deserves all the credit for doing a fantastic job and then giving me permission to release this, so please if you install this should your gratitude in her direction as without her it would've been impossible.
the two critical bugs that a/ it wasn't sending the activationid and b/ it was deleting users who didn't change their email correctly, have been squashed by Psico[/high]
v2.1: Boofo killed 2 bugs
v2.2: more bugs killed by Boofo
v2.3: bugs killed by psico
v2.3a: bugs killed by sv1cec
v2.4: changed activation code when one exists already removed (sv1cec)
v2.4: better cron logging (me)
v2.4: table prefix bug found by jlurken, fixed by moi
v2.5: email reminder sent to your inbox thanks to sv1vec, improved logging, removed redundant code.
v2.5.2: fixed table prefixes.
[high]YOU WILL NOW NEED TO EDIT THE FILE TO MAKE SURE IT WORKS, IT'S CLEARLY MARKED ON LINE 21[/high]
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
i checked the useractivation table, only 1 entry of xantrix's ID, but there's a duplicate of someone else's id. the person with the same ID appearing 2 times in the table, i had activated myself in admin cp, so i dunno >.<
by the way, is it safe for me to clear out the userids that i have activated manually in the useractivation table?
Had a look into this problem and i think i know why some users show up double.
If you send a new activation mail from AdminCP (user contacted you to say they never received the mail??), vB will add a second record for that user into the 'useractivation' table, making this script see 2 waiting activations.
Had a look into this problem and i think i know why some users show up double.
If you send a new activation mail from AdminCP (user contacted you to say they never received the mail??), vB will add a second record for that user into the 'useractivation' table, making this script see 2 waiting activations.
Can you confirm this scenario?
i don't know if the user themselves clicked on resend validation or whatever link it was. but i looked inside the useractivation table and there it was indeed multiple entries of those people's ID's, each with a different activation ID. hope that helps with troubleshooting.
also, is it safe to delete the contents in the useractivation table after this 'bug' have been fixed? or will it be fine to just leave it there as it is?
The double entries in the useractivation table are not caused by this hack, it is standard vB behaviour. It is only that this hack don't check for double ones, so there should be no reason to manually remove entries from that table.
$userArray=$DB_site->query("
SELECT username," . TABLE_PREFIX . "user.userid,email,joindate,activationid
FROM " . TABLE_PREFIX . "user
LEFT JOIN " . TABLE_PREFIX . "useractivation ON (" . TABLE_PREFIX . "user.userid=" . TABLE_PREFIX . "useractivation.userid)
WHERE " . TABLE_PREFIX . "user.usergroupid=3 AND " . TABLE_PREFIX . "user.posts = 0
");
And replace by:
PHP Code:
$userArray=$DB_site->query("
SELECT username,user.userid,email,joindate,activationid
FROM " . TABLE_PREFIX . "useractivation AS useractivation
LEFT JOIN " . TABLE_PREFIX . "user AS user ON(user.userid=useractivation.userid)
WHERE dateline =
(select MAX(dateline) FROM " . TABLE_PREFIX . "useractivation AS ua2 WHERE ua2.userid = useractivation.userid)
AND user.usergroupid=3 AND user.posts = 0 ");
Your code wouldn't work sabe, try it.
PS I not tried my solution, so test it on a testboard first.