someplus / module-mage-content-reactions
someplus/module-mage-content-reactions
Content reactions (emoji) module for Magento 2 CMS pages
No README yet
The vendor hasn't published a README for this package. The latest version's install command is on the right.
Release Notes
[1.0.0] - 2024-01-13
Added
- Initial release of MageContentReactions for Adobe Commerce.
- Built-in support for 6 reaction types (Like, Love, Haha, Wow, Sad, Celebrate).
- Full Page Cache (FPC) compatibility using AJAX data sourcing.
- Comprehensive Admin Configuration panel:
- Globalization: Toggle the extension on or off.
- Security: Enable/Disable guest reactions.
- Customization: Choose which reactions to display.
- Targeting: Exclude specific CMS pages by identifier.
- Layout: Option to position the block before or after page content.
- Secure AJAX handling with CSRF validation and form key integration.
- Responsive frontend UI with modern CSS gradients and animations.
- Dark Mode support based on system preferences.
- PSR-4 compliant architecture and optimized database schema.
Requires 4
| Package | Constraint |
|---|---|
| magento/framework | >=103.0 |
| magento/module-cms | >=104.0 |
| magento/module-customer | >=103.0 |
| php | >=8.1 |
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.
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 Some Plus
View vendorMageAssist - AI-powered admin assistant for Adobe Commerce with OpenAI, Claude, and OpenRouter support
Magento 2 Free Shipping Progress Bar - Motivate customers to reach free shipping threshold with a dynamic progress bar displayed in header, mini cart, cart page, and checkout.
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.