yireo / magento2-salesblock2-by-email
yireo/magento2-salesblock2-by-email
Block transactions based on email matching
Yireo SalesBlock2ByEmail for Magento 2
This module is a helper-module for the Yireo_SalesBlock2 extension, that allows you to block orders from being placed, based on specific rules defined in the Magento Admin Panel.
This specific module allows you to match by a specific email address. When a word is added to match an email address, the word is matched case-insensitive and regardless of the position. For instance, the following matches would be found when an order is placed with the email address [email protected]:
info@example.org@example.orgExample
Installation
To install this module, use the following commands. First, install this module using composer. Note that this step will fail if the Yireo_SalesBlock2 is not installed yet.
composer require yireo/magento2-salesblock2-by-email
Once this module is installed via composer, you can enable it:
./bin/magento module:enable Yireo_SalesBlock2ByEmail
There are no further steps to take. The Yireo_SalesBlock2 module automatically picks up on things.
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.2.1] - 9 April 2024
Fixed
- Upgrade due to renamed PHP 8 class
Removed
- Removed unneeded module version
[2.2.0] - 16 April 2022
Fixed
- PHP 8 compatibility (and therefore Magento 2.4.4)
[2.1.0] - 18 February 2021
Added
- Implemented new debugger
[2.0.1] - 29 July 2020
Added
- Magento 2.4 compatibility
- Remove PHP dep from composer
[2.0.0] - July 2019
Added
- Initial public release
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 2.2.1 | stable | Fail | Not compatible Details | 2024-04-09 14:12:01 |
| 2.2.0 | stable | Not tested | Not yet tested Details | 2022-04-16 13:17:53 |
| 2.1.0 | stable | Not tested | Not yet tested Details | 2021-02-18 16:14:24 |
| 2.0.1 | stable | Not tested | Not yet tested Details | 2021-02-17 16:12:15 |
Requires 3
| Package | Constraint |
|---|---|
| magento/module-customer | ^101.0|^102.0|^103.0 |
| magento/module-quote | ^101.0 |
| yireo/magento2-salesblock2 | ^2.2 |
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.
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | not tested | not tested | ||
| 2.4.8 | not tested | not tested | ||
| 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.
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
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.