827b294ca8
This commit replays, conditionally, all the upgrade steps from MOODLE_19_STABLE to MOODLE_23_STABLE in the mod_book activity. That guarentees that any site using the mod_book before landing to core, no matter if it was the latest or an outdated one will upgrade perfectly to the expected current version. As a general rule, everytime one contrib plugin lands to core, its complete upgrade code must be kept, at least until the core version that introduced it, is out completely from the upgrade requirement conditions. In this case, with the missing upgrade code being added to 2.4, it will be safe to delete the upgrade steps once 2.5 (or upwards) become a requirement. Never always.
ACTIVITY MODULES
----------------
These are main modules in Moodle, allowing various activities.
Each of these modules contains a number of expected components:
mod_form.php: a form to setup/update a module instance
version.php: defines some meta-info and provides upgrading code
pix/icon.gif: a 16x16 icon for the module
db/install.xml: an SQL dump of all the required db tables and data
index.php: a page to list all instances in a course
view.php: a page to view a particular instance
lib.php: any/all functions defined by the module should be in here.
constants should be defined using MODULENAME_xxxxxx
functions should be defined using modulename_xxxxxx
There are a number of standard functions:
modulename_add_instance()
modulename_update_instance()
modulename_delete_instance()
modulename_user_complete()
modulename_user_outline()
modulename_cron()
modulename_print_recent_activity()
If you are a developer and interested in developing new Modules see:
Moodle Documentation: http://moodle.org/doc
Moodle Community: http://moodle.org/community