Plans for Alpha 1 about draiwiki HOT 2 OPEN

In one of the school projects I'm currently doing, errors are handled like this: the execute() method returns an integer (the error code). The main class then checks if the return code is equal to zero. If so, no errors occurred and the display() method can be invoked. If not, the appropriate error message is displayed like this:

switch ($returnCode) {
    case ReturnCode::GENERAL_ERROR:
        $errorMessage = 'general_error';
        break;
    ...
}

This would be a lot cleaner, since more advanced errors (for example, if you need to specify field names) could be handled by the model itself. If a model method returns an error code, the controller would then check the $errors array and handle the error and call an error template manually (in the display() method).

Database errors are always fatal, so we wouldn't have to worry about them.

Management panel-related errors would be handled by the management controller, since it uses a different layout.

from draiwiki.

The following management panel sections will be postponed indefinitely:

• Security log
• Server & database settings
• Advanced theme management (will be moved to general settings for the time being)
• Manual (might redirect to the official wiki)

Features that will possibly be postponed as well:

• Maintenance actions
• Bans

The reason that these features are postponed is a lack of time. Besides, most of these are nice to have, but not absolutely required.

from draiwiki.