Hi all,
I recently found out that my super secret test vb3 forum was busy churning out happy birthday e-mails and account activation reminders like it was nobody's business. "Click on this secure link which will prompt you for a username and password you don't know to activate the account you created six months ago" ... nice.
Now, 100 angry users later, I find out that this vbcron thing just clicked itself on without asking anyone and went happy e-mailing everyone.
It would be super nice if you could possibily include a way to temporarily disable those e-mails from being processed and/or sent for situations like these. The only way I saw to stop them from going out was to delete the cron jobs, which it looks like without knowing the appropriate .php file, is difficult to bring back.
A nice little addition to the drop down box would be good "disable/enable". I'd suggest this as a new feature, but I'm of the opinion that the installer should ask first before contacting people.
Move this as you see fit.
Best wishes,
Paul
I recently found out that my super secret test vb3 forum was busy churning out happy birthday e-mails and account activation reminders like it was nobody's business. "Click on this secure link which will prompt you for a username and password you don't know to activate the account you created six months ago" ... nice.
Now, 100 angry users later, I find out that this vbcron thing just clicked itself on without asking anyone and went happy e-mailing everyone.
It would be super nice if you could possibily include a way to temporarily disable those e-mails from being processed and/or sent for situations like these. The only way I saw to stop them from going out was to delete the cron jobs, which it looks like without knowing the appropriate .php file, is difficult to bring back.
A nice little addition to the drop down box would be good "disable/enable". I'd suggest this as a new feature, but I'm of the opinion that the installer should ask first before contacting people.
Move this as you see fit.
Best wishes,
Paul
Comment