ioweb-gr / m2_mariadbhotfix
ioweb-gr/m2_mariadbhotfix
Ioweb_MariaDbHotfix
Magento 2 module that patches the SqlVersionProvider to accept MariaDB 10.x and 11.x version strings. Without this patch, Magento throws a version compatibility error when running on recent MariaDB releases.
What it does
Adds two version patterns to Magento\Framework\DB\Adapter\SqlVersionProvider via DI:
^10\.\d+\.— matches any MariaDB 10.x release^11\.\d+\.— matches any MariaDB 11.x release
This is not a functional compatibility fix — it simply tells Magento to stop rejecting the MariaDB version string.
Installation
composer require ioweb-gr/m2_mariadbhotfix
bin/magento module:enable Ioweb_MariaDbHotfix
bin/magento setup:upgrade
Requirements
- PHP >= 7.0
- Magento 2
License
Proprietary — IOWEB TECHNOLOGIES
Changelog
[1.0.9] - 2026-03-20
Changed
- Fixed package name to
ioweb-gr/m2_mariadbhotfix(wasioweb/mariadbhotfix) - Added
versionfield tocomposer.json - Bumped
setup_versionfrom0.1.0to1.0.9 - Removed legacy
magento/magento-composer-installerdependency - Added GitHub Actions auto-release workflow on semantic version tag push
- Added
create-junction.cmdfor Windows FTP mapping - Added
README.md,USER_GUIDE.md,CHANGELOG.md - Removed
.idea/IDE artifacts
[1.0.8] - Previous
- Added MariaDB 11.x support pattern (
^11\.\d+\.) toSqlVersionProvider
[1.0.7] - Previous
- Added MariaDB 10.x support pattern (
^10\.\d+\.) toSqlVersionProvider
[0.1.0] - Initial
- Initial release: DI patch forcing Magento 2 to accept MariaDB 10.5+
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.0.9 | stable | Pass | Magento 2.4.7-2.4.9 Details | 2026-03-20 07:36:43 |
| 1.0.8 | stable | Not tested | Not yet tested Details | 2025-11-05 07:46:52 |
| 1.0.7 | stable | Not tested | Not yet tested Details | 2025-03-06 09:36:49 |
| 1.0.6 | stable | Not tested | Not yet tested Details | 2024-11-11 10:14:54 |
| 1.0.5 | stable | Not tested | Not yet tested Details | 2024-11-11 09:00:09 |
| 1.0.4 | stable | Not tested | Not yet tested Details | 2023-04-23 09:02:37 |
| 1.0.3 | stable | Not tested | Not yet tested Details | 2022-09-01 10:45:09 |
| 1.0.2 | stable | Not tested | Not yet tested Details | 2021-01-29 14:50:46 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2020-12-11 08:30:45 |
Requires 1
| Package | Constraint |
|---|---|
| php | >=7.0 |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from ioweb-gr
View vendorTurn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.