MokoConsulting/MokoSuiteCross
1
0
Fork 0
Code Issues 27 Pull Requests 1 Releases 5 Wiki Activity

feature: category routing rules have no admin UI -- table exists but no CRUD #237

New Issue
Open
opened 2026-06-29 14:21:31 +00:00 by jmiller · 1 comment
jmiller commented 2026-06-29 14:21:31 +00:00
Owner
Copy Link
Copy Source

Description

The #__mokosuitecross_category_rules table exists in the install SQL and CrossPostDispatcher::dispatch() queries it to filter services by Joomla category. However, there is no admin interface to manage these rules:

  • No CategoryRulesModel or CategoryRulesController
  • No view/template for managing rules
  • The config.xml has a category_rules fieldset but it only contains a note field -- no actual form controls

Users currently have no way to create or manage category routing rules without direct database access.

Suggested implementation

Add a Category Rules management view accessible from the component sidebar or a tab within the Services view:

  • List view showing category -> service mappings
  • Edit form with category dropdown + service multi-select
  • Or: add a "Category Rules" tab to the Service edit form with category checkboxes

Impact

  • Severity: Medium -- feature is documented and the backend exists, but inaccessible to users
  • Affected files: Need new Model, Controller, View, and template files
## Description The `#__mokosuitecross_category_rules` table exists in the install SQL and `CrossPostDispatcher::dispatch()` queries it to filter services by Joomla category. However, there is no admin interface to manage these rules: - No `CategoryRulesModel` or `CategoryRulesController` - No view/template for managing rules - The `config.xml` has a `category_rules` fieldset but it only contains a `note` field -- no actual form controls Users currently have no way to create or manage category routing rules without direct database access. ## Suggested implementation Add a Category Rules management view accessible from the component sidebar or a tab within the Services view: - List view showing category -> service mappings - Edit form with category dropdown + service multi-select - Or: add a "Category Rules" tab to the Service edit form with category checkboxes ## Impact - **Severity**: Medium -- feature is documented and the backend exists, but inaccessible to users - **Affected files**: Need new Model, Controller, View, and template files
jmiller commented 2026-06-29 14:21:35 +00:00
Author
Owner
Copy Link
Copy Source

Branch created: feature/237-feature-category-routing-rules-have-no-a

git fetch origin
git checkout feature/237-feature-category-routing-rules-have-no-a
Branch created: [`feature/237-feature-category-routing-rules-have-no-a`](https://git.mokoconsulting.tech/MokoConsulting/MokoSuiteCross/src/branch/feature/237-feature-category-routing-rules-have-no-a) ```bash git fetch origin git checkout feature/237-feature-category-routing-rules-have-no-a ```
Sign in to join this conversation.
Labels
No items
No labels
Priority Medium
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/MokoSuiteCross#237
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?