yireo / yireo_googletagmanager2lokicheckout
yireo/yireo_googletagmanager2lokicheckout
N/A
Yireo_GoogleTagManager2LokiCheckout
This Magento 2 module adds additional logic of the Yireo GoogleTagManager 2 to the Yireo Loki Checkout.
Installation
composer require yireo/magento2-googletagmanager2-loki-checkout
bin/magento module:enable Yireo_GoogleTagManager2LokiCheckout
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
[Unreleased]
[2.0.7] - 17 February 2026
Fixed
awaitforAlpine.store('LocalStorage').get('loki-checkout')
[2.0.6] - 12 November 2025
Fixed
- Rename LokiLocalStorage to LocalStorage
- Update keywords
- Update composer keywords
- Update composer keywords
[2.0.5] - 22 October 2025
Fixed
- Update MODULE.json with PHPCS severity 8
- Sort entries of module.xml file
- Sort dependencies of composer.json
- Copy generic CI/CD files
- Update MODULE.json
[2.0.4] - 08 October 2025
Fixed
- Do not apply hyva handle, but just copy all XML layout changes
[2.0.3] - 29 September 2025
Fixed
- Enable Alpine templates to call upon Yireo GTM properly
- Failsafe for when store is not present yet
[2.0.2] - 27 September 2025
- Change container to block
- Prevent empty quote from causing exception
- New structure of localStorage listener
[2.0.1] - 13 August 2025
Fixed
- Prepare release
- Rename LokiDataLoaderComponentPartial to LokiLoadDataComponentPartial
[2.0.0] - 22 July 2025
Fixed
- Rename composer package from
yireo/magento2-loki*toloki/magento2* - Rename PHP namespace from
Yireo_Loki*toLoki*
[1.0.1] - 30 May 2025
Fixed
- Fix potential issue of incomplete events
[0.0.1] - 06 May 2025
Added
- Initial release
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 2.0.7 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2026-02-17 14:35:40 |
| 2.0.6 | stable | Not tested | Not yet tested Details | 2025-11-12 11:55:21 |
| 2.0.5 | stable | Not tested | Not yet tested Details | 2025-10-22 11:28:23 |
| 2.0.4 | stable | Not tested | Not yet tested Details | 2025-10-08 12:47:38 |
| 2.0.3 | stable | Not tested | Not yet tested Details | 2025-09-29 12:09:33 |
| 2.0.2 | stable | Not tested | Not yet tested Details | 2025-09-27 01:34:42 |
| 2.0.1 | stable | Not tested | Not yet tested Details | 2025-08-13 08:12:46 |
| 2.0.0 | stable | Not tested | Not yet tested Details | 2025-07-22 08:43:47 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2025-05-30 12:47:04 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2025-05-06 09:48:08 |
Requires 4
| Package | Constraint |
|---|---|
| loki/magento2-components | ^2.0 |
| magento/framework | ^102.0 || ^103.0 |
| magento/module-checkout | ^100.0 |
| yireo/magento2-googletagmanager2 | ^3.10 |
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 yireo
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.