Upgrade Help

Upgrade Help

by Iain Munro -
Number of replies: 2

Just did an upgrade to Moodle 3.10.1 (Build: 20210118) and got the following three errors:

databasemysql (5.5.5-10.3.25-MariaDB)

Wrong $CFG->dbtype: you need to change it in your config.php file, from 'mysql' to 'mariadb'.


php_settingopcache.enable

PHP opcode caching improves performance and lowers memory requirements, OPcache extension is recommended and fully supported.


mysql_full_unicode_support

The current setup of MySQL or MariaDB is using 'utf8'. This character set does not support four byte characters which include some emoji. Trying to use these characters will result in an error when updating a record, and any information being sent to the database will be lost. Please consider changing your settings to 'utf8mb4'. See the documentation for full details.


Any help tp get me back and running would be appreciated.


Iain

Average of ratings: -
In reply to Iain Munro

Re: Upgrade Help

by Usman Asar -
Picture of Plugin developers Picture of Testers
Iain, in your moodle folder, you'll find config.php file. open that and you'll find the line $CFG->dbtype = 'mysql', all you need to do is change 'mysql' to 'mariadb' and you'll be able to use moodle, whereas opcache is concerned, this you have to ask your hosting provider if they allow opcache, if yes, you have to enable in PHP settings from your hosting panel, though opcache is recommended and not required.
where as your last query about unicode support, you have to make changes once again in config file, find the dboptions in your config and add following line.

$CFG->dboptions = array(

'dbcollation' => 'utf8mb4_unicode_ci',

);

Things should work for you.
Average of ratings: Useful (1)
In reply to Usman Asar

Re: Upgrade Help

by Leon Stringer -
Picture of Core developers Picture of Particularly helpful Moodlers

Just to expand on what Usman says: to fix the mysql_full_unicode_support warning you should change your Moodle's database to use the recommended utf8mb4 character set before setting 'dbcollation' => 'utf8mb4_unicode_ci'. The steps are in the link in that warning.