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

Exclude dirs/files/tables as editable table rows #33

New Issue
Open
opened 2026-06-05 01:26:40 +00:00 by jmiller · 0 comments
jmiller commented 2026-06-05 01:26:40 +00:00
Owner
Copy Link
Copy Source

Summary

Replace the textarea-based exclude fields (dirs, files, tables) with a dynamic table UI where each exclusion is an individual row that can be added or removed.

Current

  • Newline-separated textarea for each exclusion type
  • Error-prone, no validation per entry

Proposed

  • Repeatable subform or dynamic table with add/remove buttons
  • Each row is a single path/pattern/table name
  • Easier to manage, especially for long exclusion lists

Exclude Tables

  • Auto-populate with all database tables from the site
  • Checkbox/selection markers beside each table
  • Pre-check tables that are currently excluded
  • Users toggle tables on/off instead of typing names manually
## Summary Replace the textarea-based exclude fields (dirs, files, tables) with a dynamic table UI where each exclusion is an individual row that can be added or removed. ## Current - Newline-separated textarea for each exclusion type - Error-prone, no validation per entry ## Proposed - Repeatable subform or dynamic table with add/remove buttons - Each row is a single path/pattern/table name - Easier to manage, especially for long exclusion lists ## Exclude Tables - Auto-populate with all database tables from the site - Checkbox/selection markers beside each table - Pre-check tables that are currently excluded - Users toggle tables on/off instead of typing names manually
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
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
Type Bug
Status —
Priority —
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#33
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?