ppl / module-report-admin-daily-digest
Scheduled Magento 2 admin email digest assembled from installed PPL Reports modules.
PPL Report Admin Daily Digest for Magento 2
PPL Report Admin Daily Digest sends a scheduled admin email digest assembled from installed PPL report modules.
What It Adds
- Digest email configuration for installed reports
- Daily, weekly, or monthly scheduling options
- Report inclusion switches for installed report data
Requirements And Dependencies
- PHP: >=8.1
- Magento packages: magento/module-backend, magento/module-config, magento/module-email, magento/module-reports, magento/module-sales, magento/module-store
- PPL packages: ppl/module-report-core
Installation
Composer installation:
composer require ppl/module-report-admin-daily-digest
bin/magento module:enable Ppl_Hub Ppl_ReportCore Ppl_ReportAdminDailyDigest
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:clean
Manual app/code installation: copy the module to app/code/Ppl/ReportAdminDailyDigest, install the dependencies listed above, then run the same Magento commands without the Composer step.
First Use
- Install Ppl_ReportCore and at least one report module that the digest can include.
- Configure recipient email and schedule under PPL Reports.
- Run cron or wait for the scheduled send time.
Admin entry: Stores > Configuration > PPL Reports > Admin Report Digest Email.
Integrations And Boundaries
- Uses installed PPL report modules and Report Core scheduled infrastructure.
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-report-admin-daily-digest/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.2
- Fixed the manual Send test email now action so it sends a diagnostic test email even when no optional digest sections are available.
- Kept scheduled cron delivery behavior unchanged: regular digests still skip and log a warning when no sections can be built.
- Added configuration guidance for optional report modules and empty-section test email behavior.
1.0.1
- Added configurable digest frequency: daily, weekly, or monthly.
- Added weekly send day and monthly send day configuration.
- Updated digest periods so daily uses yesterday, weekly uses the last 7 days, and monthly uses the last 30 days.
- Added frequency-aware send guards so weekly and monthly digests are sent once per configured period.
1.0.0
Initial release.
Features:
- Daily admin email digest
- Optional report-module aggregation
- Cron-based delivery with once-per-day cache guard
- Configuration under PPL Reports
Requires 12
| Package | Constraint |
|---|---|
| magento/framework | >=103.0.0 <104.0.0 |
| magento/module-backend | >=102.0.0 <103.0.0 |
| magento/module-config | >=101.2.0 <102.0.0 |
| magento/module-cron | >=100.4.0 <101.0.0 |
| magento/module-email | >=101.1.0 <102.0.0 |
| magento/module-reports | >=100.4.0 <101.0.0 |
| magento/module-sales | >=103.0.0 <104.0.0 |
| magento/module-store | >=101.1.0 <102.0.0 |
| php | >=8.1 |
| ppl/module-hub | ^1.2 |
| ppl/module-report-core | ^1.2 |
| psr/log | ^1.0 || ^2.0 || ^3.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.
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.