faonni / module-tracking-link
faonni/module-tracking-link
Extension add Tracking Url in Shipment Email.
Magento2 Tracking Link
Extension add Tracking Url in Shipment Email.
Native shipment email doesn’t include a clickable tracking number link, just plain text one. The customer has to copy and then go to the courier site to get the tracking information. The extension make the tracking number a clickable link that will bring them to the carriers site and display the tracking information.
The extension supports all couriers which support shipping tracking.
Compatibility
Magento CE(EE) 2.0.x, 2.1.x, 2.2.x, 2.3.x, 2.4.x
Install
Install via Composer (recommend)
-
Go to Magento2 root folder
-
Enter following commands to install module:
For Magento CE(EE) 2.0.x, 2.1.x, 2.2.x, 2.3.x
composer require faonni/module-tracking-link:2.0.*For Magento CE(EE) 2.4.x
composer require faonni/module-tracking-link:2.4.*Wait while dependencies are updated.
Manual Installation
-
Create a folder {Magento root}/app/code/Faonni/TrackingLink
-
Download the corresponding latest version
-
Copy the unzip content to the folder ({Magento root}/app/code/Faonni/TrackingLink)
Completion of installation
-
Go to Magento2 root folder
-
Enter following commands:
php bin/magento setup:upgrade php bin/magento setup:di:compile php bin/magento setup:static-content:deploy (optional)
Configuration
In the Magento Admin Panel go to Stores > Configuration > Sales > Tracking Settings > Tracking Service Url.
Usage
Shipment Email
Service Tracking Page
Uninstall
Remove database data
This works only with modules defined as Composer packages.
-
Go to Magento2 root folder
-
Enter following commands to remove database data:
php bin/magento module:uninstall -r Faonni_TrackingLink
Remove Extension
-
Go to Magento2 root folder
-
Enter following commands to remove:
composer remove faonni/module-tracking-link
Completion of uninstall
-
Go to Magento2 root folder
-
Enter following commands:
php bin/magento setup:upgrade php bin/magento setup:di:compile php bin/magento setup:static-content:deploy (optional)
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.10 | stable | Not tested | Not yet tested Details | 2021-09-09 06:46:44 |
| 2.4.1 | stable | Pass | Magento 2.4.7-2.4.9 Details | 2021-09-09 06:46:13 |
| 2.4.0 | stable | Not tested | Not yet tested Details | 2020-09-28 06:45:21 |
| 2.0.9 | stable | Not tested | Not yet tested Details | 2019-05-19 11:19:06 |
| 2.0.8 | stable | Not tested | Not yet tested Details | 2018-12-17 20:11:57 |
| 2.0.7 | stable | Not tested | Not yet tested Details | 2018-10-10 21:05:46 |
| 2.0.6 | stable | Not tested | Not yet tested Details | 2018-06-07 09:53:58 |
| 2.0.5 | stable | Not tested | Not yet tested Details | 2018-02-03 13:39:11 |
| 2.0.4 | stable | Not tested | Not yet tested Details | 2018-01-11 20:00:00 |
| 2.0.3 | stable | Not tested | Not yet tested Details | 2017-12-13 23:09:32 |
| 2.0.2 | stable | Not tested | Not yet tested Details | 2017-11-09 08:55:17 |
| 2.0.1 | stable | Not tested | Not yet tested Details | 2017-10-16 18:30:31 |
Requires 4
| Package | Constraint |
|---|---|
| magento/framework | 103.0.* |
| magento/module-config | 101.2.* |
| magento/module-sales | 103.0.* |
| magento/module-shipping | 100.4.* |
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.
More from faonni
View vendorTurn 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.