After migrating to Mage OS 1.0.4 3rd party modules that rely on release version failed as they are checking against Magento release version and then selecting the wrong code version. An example is Mirasvit's Ultimate Search module that checks which Magento version is installed, to then build the correct Class headers, src/SearchElastic/SearchAdapter/Query/Builder/MatchCompatibility.php
as 1.0.4 < 2.4.4 it is selecting the wrong Class headers and the compilation fails.
Do you propose a better was of selecting which version is installed?
Examples
if (version_compare(CompatibilityService::getVersion(), '2.4.4', '<')) {
Proposed solution
No response
Release note
No response
Triage and priority
[ ] Severity: S0- Affects critical data or functionality and leaves users without workaround.
[ ] Severity: S1- Affects critical data or functionality and forces users to employ a workaround.
[ ] Severity: S2- Affects non-critical data or functionality and forces users to employ a workaround.
[ ] Severity: S3- Affects non-critical data or functionality and does not force users to employ a workaround.
[ ] Severity: S4- Affects aesthetics, professional look and feel, “quality” or “usability”.
Summary
After migrating to Mage OS 1.0.4 3rd party modules that rely on release version failed as they are checking against Magento release version and then selecting the wrong code version. An example is Mirasvit's Ultimate Search module that checks which Magento version is installed, to then build the correct Class headers, src/SearchElastic/SearchAdapter/Query/Builder/MatchCompatibility.php
as 1.0.4 < 2.4.4 it is selecting the wrong Class headers and the compilation fails.
Do you propose a better was of selecting which version is installed?
Examples
if (version_compare(CompatibilityService::getVersion(), '2.4.4', '<')) {
Proposed solution
No response
Release note
No response
Triage and priority