Moderation Alerts Pack 2.0 Patched

This release patches a common error while installing. It's just the same version as 2.0 but includes a modified core edit which hopefully does not trigger that error anymore.

Moderation Alerts Pack 2.0

This is the first major update for Moderation Alerts Pack. Although it doesn't feature too many new things, it's code has been totally rewritten, thus a new major release was necessary. It features:

• A completely rewritten approach to installation, uninstallation, core edits and hooks injection;
• Core edits are now checked upon installation and if one of the file the plugin wants to patch doesn't have the minimum required write permissions (664), the installation will be aborted and a message containing all the files that need to be updated will be prompted to the user;
• Uninstallation now works even if MyAlerts has been previously uninstalled and its database tables are not available. No more SQL errors!
• 3 new alert types has been added: you can be now notified whenever an user edits your signature (both from MCP and ACP), whenever an user approves your threads and whenever an user unapproves your threads;
• Dramatic code and file size cleanup: taking 3KB less than the previous version, but with a lot of new additions;

Moderation Alerts Pack 1.1

This is the first major update in the 1.x serie of Moderation Alerts Pack for MyAlerts. It features a completely rewritten approach to the alert generation, being fired directly in the moderation class. This new method makes Moderation Alerts Pack more flexible and fully compatible with external plugins that affects moderation.

Performances has been top priority whilst building the plugin. That's why every notification type has the minimum amount of queries and code possible in order to ensure the best performance and the less impact both to the database and to the server.