elgentos / magento2-rumvision
elgentos/magento2-rumvision
Magento2 extension for the frontend implementation of RUMVision
Elgentos RUMvision Frontend implementation module
composer require elgentos/magento2-rumvision
Main Functionalities
Magento2 extension for the frontend implementation of RUMvision. You can find more information about rumvision on this page: https://www.rumvision.com/.
This module also adds page-type meta tags to help categorize different page types:
home- Homepagecms- CMS pagesproduct-detail- Product detail pagesproduct-listing- Category/product listing pagescart- Shopping cart pagecheckout- Checkout pagesuccess- Order success pagesearch- Search results pageaccount- Customer account pages
By these meta tags the RUMvision tool can automatically categorize the pages and show them in the correct dashboard.
Ofcourse its also possible to add custom types by adding the meta tag yourself in the head of the page like this:
<head>
<meta name="page-type" content="VALUE"/>
</head>
Installation
- Install the module composer by running
composer(2) require elgentos/magento2-rumvision - enable the module by running
php bin/magento module:enable Elgentos_Rumvision - apply database updates by running
php bin/magento setup:upgrade* - Flush the cache by running
php bin/magento cache:flush
Configuration
Next is to set the correct database settings for the module. From RUMvision you need the TrackingID and the hostname configured in the tool at: https://insights.rumvision.com
- Go to:
Stores > Configuration > Elgentos > RUMvision - Enabled the frontend implementation
- Set the Tracking ID
- Set the hostname
Set this in the backend of magento:
Output will be this script in the before.body.end container.
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.1.0 | stable | Pass | Magento 2.4.7-2.4.9 Details | 2026-06-11 10:43:22 |
| 1.0.11 | stable | Not tested | Not yet tested Details | 2025-11-10 21:25:40 |
| 1.0.10 | stable | Not tested | Not yet tested Details | 2025-11-10 21:23:08 |
| 1.0.9 | stable | Not tested | Not yet tested Details | 2025-04-22 14:22:26 |
| 1.0.8 | stable | Not tested | Not yet tested Details | 2025-04-18 14:08:50 |
| 1.0.7 | stable | Not tested | Not yet tested Details | 2025-01-31 09:40:44 |
| 1.0.6 | stable | Not tested | Not yet tested Details | 2025-01-31 09:01:19 |
| 1.0.5 | stable | Not tested | Not yet tested Details | 2024-12-02 15:01:05 |
| 1.0.4 | stable | Not tested | Not yet tested Details | 2024-02-19 13:08:52 |
| 1.0.3 | stable | Not tested | Not yet tested Details | 2023-03-03 14:22:30 |
| 1.0.2 | stable | Not tested | Not yet tested Details | 2023-03-03 12:03:16 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2023-03-03 10:55:06 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2023-03-03 07:45:26 |
Requires 3
| Package | Constraint |
|---|---|
| magento/framework | * |
| magento/module-store | * |
| php | ~8.0.0 || ~8.1.0 || ~8.2.0 || ~8.3.0 || ~8.4.0 || ~8.5.0 |
Requires-dev 1
| Package | Constraint |
|---|---|
| roave/security-advisories | dev-latest |
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 elgentos
View vendorLink existing guest orders to newly created or existing customer based on e-mail address
Allows customers to enter a secondary email address to login with
Hide Mollie payment methods based on category
Turn 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.