MDL-35297 book: replay some steps lost when book landed to core
authorEloy Lafuente (stronk7) <stronk7@moodle.org>
Sun, 21 Oct 2012 07:56:01 +0000 (15:56 +0800)
committerEloy Lafuente (stronk7) <stronk7@moodle.org>
Sun, 21 Oct 2012 09:58:10 +0000 (17:58 +0800)
commit8be3d5ab030ab215333ebba7af07fdf5b0c10d47
treebe37e4f713cccbb0ba01ae0951d67da2fbc372a2
parent98197952cc12587ed11d8dd13922b19df137b772
MDL-35297 book: replay some steps lost when book landed to core

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.

Conflicts:
mod/book/version.php
mod/book/db/upgrade.php
mod/book/db/upgradelib.php [new file with mode: 0644]
mod/book/version.php