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

Test: onContentBeforeDisplay Joomla 5/6 compatibility fix #74

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

Test: Article Editor Status Badges

What changed

Fixed onContentBeforeDisplay to accept Joomla 5/6 BeforeDisplayEvent object.

Steps to test

  1. Navigate to any article that has been cross-posted
  2. Verify cross-post status badges appear (green/red/yellow) in the admin article view
  3. Verify NO "Argument must be of type string, BeforeDisplayEvent given" error
  4. Check both article list view and single article edit view

Labels

type: testing, priority: critical

## Test: Article Editor Status Badges ### What changed Fixed onContentBeforeDisplay to accept Joomla 5/6 BeforeDisplayEvent object. ### Steps to test 1. Navigate to any article that has been cross-posted 2. Verify cross-post status badges appear (green/red/yellow) in the admin article view 3. Verify NO "Argument must be of type string, BeforeDisplayEvent given" error 4. Check both article list view and single article edit view ### Labels `type: testing`, `priority: critical`
jmiller commented 2026-05-29 04:12:44 +00:00
Author
Owner
Copy Link
Copy Source

Branch created: feature/74-test-oncontentbeforedisplay-joomla-5-6-c

git fetch origin
git checkout feature/74-test-oncontentbeforedisplay-joomla-5-6-c
Branch created: [`feature/74-test-oncontentbeforedisplay-joomla-5-6-c`](https://git.mokoconsulting.tech/MokoConsulting/MokoJoomCross/src/branch/feature/74-test-oncontentbeforedisplay-joomla-5-6-c) ```bash git fetch origin git checkout feature/74-test-oncontentbeforedisplay-joomla-5-6-c ```
Sign in to join this conversation.
Labels
Clear labels
pending: testing
Implemented, awaiting testing
 priority: critical
Must have for MVP
 priority: high
Important, near-term
 priority: low
Nice to have
 priority: medium
Standard priority
 type: api
API endpoint
 type: feature
New feature
 type: infrastructure
Build, CI/CD, tooling
 type: integration
Platform integration
 type: migration
Data migration
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 Critical
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#74
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?