I have a Moodle 3.3.1 instance hosted by 1and1 (now IONOS) and back in Jan 2018 I tried to upgrade it to 3.4.
This failed because of the mysql innodb file requirement to be Barracuda and I had to do a complete roll back.
I am now trying this again. This time I have created a VM with all the standard settings from the https://docs.moodle.org/33/en/Step-by-step_Installation_Guide_for_Ubuntu
I have then set the mysql innodb to Antelope expecting the upgrade to 3.4.7 to fail.
SET GLOBAL innodb_file_format = antelope;
SET GLOBAL innodb_file_format_max = antelope;
SET GLOBAL innodb_large_prefix = off;
But it did not fail and when I checked the innodb settings afterwards I found it had set them back to Barracuda.
Because of the shared hosting I am unable to change the innodb settings for my live instance. I am guessing the Moodle upgrade process will also be unable to make the change.
How can I set up my VM so the Moodle upgrade fails?
The whole point of all this was I wanted to try an bypass the check using https://stackoverflow.com/questions/51838089/moodle-baracuda-check-bypass-or-highest-antelope-version
Has anyone got this upgrade working on a 1and1 shared hosting?
Or has Moodle 3.4.7 resolved the Barracuda requirement?
We do not need Unicode support