Today, Magento (now Adobe Commerce or Magento Open Source) is a modern platform that requires a server environment that meets its strict prerequisites. The current stable version is often 2.4.8 or a more recent patch version. These versions absolutely require up-to-date technologies such as PHP 8.2/8.3, MySQL 8.0/MariaDB 10.6, and a dedicated search engine such as Elasticsearch or OpenSearch.

For any new installation or migration, it is strongly recommended to use the latest stable version without any manual modification of the source code. You should choose a high-performance hosting type (Cloud Server or VPS/Dedicated) that guarantees access to all the system privileges required for secure and stable operation.

This guide explains how to patch the Magento installation so that it can be performed on an Infomaniak shared hosting, even without the privileges of type triggers & routines.

Troubleshooting Magento 2 Installation Issues

Edit the DbValidator.php file:

--- setup/src/Magento/Setup/Validator/DbValidator.php.orig 2019-04-11 17:01:45.154767893 +0200
+++ setup/src/Magento/Setup/Validator/DbValidator.php 2019-04-13 21:37:02.560386985 +0200
@@ -150,12 +150,8 @@
'ALTER',
'CREATE TEMPORARY TABLES',
'LOCK TABLES',
- 'EXECUTE',
'CREATE VIEW',
- 'SHOW VIEW',
- 'CREATE ROUTINE',
- 'ALTER ROUTINE',
- 'TRIGGER'
+ 'SHOW VIEW'
];
// check global privileges

In case of a problem

Depending on the version of Magento used, the soap function may not work correctly and may return the following error message: "Uncaught SoapFault exception: [Client] looks like we got no XML document".

The problem is not due to a misconfiguration of the server, but rather to a poor design of Magento that does not take into account the case of PHP running in an FPM environment. Thus, the SOAP requests generated by Magento contain double headers (not compliant with the SOAP specification) and generate an error.

Refer to this solution (not developed by Infomaniak) in case of a SOAP/PHPfpm error.