kiwicommerce / module-admin-activity
kiwicommerce/module-admin-activity
Magento 2 - Admin Activity
Magento 2 - Admin Activity by KiwiCommerce
- Easily track every admin activity like add, edit, delete, print, view, mass update etc.
- Failed attempts of admin login are recorded as well. You get access to the user’s login information and IP address.
- Track page visit history of admin.
- Track fields that have been changed from the backend.
- Allow administrator to revert the modification.
Installation
-
Composer Installation
- Navigate to your Magento root folder
cd path_to_the_magento_root_directory - Then run the following command
composer require kiwicommerce/module-admin-activity - Make sure that composer finished the installation without errors.
- Navigate to your Magento root folder
-
Command Line Installation
- Backup your web directory and database.
- Download Admin Activity Log installation package from here
- Navigate to your Magento root folder
cd path_to_the_magento_root_directory - Upload contents of the Admin Activity Log installation package to your Magento root directory.
- Then run the following command
php bin/magento module:enable KiwiCommerce_AdminActivity
- After installing the extension, run the following command
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
php bin/magento cache:flush
- Log out from the backend and log in again.
Find More details on KiwiCommerce
Where will it appear in the Admin Panel
Admin Activity Log
Go to System > Admin Activity by KiwiCommerce > Admin Activity. Here you can See the list of admin activity logs and page visit history.
- Page Visit History
By clicking View in each admin activity log, you can see the slider with admin activity log details.
Login Activity
Go to System > Admin Activity by KiwiCommerce > Login Activity. Here you can See the list of login activity logs.
Configuration
You need to follow this path. System > Admin Activity by KiwiCommerce > Configuration
- General configuration
- Allow Module Section
Need Additional Features?
Feel free to get in touch with us at https://kiwicommerce.co.uk/get-in-touch/
Other KiwiCommerce Extensions
- Magento 2 Cron Scheduler
- Magento 2 Login As Customer
- Magento 2 Inventory Log
- Magento 2 Enhanced SMTP
Contribution
Well unfortunately there is no formal way to contribute, we would encourage you to feel free and contribute by:
- Creating bug reports, issues or feature requests on Github
- Submitting pull requests for improvements.
We love answering questions or doubts simply ask us in issue section. We're looking forward to hearing from you!
- Follow us @KiwiCommerce
- Email Us
- Have a look at our documentation
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.4 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2018-07-02 07:13:22 |
| 1.0.3 | stable | Not tested | Not yet tested Details | 2018-06-13 12:00:57 |
| 1.0.2 | stable | Not tested | Not yet tested Details | 2018-06-09 12:18:40 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2018-06-08 12:12:15 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2018-06-08 12:12:15 |
No dependencies declared
This package's composer.json doesn't declare any required, suggested, replaced, or conflicting packages.
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 | Fail | 560 | 17 errors, 543 warnings (ruleset: Magento2) — 275 auto-fixable with phpcbf |
| PHPMD | Warning | 40 | 40 rule violations (MissingImport:12, CyclomaticComplexity:6, UnusedLocalVariable:4, ExcessiveClassComplexity:3, UnusedFormalParameter:3) |
| Cpd | Pass | 0 | |
| 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.
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.