sebwite / magento2-product-downloads
sebwite/magento2-product-downloads
Magento 2.0 product download module
README
Magento 2.0 Product Downloads extension
[image: Alt text]
Adds a new tab on the product page to add downloads. This downloads will be shown in a tab on the product page. You can configure the allowed file extensions from the admin settings menu.
Screenshot
[image: Alt text]
Installation with composer (recommended)
- Include the repository:
composer require sebwite/magento2-product-downloads - Enable the extension:
php bin/magento --clear-static-content module:enable Sebwite_ProductDownloads - Upgrade db scheme:
php bin/magento setup:upgrade - Clear cache
Installation without composer
- Download zip file of this extension
- Place all the files of the extension in your Magento 2 installation in the folder app/code/Sebwite/ProductDownloads
- Enable the extension:
php bin/magento --clear-static-content module:enable Sebwite_ProductDownloads - Upgrade db scheme:
php bin/magento setup:upgrade - Clear cache
After these steps the extra tab on the products page will be visible. This extension has no config options (yet)
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 2.0.1 | stable | Fail | Not yet tested Details | 2016-10-06 14:47:12 |
| 1.0.2 | stable | Not tested | Not yet tested Details | 2016-07-09 12:07:25 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2016-01-20 14:53:30 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2016-01-14 08:15:42 |
Requires 2
| Package | Constraint |
|---|---|
| php | ~5.5.0|~5.6.0|~7.0.0 |
| magento/magento-composer-installer | * |
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 | not tested |
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.
| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Fail | 84 | 7 errors, 77 warnings (ruleset: Magento2) — 29 auto-fixable with phpcbf |
| PHPMD | Warning | 9 | 9 rule violations (UnusedLocalVariable:3, UnusedFormalParameter:3, IfStatementAssignment:1, CyclomaticComplexity:1, MissingImport:1) |
| Cpd | Pass | 0 | |
| Composer validate | Info | 2 | valid; 2 advisory notes (composer validate --strict) |
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.