Extract content sync handlers from core plugin #158

New Issue

2026-06-04T18:28:33Z

jmiller commented

2026-06-04 18:28:33 +00:00

Content sync API handlers should move to com_mokowaas API controller:

handleSyncAction() - sync trigger
handleSyncReceiveAction() - sync receiver
handleSyncClearAction() - sync clear
handleSyncPushAction() - bulk sync push

ContentSyncService and ContentSyncReceiver already exist as separate classes. The core plugin just routes API calls to them.

Content sync API handlers should move to com_mokowaas API controller: - [ ] handleSyncAction() - sync trigger - [ ] handleSyncReceiveAction() - sync receiver - [ ] handleSyncClearAction() - sync clear - [ ] handleSyncPushAction() - bulk sync push ContentSyncService and ContentSyncReceiver already exist as separate classes. The core plugin just routes API calls to them.

jmiller commented

2026-06-04 18:28:37 +00:00

Branch created: feature/158-extract-content-sync-handlers-from-core-

git fetch origin
git checkout feature/158-extract-content-sync-handlers-from-core-

Branch created: [`feature/158-extract-content-sync-handlers-from-core-`](https://git.mokoconsulting.tech/MokoConsulting/MokoWaaS/src/branch/feature/158-extract-content-sync-handlers-from-core-) ```bash git fetch origin git checkout feature/158-extract-content-sync-handlers-from-core- ```

jmiller closed this issue

2026-06-06 16:17:53 +00:00

Sign in to join this conversation.

Priority -

Type Task

Status —

Priority —

Type —

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoSuite#158