1000 FAQs, 500 tutorials and explanatory videos. Here, there are only solutions!
Install Magento without privilege triggers/routines
WARNING: This method modifies Magento core files to disable advanced privilege checks (triggers
, routines
), which is a risky practice in terms of security, stability, and complicates future updates.
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 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 must 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.
Absolutely avoid using the old patch below. Note that this patch is unnecessary in case of installation on a Cloud Server.
This guide explains how to patch the Magento installation so that it can be performed on an Infomaniak shared hosting, even without triggers
& routines
type privileges.
Resolve Magento 2 installation issues
Edit the file DbValidator.php
:
--- 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 SOAP/PHPfpm error
Depending on the version of Magento used, the soap
function does not work correctly and may return the following error message: Β«Uncaught SoapFault exception: [Client] looks like we got no XML document
Β».
The problem does not come from a bad server configuration, but rather from a poor design of Magento which does not take into account the case of PHP execution in an FPM environment. Thus, the SOAP requests generated by Magento contain double headers (non-compliant with the SOAP specification) and generate an error.
Be aware of this solution (not developed by Infomaniak).