MokoConsulting/MokoDoliJoomShop
1
0
Fork 0
generated from MokoConsulting/Template-Joomla
Code Issues 25 Pull Requests Releases 1 Wiki Activity

Access control (ACL) #25

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

Summary

Joomla ACL integration for component permissions.

Requirements

  • Component-level ACL (manage products, view orders, manage settings)
  • Frontend purchase permissions (guest vs registered)
  • Admin section access per role
  • Category-level viewing permissions

Acceptance Criteria

  • ACL configurable in component options
  • Admin sections respect permissions
  • Purchase restricted by checkout mode setting
  • Category viewing respects access levels
## Summary Joomla ACL integration for component permissions. ## Requirements - Component-level ACL (manage products, view orders, manage settings) - Frontend purchase permissions (guest vs registered) - Admin section access per role - Category-level viewing permissions ## Acceptance Criteria - [ ] ACL configurable in component options - [ ] Admin sections respect permissions - [ ] Purchase restricted by checkout mode setting - [ ] Category viewing respects access levels
jmiller added the priority/lowtype/featurearea/adminarea/security labels 2026-05-21 20:06:20 +00:00
Sign in to join this conversation.
Labels
Clear labels
area/admin
Administrator backend
 area/cart
Shopping cart
 area/checkout
Checkout and order flow
 area/database
Database schema or queries
 area/dolibarr-api
Dolibarr REST API integration
 area/frontend
Site/storefront display
 area/products
Product catalog
 area/security
Security and authentication
 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
 type/bug
Something is broken
 type/docs
Documentation
 type/enhancement
Improvement to existing feature
 type/feature
New feature or functionality
 version-drift
Version mismatch across files
 work-in-progress
Draft or incomplete work
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/security priority/low type/feature
Type Task
Status —
Priority —
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/MokoDoliJoomShop#25
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?