integer-net / magento2-session-unblocker
integer-net/magento2-session-unblocker
Module for Magento 2 that prevents session blocking between concurrent AJAX requests
Integer_Net Session Unblocker
This extension improves the performance of AJAX requests in Magento by reducing session locking, without having to disable locking in the cache backend (e.g. Redis)
Session locking keeps safe from race conditions from parallel requests, so disabling it completely can result in session data loss.
Instead we minimize the lock time by closing the session as soon as we have read it, if we do not need to write to it anymore.
Installation
- Install via composer
composer require integer-net/magento2-session-unblocker - Enable module
bin/magento setup:upgrade
Configuration
Zero configuration needed.
Change log
Please see CHANGELOG for more information on what has changed recently.
Testing
Magento Integration Tests
-
Configure test database in
dev/tests/integration/etc/install-config-mysql.php. Read more in the Magento docs. -
Copy
Test/Integration/phpunit.xml.distfrom the package todev/tests/integration/phpunit.xmlin your Magento installation. -
In that directory, run
../../../vendor/bin/phpunit
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.
0.1.0 - 2019-02-14
Added
- Closes session at the beginning of
customer/section/loadAJAX requests
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 0.1.5 | stable | Pass | Magento 2.4.7-2.4.9 Details | 2022-03-11 11:46:28 |
| 0.1.4 | stable | Not tested | Not yet tested Details | 2019-03-25 13:11:07 |
| 0.1.3 | stable | Not tested | Not yet tested Details | 2019-02-19 09:54:22 |
| 0.1.2 | stable | Not tested | Not yet tested Details | 2019-02-18 15:22:41 |
| 0.1.1 | stable | Not tested | Not yet tested Details | 2019-02-18 14:01:55 |
| 0.1.0 | stable | Not tested | Not yet tested Details | 2019-02-15 07:17:59 |
Requires 4
| Package | Constraint |
|---|---|
| magento/framework | ^100.1|^101.0|^102.0|^103.0 |
| magento/module-customer | ^101.0.0|^102.0.0|^103.0 |
| magento/module-catalog | ^101.0.0|^102.0.0|^103.0|^104.0 |
| php | >=7.1.0 |
Requires-dev 1
| Package | Constraint |
|---|---|
| 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.
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.
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 |
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 integer-net
View vendorGenerate RewriteMap files for Apache from Magento URL rewrites
Magento 2 Health Check
Create an "is_sale" product attribute and update it automatically from the "price" and "special_price" attributes
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.