MokoConsulting/MokoJoomCross
1
0
Fork 0
Code Issues 105 Pull Requests Releases 1 Wiki Activity

Test: Evergreen content re-sharing #58

New Issue
Open
opened 2026-05-29 04:12:31 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-29 04:12:31 +00:00
Owner
Copy Link
Copy Source

Test: Evergreen Feature

What changed

  • Per-article evergreen toggle + interval field in Cross-Posting fieldset
  • Global config: enable/disable, default interval, max per run
  • QueueProcessor::processEvergreen() finds due articles and re-queues

Steps to test

  1. Edit an article → Cross-Posting tab → enable Evergreen Content
  2. Set interval to 1 day (for testing)
  3. Publish the article → verify initial cross-post succeeds
  4. In Components → MokoJoomCross → Options → Evergreen tab: verify settings
  5. Wait for next task scheduler run (or trigger manually)
  6. After interval elapses, verify article is re-queued automatically
  7. Check Activity Logs for "Evergreen re-share queued" message

Expected

  • Evergreen toggle and interval only visible when Skip = No
  • Re-shares respect the configured interval
  • Max per run limit prevents flooding
  • Duplicate guard prevents double-queuing

Labels

type: testing, priority: medium

## Test: Evergreen Feature ### What changed - Per-article evergreen toggle + interval field in Cross-Posting fieldset - Global config: enable/disable, default interval, max per run - QueueProcessor::processEvergreen() finds due articles and re-queues ### Steps to test 1. Edit an article → Cross-Posting tab → enable **Evergreen Content** 2. Set interval to 1 day (for testing) 3. Publish the article → verify initial cross-post succeeds 4. In Components → MokoJoomCross → Options → Evergreen tab: verify settings 5. Wait for next task scheduler run (or trigger manually) 6. After interval elapses, verify article is re-queued automatically 7. Check Activity Logs for "Evergreen re-share queued" message ### Expected - Evergreen toggle and interval only visible when Skip = No - Re-shares respect the configured interval - Max per run limit prevents flooding - Duplicate guard prevents double-queuing ### Labels `type: testing`, `priority: medium`
jmiller commented 2026-05-29 04:12:33 +00:00
Author
Owner
Copy Link
Copy Source

Branch created: feature/58-test-evergreen-content-re-sharing

git fetch origin
git checkout feature/58-test-evergreen-content-re-sharing
Branch created: [`feature/58-test-evergreen-content-re-sharing`](https://git.mokoconsulting.tech/MokoConsulting/MokoJoomCross/src/branch/feature/58-test-evergreen-content-re-sharing) ```bash git fetch origin git checkout feature/58-test-evergreen-content-re-sharing ```
Sign in to join this conversation.
Labels
Clear labels
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 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/MokoJoomCross#58
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?