Proyectos de Subversion Moodle

Rev

| Ultima modificación | Ver Log |

Rev Autor Línea Nro. Línea
1 efrain 1
<?php
2
// This file is part of Moodle - http://moodle.org/
3
//
4
// Moodle is free software: you can redistribute it and/or modify
5
// it under the terms of the GNU General Public License as published by
6
// the Free Software Foundation, either version 3 of the License, or
7
// (at your option) any later version.
8
//
9
// Moodle is distributed in the hope that it will be useful,
10
// but WITHOUT ANY WARRANTY; without even the implied warranty of
11
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
12
// GNU General Public License for more details.
13
//
14
// You should have received a copy of the GNU General Public License
15
// along with Moodle.  If not, see <http://www.gnu.org/licenses/>.
16
 
17
/**
18
 * This file keeps track of upgrades to the settings block
19
 *
20
 * Sometimes, changes between versions involve alterations to database structures
21
 * and other major things that may break installations.
22
 *
23
 * The upgrade function in this file will attempt to perform all the necessary
24
 * actions to upgrade your older installation to the current version.
25
 *
26
 * If there's something it cannot do itself, it will tell you what you need to do.
27
 *
28
 * The commands in here will all be database-neutral, using the methods of
29
 * database_manager class
30
 *
31
 * Please do not forget to use upgrade_set_timeout()
32
 * before any action that may take longer time to finish.
33
 *
34
 * @since Moodle 2.0
35
 * @package block_settings
36
 * @copyright 2009 Sam Hemelryk
37
 * @license   http://www.gnu.org/copyleft/gpl.html GNU GPL v3 or later
38
 */
39
 
40
/**
41
 * As of the implementation of this block and the general navigation code
42
 * in Moodle 2.0 the body of immediate upgrade work for this block and
43
 * settings is done in core upgrade {@see lib/db/upgrade.php}
44
 *
45
 * There were several reasons that they were put there and not here, both becuase
46
 * the process for the two blocks was very similar and because the upgrade process
47
 * was complex due to us wanting to remvoe the outmoded blocks that this
48
 * block was going to replace.
49
 *
50
 * @param int $oldversion
51
 * @param object $block
52
 */
53
function xmldb_block_settings_upgrade($oldversion, $block) {
54
    // Automatically generated Moodle v4.1.0 release upgrade line.
55
    // Put any upgrade step following this.
56
 
57
    // Automatically generated Moodle v4.2.0 release upgrade line.
58
    // Put any upgrade step following this.
59
 
60
    // Automatically generated Moodle v4.3.0 release upgrade line.
61
    // Put any upgrade step following this.
62
 
63
    // Automatically generated Moodle v4.4.0 release upgrade line.
64
    // Put any upgrade step following this.
65
 
66
    return true;
67
}