MokoConsulting/MokoJoomBackup
1
0
Fork 0
Code Issues 30 Pull Requests 1 Packages Projects Releases 1 Wiki Activity

Actionlog plugin - user action logging #31

New Issue
Open
opened 2026-06-04 17:15:58 +00:00 by jmiller · 0 comments
jmiller commented 2026-06-04 17:15:58 +00:00
Owner
Copy Link
Copy Source

Summary

New plg_actionlog_mokobackup plugin that logs MokoJoomBackup actions to Joomla's User Action Logs.

Logged Events

Event Trigger
Profile created onContentAfterSave (context: com_mokobackup.profile, isNew=true)
Profile updated onContentAfterSave (context: com_mokobackup.profile, isNew=false)
Profile deleted onContentAfterDelete (context: com_mokobackup.profile)
Backup record deleted onContentAfterDelete (context: com_mokobackup.backup)
Backup completed onMokoBackupAfterRun (success=true)
Backup failed onMokoBackupAfterRun (success=false)

Implementation

  • Writes directly to #__action_logs with parameterized language keys
  • BackupEngine dispatches onMokoBackupAfterRun event after both success and failure paths
  • Event payload: success, record_id, description, profile_id, origin

Files

New

  • src/packages/plg_actionlog_mokobackup/ (full plugin directory)

Modified

  • src/packages/com_mokobackup/src/Engine/BackupEngine.php - added dispatchAfterRun() and Event import
## Summary New `plg_actionlog_mokobackup` plugin that logs MokoJoomBackup actions to Joomla's User Action Logs. ## Logged Events | Event | Trigger | |---|---| | Profile created | `onContentAfterSave` (context: `com_mokobackup.profile`, isNew=true) | | Profile updated | `onContentAfterSave` (context: `com_mokobackup.profile`, isNew=false) | | Profile deleted | `onContentAfterDelete` (context: `com_mokobackup.profile`) | | Backup record deleted | `onContentAfterDelete` (context: `com_mokobackup.backup`) | | Backup completed | `onMokoBackupAfterRun` (success=true) | | Backup failed | `onMokoBackupAfterRun` (success=false) | ## Implementation - Writes directly to `#__action_logs` with parameterized language keys - `BackupEngine` dispatches `onMokoBackupAfterRun` event after both success and failure paths - Event payload: `success`, `record_id`, `description`, `profile_id`, `origin` ## Files ### New - `src/packages/plg_actionlog_mokobackup/` (full plugin directory) ### Modified - `src/packages/com_mokobackup/src/Engine/BackupEngine.php` - added `dispatchAfterRun()` and `Event` import
Sign in to join this conversation.
Labels
Clear labels
component: admin
Admin UI and views
 component: api
REST API
 component: engine
Backup/restore engine
 component: remote
Remote storage (FTP/GDrive)
 component: scheduler
Scheduled tasks
 priority: critical
Must fix before release
 priority: high
Important for release
 priority: low
Nice to have
 priority: medium
Normal priority
 status: blocked
Blocked by dependency
 status: ready
Ready for development
 type: bug
Something is broken
 type: docs
Documentation
 type: feature
New feature or enhancement
 type: testing
Testing and QA
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoJoomBackup#31
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?