Development Discussion Board

I'll post the same thing here: It would also be nice if the "before" hook were able to deny changes alltogether (or reject parts of the changes). A GEO Mod might check the entered location for example, or one might wish to restrict the Homepages to some special domains.

How about a simple notification that "something" in the user profile was changed? I agree that some mods need the name change, but other mods might need other changes as well. One could simply have a hook that carries the information of the column names that were changed along with the new values ...

It should be possible to deny adding the user through the "before" hook. A mod might set conditions that must be met, before a user can be added, for example it might check some data entered in custom profile fields (beyond just checking for the correct format, i.e. it might compare a field for ...

If you leave this up to the mods then the question is rather: Will the Mod Author be able to foresee all possible other mods that use the same hook and position his mod correctly in the execution order for all of them to work? I think there should be some way of sorting the mods so that Mod A can be ...

Yes, a lot of mods need to add a link to that menu.

Oh, I guess I missed that one. Yes, agreed.

The same thing goes for deleting topics, forums and posts since mods may need to delete data along with it.

It may be sensible to also be able to cancel a deletion process as well, sometimes the user may only be deleted if certain circumstances are met (for example the user may have to pay his ...

Name: hook_cron
Rationale: Many mods require to do maintenance on a regular basis, a calendar mod could delete old entries every week or a topic robot could post special topics every week.
Placement: cron.php
Input arguments: 1: repetition_rate (one of the constants: CRON_DAYLY CRON_WEEKLY ...