MySQL Parameter (Barracuda, etc.) - ALL-INKL.COM shared web hosting


I was wondering if it is really necessary to change the mariadb file format to Barracuda and set innodb_large_prefix = 1. Because this changes makes it impossible to install Pimcore 5.x on a “regular shared” webhosting (allinkl in my case).

As I could install Pimcore 3.x without any problems on a shared webhosting, starting with 4.x there has been a dependency to memcached and now 5.x is complaining about missing my.cnf parameters (as mentioned above) when trying to run the install script.

So are those my.cnf changes are really required to run pimcore?

Thx & BR,

Hate it too, but yes, it is necessary

Do you know what would not be functional if these settings are not set?

@leuchtdiode: read more about this here:

Alright, thanks for the explanation.

Do I understand it right? By installing a fresh Pimcore instance, the installer sets the keys/filenames to ascii and I do not have to set the innodb_-settings?

Is there a way to overwrite this for the update process? My customers won’t be very happy to leave there hoster or take a root server just for setting those vars… :wink:

Nope, these settings are a requirement now. Even for updates. If you have a hoster like hetzner, they support this out-of-the-box anyway.

1 Like

I get the point of @daniel.schmieder. It’s not optimal that pimcore 5.1.x is not running on my hoster allinkl any longer. It’s impossible for me now to update some instances I’m running.

I absolutely understand this change. But the possibility to switch off the utf8 support and keep the ascii names as before would be great… Maybe there’s an inofficial way to achieve this. Have to check this out or does anybody already had a look for this?

2 1/2 half years later I tested pimcore again on allinkl and the system requirements check passes now the database requirements!

Need to do some more testing, but I think it’s now running on allinkl :slight_smile:

@daniel.schmieder fyi if you are also still wondering :laughing: