Sara Arjona
a26cfe71d3
This just deletes all the upgrade steps previous to 3.5.0. Some small adjustments, like tweaking globals can also be applied when needed. Also includes an upgrade step to prevent upgrading from any version < 2018051700 (v3.5.0) as anti-cheating measure. Previous commits have removed/deprecated all the upgradelib functions not used anymore in codebase. Deletion has been documented in corresponding upgrade.txt files: - upgrade_fix_block_instance_configuration() - upgrade_theme_is_from_family(), upgrade_find_theme_location() and linkcoursesectionsupgradescriptwasrun setting - upgrade_block_positions - upgrade_fix_config_auth_plugin_names() and upgrade_fix_config_auth_plugin_defaults() - format_xxx_upgrade_remove_numsections(), format_xxx_upgrade_hide_extra_sections() and format_xxx_upgrade_add_empty_sections() - filter_mathjaxloader_upgrade_cdn_cloudflare() and filter_mathjaxloader_upgrade_mathjaxconfig_equal() - get_assignments_with_rescaled_null_grades() These have been kept because continue being used by restore: - \core\task\refresh_mod_calendar_events_task
58 lines
2.0 KiB
PHP
58 lines
2.0 KiB
PHP
<?php
|
|
// This file keeps track of upgrades to
|
|
// the data module
|
|
//
|
|
// Sometimes, changes between versions involve
|
|
// alterations to database structures and other
|
|
// major things that may break installations.
|
|
//
|
|
// The upgrade function in this file will attempt
|
|
// to perform all the necessary actions to upgrade
|
|
// your older installation to the current version.
|
|
//
|
|
// If there's something it cannot do itself, it
|
|
// will tell you what you need to do.
|
|
//
|
|
// The commands in here will all be database-neutral,
|
|
// using the methods of database_manager class
|
|
//
|
|
// Please do not forget to use upgrade_set_timeout()
|
|
// before any action that may take longer time to finish.
|
|
|
|
defined('MOODLE_INTERNAL') || die();
|
|
|
|
function xmldb_data_upgrade($oldversion) {
|
|
global $CFG, $DB;
|
|
|
|
// Automatically generated Moodle v3.5.0 release upgrade line.
|
|
// Put any upgrade step following this.
|
|
|
|
// Automatically generated Moodle v3.6.0 release upgrade line.
|
|
// Put any upgrade step following this.
|
|
|
|
// Automatically generated Moodle v3.7.0 release upgrade line.
|
|
// Put any upgrade step following this.
|
|
|
|
if ($oldversion < 2019052001) {
|
|
|
|
$columns = $DB->get_columns('data');
|
|
|
|
$oldclass = "mod-data-default-template ##approvalstatus##";
|
|
$newclass = "mod-data-default-template ##approvalstatusclass##";
|
|
|
|
// Update existing classes.
|
|
$DB->replace_all_text('data', $columns['singletemplate'], $oldclass, $newclass);
|
|
$DB->replace_all_text('data', $columns['listtemplate'], $oldclass, $newclass);
|
|
$DB->replace_all_text('data', $columns['addtemplate'], $oldclass, $newclass);
|
|
$DB->replace_all_text('data', $columns['rsstemplate'], $oldclass, $newclass);
|
|
$DB->replace_all_text('data', $columns['asearchtemplate'], $oldclass, $newclass);
|
|
|
|
// Data savepoint reached.
|
|
upgrade_mod_savepoint(true, 2019052001, 'data');
|
|
}
|
|
// Automatically generated Moodle v3.8.0 release upgrade line.
|
|
// Put any upgrade step following this.
|
|
|
|
return true;
|
|
}
|