ppl / module-missing-translation
Magento 2 admin and CLI tool for auditing and filling missing extension translation CSV rows.
PPL Missing Translation for Magento 2
PPL Missing Translation audits Magento extension translation CSV files and helps teams find missing, extra, equal, or TODO translation rows before packaging.
What It Adds
- Admin and CLI translation audit
- Report-only mode plus controlled append workflows
- Checks for missing keys, locale gaps, extra CSV keys, equal values, and TODO values
Requirements And Dependencies
- PHP: >=8.1
- Magento packages: magento/framework, magento/module-backend
- PPL packages: ppl/module-dev-tool, ppl/module-hub
- PHP extensions/other Composer requirements: ext-dom
Installation
Composer installation:
composer require ppl/module-missing-translation
bin/magento module:enable Ppl_Hub Ppl_DevTool Ppl_MissingTranslation
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:clean
Manual app/code installation: copy the module to app/code/Ppl/MissingTranslation, install the dependencies listed above, then run the same Magento commands without the Composer step.
First Use
- Install Ppl_Hub and Ppl_DevTool first.
- Run an audit in report-only mode before allowing writes.
- Use production write overrides only for controlled maintenance windows.
Admin entry: PPL Hub > PPL Missing Translation > Missing Translation Audit.
Integrations And Boundaries
- Useful before packaging any PPL module or custom Magento extension with i18n CSV files.
- Intended for development, QA, demo, or disposable staging environments. Do not treat generated data as production merchant data.
Localization
The package includes translation CSV files for 12 locales: de_DE, en_US, es_ES, fr_FR, it_IT, ja_JP, nl_NL, pl_PL, pt_BR, ru_RU, tr_TR, zh_CN.
Documentation
- Screenshot inventory:
docs/images/ppl-missing-translation/in the repository documentation tree
Support
Support contact: [email protected]. Include the module version, Magento version, enabled PPL companion modules, and the relevant admin or storefront screenshot when reporting an issue.
Changelog
1.2.0
- Adapted to the updated PPL Hub: admin navigation, ACL, and menu integration aligned to the PPL Hub 1.2 line
- Minor fixes and stability improvements
1.0.0
- Initial release.
- Audit translation CSV files and report missing, extra, source-equal, and TODO rows before packaging.
Requires 9
| Package | Constraint |
|---|---|
| ext-dom | * |
| ext-libxml | * |
| magento/framework | >=103.0.0 <104.0.0 |
| magento/module-backend | >=102.0.0 <103.0.0 |
| php | >=8.1 |
| ppl/module-dev-tool | ^1.2 |
| ppl/module-hub | ^1.2 |
| psr/log | ^1.0 || ^2.0 || ^3.0 |
| symfony/console | ^6.4 || ^7.0 |
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.
| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Pass | 0 | |
| PHPMD | Warning | 3 | 3 rule violations (NPathComplexity:2, CyclomaticComplexity:1) |
| Cpd | Warning | 2 | 2 duplicated chunks spanning 80 total lines (min-lines=5, min-tokens=70) |
| Composer validate | Info | 1 | valid; 1 advisory note (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
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 Pawel Pliousnin Digital Solutions
View vendorFoundation and anchor infrastructure for modular PPL admin reports; individual PPL report modules provide the actual reports.
Admin action board for Magento 2 that turns shop and PPL report signals into severity-scored task cards.
Standalone PPL Tracking & Privacy HV storefront package for Magento 2, compatible with Hyvä-based storefronts, with consent-aware behavioural tracking and data-subject tooling.
Privacy-first behavioural tracking, consent management and EU/DE data-subject-rights tooling. Requires Ppl_Hub and remains independent of search and filter modules.
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.