elgentos / magento2-review-reminder
elgentos/magento2-review-reminder
Magento 2 Review reminder
Review Reminder Module for Magento 2
Overview
The Review Reminder Module for Magento 2 is a customizable tool that enables online shop owners to automate the process of sending review reminders to customers after their products have been delivered. This module provides a convenient way to request feedback and reviews from customers, helping to improve the reputation and credibility of your online store.
Features
-
Configuration Options: The module allows you to configure the review link and the complaint link according to your specific requirements. You can set the URLs for these links to direct customers to the appropriate pages where they can leave reviews or submit complaints.
-
Email Customization: You have the flexibility to configure different email addresses for each shop. This feature enables you to send review reminder emails from specific addresses associated with each shop, providing a more personalized and professional touch.
-
Delay Settings: The module allows you to set a specific delay period in days after the record creation before sending the review reminder email. This gives customers enough time to experience the product and provide a well-informed review.
Composer Installation
composer require elgentos/magento2-review-reminde2
Usage
After installing the module, it allows you to send review reminder emails based on a specified delay period after the record creation.
To configure the module, navigate to the admin panel of your Magento 2 store and follow these steps:
- Go to Stores > Configuration > Extensions > Elgentos/Review Reminder.
- Customize the review link and complaint link URLs to match your store's review and complaint pages.
- Configure the email address to be used for each shop.
- Adjust the delay period in days after which the review reminder email should be sent.
Contributing
We welcome contributions to enhance the functionality of the Review Reminder Module. If you would like to contribute, please create a pull request.
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
Requires 14
| Package | Constraint |
|---|---|
| php | ^8.0|^8.1|^8.2 |
| ext-json | * |
| magento/framework | ^103.0 |
| magento/module-amqp | ^100.4 |
| magento/module-asynchronous-operations | ^100.4 |
| magento/module-backend | ^102.0 |
| magento/module-config | ^101.2 |
| magento/module-cron | ^100.4 |
| magento/module-email | ^101.1 |
| magento/module-message-queue | ^100.4 |
| magento/module-sales | ^103.0 |
| magento/module-store | ^101.1 |
| phpseclib/phpseclib | ^3.0.19 |
| nesbot/carbon | ^2.67 |
Requires-dev 4
| Package | Constraint |
|---|---|
| bitexpert/phpstan-magento | ^0.30.1 |
| elgentos/testing-suite | ^0.1.1 |
| phpstan/extension-installer | ^1.3 |
| youwe/coding-standard-magento2 | ^2.0.0 |
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.