ometria / magento2

ometria/magento2

Dev composer package for Ometria Extension

  • Ometria
magento2-module Compatibility: 2.4.7-2.4.8 Code Quality: Fail Tests: Fail Security: Pass

Are you the maintainer of ometria?

Packagento pulls ometria's Composer packages from the public registry so buyers can find them here.

Claim the namespace to take ownership, publish new releases directly, and start charging for premium versions.

Claim this namespace →

Installing the Extension

While you're free to manually install the Ometria extension (the use of the app/code folder structure supports this), we recommend using Magento's PHP composer integration to install the extension. All Magento 2 systems have a composer.json file, and this file is how developers and Magento Marketplace users get new packages in and out of their system.

Installing the extension is a 4 step process

  1. Add this GitHub repository to your project's composer.json as a composer repository
  2. Add the ometria/magento2 composer package to your project's composer.json as a required dependency
  3. Update your project's composer dependencies
  4. Install the downloaded package via Magento's standard command line tool

Support

If you have any concerns or questions, please send an email to [email protected]
with all relevant details that are needed to investigate or resolve the issue.

Quick Start

After backing up your composer.json file

cp composer.json composer.json.bak

Run

composer.phar config repositories.ometria vcs https://github.com/Ometria/magento2-extension
composer require ometria/magento2 --no-update
composer update ometria/magento2
php bin/magento module:enable Ometria_AbandonedCarts Ometria_Api Ometria_Core
php bin/magento setup:upgrade

After running the above, the Ometria extension will be installed, ready for configuration.

Please note, if you are running PHP OPcache on your server and have configured it not to clear automatically then you will need to clear the OPcache in order for the new module to become available after the above steps.

Composer Details

The first composer command

composer.phar config repositories.foo vcs https://github.com/Ometria/magento2-extension

add this GitHub repository as a composer repository

#File: composer.json
//...
"repositories": {
    "ometria": {
        "type": "vcs",
        "url": "https://github.com/Ometria/magento2-extension"
    }
},
//...

This tells composer it should look for additional packages in this GitHub repository.

The second command

composer require ometria/magento2 --no-update

add the latest stable version of ometria/magento2 to your composer.json file's require section.

#File: composer.json
//...
"require": {
    //...
    "ometria/magento2": "^2.0"
},
//...

The third command

composer update ometria/magento2

Updates any composer packages that match the string ometria/magento2. This is what triggers the download of the Ometria extension source code to vendor/ometria.

The final two commands are Magento commands. This command enables the three modules that make up the Ometria extension

php bin/magento module:enable Ometria_AbandonedCarts Ometria_Api Ometria_Core

Once a module is enabled, the rest of Magento can "see" it. The last command tells Magento to actually install the module.

php bin/magento setup:upgrade

Upgrading the Extension

Composer can be used to upgrade an existing install of the module to the latest release using the following commands:

composer require ometria/magento2 --no-update
composer update ometria/magento2
php bin/magento setup:upgrade

This will update your composer.json file's require section with the latest stable version of ometria/magento2. Then the latest code at that version will be pulled in by composer update. Finally re-running the Magento setup:upgrade command will ensure the module is installed correctly at the new version.

If you installed the module manually in to app/code please ensure you remove all of the existing module files before replacing with the new files from the latest release and re-running the Magento setup:upgrade command.

Important: Changing a Magento system running in production is not a recommended practice. Depending on your system software, or other running extensions, running setup:upgrade may trigger undesired behaviors. As with installing any new software on your system, don't forget to take appropriate backup steps, and to test your new module in a development or staging environment before deploying to production.

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Compatibility Released
2.7.0 stable Fail Magento 2.4.7-2.4.8 Details 2026-03-10 06:27:40
2.6.13 stable Not tested Not yet tested Details 2026-01-30 08:56:56
2.6.12 stable Not tested Not yet tested Details 2025-09-10 12:31:36
2.6.11 stable Not tested Not yet tested Details 2025-07-17 05:13:40
2.6.10 stable Not tested Not yet tested Details 2025-05-13 14:13:53
2.6.9 stable Not tested Not yet tested Details 2024-12-09 11:26:56
2.6.8 stable Not tested Not yet tested Details 2024-11-20 06:55:27
2.6.7 stable Not tested Not yet tested Details 2024-08-12 09:40:40
2.6.6 stable Not tested Not yet tested Details 2024-06-20 07:10:11
2.6.5 stable Not tested Not yet tested Details 2024-03-14 11:55:45
2.6.4 stable Not tested Not yet tested Details 2023-12-21 13:16:32
2.6.3 stable Not tested Not yet tested Details 2023-10-04 14:16:04
2.6.2 stable Not tested Not yet tested Details 2023-05-15 09:38:10
2.6.1 stable Not tested Not yet tested Details 2023-03-27 11:58:11
2.6.0 stable Not tested Not yet tested Details 2023-02-20 12:40:09
2.5.1 stable Not tested Not yet tested Details 2022-04-13 14:08:52
2.5.0 stable Not tested Not yet tested Details 2022-03-22 09:45:08
2.4.0 stable Not tested Not yet tested Details 2022-01-31 08:48:27
2.3.2 stable Not tested Not yet tested Details 2022-01-11 15:07:14
2.3.1 stable Not tested Not yet tested Details 2021-12-15 15:34:44
2.3.0 stable Not tested Not yet tested Details 2021-10-04 10:23:04
2.2.4 stable Not tested Not yet tested Details 2021-10-04 10:16:33
2.2.3 stable Not tested Not yet tested Details 2021-07-12 11:22:59
2.2.2 stable Not tested Not yet tested Details 2021-06-08 13:15:37
2.2.1 stable Not tested Not yet tested Details 2021-05-12 12:49:33
2.2.0 stable Not tested Not yet tested Details 2021-04-26 08:52:34
2.1.1 stable Not tested Not yet tested Details 2021-04-26 08:32:04
2.1.0 stable Not tested Not yet tested Details 2021-01-25 10:32:27
2.0.4 stable Not tested Not yet tested Details 2020-10-29 10:16:38
2.0.3 stable Not tested Not yet tested Details 2020-06-17 06:41:36
2.0.2 stable Not tested Not yet tested Details 2019-10-14 13:39:51
1.4.3 stable Not tested Not yet tested Details 2019-10-14 13:29:06
2.0.1 stable Not tested Not yet tested Details 2019-08-15 12:56:30
1.4.1 stable Not tested Not yet tested Details 2018-05-25 10:24:12
1.4.0 stable Not tested Not yet tested Details 2018-05-01 14:49:00
1.3.5 stable Not tested Not yet tested Details 2018-05-01 14:31:52
1.3.4 stable Not tested Not yet tested Details 2017-12-08 23:15:27
1.3.2 stable Not tested Not yet tested Details 2017-03-06 16:41:53
1.3.1 stable Not tested Not yet tested Details 2016-11-01 10:15:17
1.3.0 stable Not tested Not yet tested Details 2016-10-31 17:38:28
1.2.0 stable Not tested Not yet tested Details 2016-10-28 14:27:11
1.1.0 stable Not tested Not yet tested Details 2016-08-10 17:28:50
1.0.0 stable Not tested Not yet tested Details 2016-06-08 01:32:30

No dependencies declared

This package's composer.json doesn't declare any required, suggested, replaced, or conflicting packages.

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.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Pass Pass
2.4.8 Pass Pass
2.4.9 not tested Fail di error

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.

Static analysis results
Tool Status Findings Summary
PHPCS Fail 1459 10 errors, 1449 warnings (ruleset: Magento2) — 1056 auto-fixable with phpcbf
PHPMD Warning 5 5 rule violations (UnusedLocalVariable:2, CyclomaticComplexity:1, NPathComplexity:1, MissingImport:1)
Cpd Pass 0
Composer validate Fail 1 invalid composer.json: 1 error (composer validate --strict)

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.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 118 118
2.4.8 117 117
2.4.9 Unknown Unknown

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

Unit tests results by Magento and PHP version
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

Integration tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Pass Pass
2.4.8 Pass not tested
2.4.9 Pass Error

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.

Security results
Tool Status Findings Summary
Composer audit Pass 0
Malware scan Pass 0
Authors
Make it pay

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.