MokoConsulting/MokoJoomStoreLocator
1
0
Fork 0
Code Issues 11 Pull Requests Releases Wiki Activity

Access control (ACL) #23

New Issue
Closed
opened 2026-05-21 17:25:57 +00:00 by jmiller · 0 comments
jmiller commented 2026-05-21 17:25:57 +00:00
Owner
Copy Link
Copy Source

Summary

Joomla ACL integration for granular permission control.

Requirements

  • Component-level ACL (manage, create, edit, delete, edit.state)
  • Category-level permissions
  • Frontend viewing permissions per category
  • Admin access levels per section

Acceptance Criteria

  • ACL permissions configurable in component options
  • Category permissions override component defaults
  • Frontend respects viewing access levels
  • Admin sections respect user permissions
## Summary Joomla ACL integration for granular permission control. ## Requirements - Component-level ACL (manage, create, edit, delete, edit.state) - Category-level permissions - Frontend viewing permissions per category - Admin access levels per section ## Acceptance Criteria - [ ] ACL permissions configurable in component options - [ ] Category permissions override component defaults - [ ] Frontend respects viewing access levels - [ ] Admin sections respect user permissions
jmiller added the priority/lowtype/featurearea/componentarea/admin labels 2026-05-21 17:25:57 +00:00
Sign in to join this conversation.
Labels
Clear labels
area/admin
Administrator interface
 area/component
Core component (com_mokojoomstorelocator)
 area/database
Database schema or queries
 area/frontend
Site/frontend display
 area/import-export
Data import/export features
 area/module-map
Map module (mod_mokojoomstorelocator_map)
 area/module-search
Search module (mod_mokojoomstorelocator_search)
 priority/critical
Must have for v1.0
 priority/high
Important for initial release
 priority/low
Future enhancement
 priority/medium
Nice to have for v1.0
 status: pending-testing
Implementation done, awaiting test proofs before close
 status: pending-testing
Implementation done, awaiting test proofs before close
 type/bug
Something is broken
 type/docs
Documentation
 type/enhancement
Improvement to existing feature
 type/feature
New feature or functionality
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 area/admin area/component priority/low type/feature
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoJoomStoreLocator#23
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?