picqer / magento2-plugin
picqer/magento2-plugin
Picqer Extended Integration for Magento 2
Picqer Extended Integration for Magento 2
Magento 2 Extensions for Picqer.
Installation:
This project can easily be installed through Composer.
composer require picqer/magento2-plugin
bin/magento module:enable Picqer_Integration
bin/magento setup:upgrade
Activate module
- Log onto your Magento 2 admin account and navigate to Stores > Configuration > Picqer > Webhooks
- Fill out the general configuration information:
- Active: Yes
- Picqer Subdomain: is the prefix of your domain name. If you log on to 'my-shop.picqer.com', then fill in 'my-shop'.
- Connection Key: can be found in Picqer > Settings > Webshops > Magento shop. Copy and paste in this field.
Orders will now be pushed to Picqer immediately.
Uninstall:
composer remove picqer/magento2-plugin
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.0.3 | stable | Pass | Magento 2.4.7-2.4.9 Details | 2022-05-03 08:24:56 |
| 1.0.2 | stable | Not tested | Not yet tested Details | 2021-07-20 13:05:33 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2020-09-16 13:38:29 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2019-04-29 11:59:50 |
Requires 3
| Package | Constraint |
|---|---|
| php | >=5.6.0 |
| ext-curl | * |
| ext-json | * |
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 |
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.
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.