integer-net / magento2-regenerate-coupon-uses

integer-net/magento2-regenerate-coupon-uses

Regenerate coupon uses via command line so coupons cannot be used twice.

  • Andreas von Studnitz
magento2-module Compatibility: Not compatible Code Quality: Warning Tests: N/A Security: Pass MIT

IntegerNet_RegenerateCouponUses Magento Module

Latest Version on Packagist
Software License
Supported Magento Versions


Regenerate coupon uses via command line so coupons cannot be used twice.

This can be used if the Message Queue consumer sales.rule.update.coupon.usage wasn't running successfully and coupon usages haven't been recorded.
Make sure that the consumer runs again after this command has been executed.

Installation

  1. Install it into your Magento 2 project with composer:

    composer require integer-net/magento2-regenerate-coupon-uses
    
  2. Enable module

    bin/magento setup:upgrade
    

Usage

Execute on the command line:

bin/magento coupon:usage:regenerate

Contributing

Please see CONTRIBUTING for details.

Security

If you discover any security related issues, please email [email protected] instead of using the issue tracker.

Credits

License

The MIT License (MIT). Please see License File for more information.

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]

Added

Changed

Removed

Fixed

Versions
Version Stability QA Status Compatibility Released
1.0.0 stable Fail Not compatible Details 2023-08-25 06:13:08

Requires 2

Package Constraint
php ~8.1
magento/framework ^103.0.0

Requires-dev 7

Package Constraint
roave/security-advisories dev-master
phpunit/phpunit ^6.0|^9.0
pds/skeleton ^1.0
phpro/grumphp ^v0.21.0
phpstan/phpstan ^0.12.0
squizlabs/php_codesniffer ^3.5
magento/magento-coding-standard @dev

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 not tested
2.4.8 not tested not tested
2.4.9 Fail di error 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 Warning 1 1 warning (ruleset: Magento2)
PHPMD Warning 1 1 rule violation (UnusedFormalParameter:1)
Cpd Pass 0
Composer validate Pass 0

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.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 3 3
2.4.8 3 3
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 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.

Security results
Tool Status Findings Summary
Composer audit Pass 0
Malware scan Pass 0
License
MIT
Authors

More from integer-net

View vendor
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.