mysql_full_unicode_support#File_format

mysql_full_unicode_support#File_format

by CHANDRASEKAR RAVI -
Number of replies: 12

Hi,  I tried to install the latest version (3.2.2) on my shared hosting.  

I encountered two DB messages:  mysql_full_unicode_support#File_format  mysql_full_unicode_support#Large_prefix 

Please resolve this issue





Thanks in advance

Average of ratings: -
In reply to CHANDRASEKAR RAVI

Re: mysql_full_unicode_support#File_format

by Deepak Gour -

Hi Chandrasekar

You need to put code in your config-> my.ini file in case you use xampp server. 

If you use Apache server than open my.cnf  file

copy below code and paste it.


[client]
default-character-set = utf8mb4

[mysqld]
innodb_file_format = Barracuda
innodb_file_per_table = 1
innodb_large_prefix

character-set-server = utf8mb4
collation-server = utf8mb4_unicode_ci
skip-character-set-client-handshake

[mysql]
default-character-set = utf8mb4
  • Restart your MySQL server.

Average of ratings: Useful (2)
In reply to Deepak Gour

Re: mysql_full_unicode_support#File_format

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

The OP mentioned 'shared hosting'. I very much doubt this is Xampp. 

In reply to Deepak Gour

Re: mysql_full_unicode_support#File_format

by guido pazos -

Deepak Gour, Thank you so much for everything! It helped me.

Greeting

Guido

In reply to Deepak Gour

Re: mysql_full_unicode_support#File_format

by Amir Mustafa -

Along with that you can also try below codes in your phpMyAdmin sql:

Execute below code in sql of your database:

set global innodb_file_format = `BARRACUDA`;
set global innodb_large_prefix = `ON`;


This will remove antelope/ Baracuda error from checker

In reply to Deepak Gour

Re: mysql_full_unicode_support#File_format

by hip hop -

Hello.

Ty for your info. Despite I find it useful my host (@Stablehost) is doing it worst and worst and they say they can't update the mySQL server configuration nor let me do it. I've even tried doing it myself through phpMyAdmin but it throws a '1227 - Access denied; you need (at least one of) the SUPER privilege(s) for this operation'. sad

There may be any alternative option or should I move to a new reliable host?

TIA,
h

In reply to hip hop

Re: mysql_full_unicode_support#File_format

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

If you can’t configure MySQL as recommended, you must manually create your database with utf8 (not utf8mb4) character encoding before starting the installation of Moodle. The main disadvantage is that your site will be unable to display emojis. You will still see a warning message but you should be able to proceed with the installation.

Alternatively you can move to a better hosting provider as you suggested which will allow your Moodle site to be installed in the recommended way.

Average of ratings: Useful (1)
In reply to Leon Stringer

Re: mysql_full_unicode_support#File_format

by hip hop -

Ty! I'll try both.
Any suggestions/thread about hostings. I'd need a shared one for some 4 or 5 customers plus my experiments and tests.

TIA. Have a nice day!
hip

In reply to Leon Stringer

Re: mysql_full_unicode_support#File_format

by hip hop -

Hi Leon. I already had the DB as utf8 (not utf8mb4) and still get the following error message:
"Your database uses Antelope as the file format. Full UTF-8 support in MySQL and MariaDB requires the Barracuda file format. Please switch to the Barracuda file format. See the documentation MySQL full unicode support for details."

and stuck prior install process. Any clue? Thank you in advance.

In reply to hip hop

Re: mysql_full_unicode_support#File_format

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

If you've previously attempted to install this you may have a config.php in your Moodle source code folder with the utf8mb4 setting. Check this file for the line:

  'dbcollation' => 'utf8mb4_unicode_ci',

and if this is present try changing this to:

  'dbcollation' => 'utf8_unicode_ci',


Average of ratings: Useful (3)