This PR is in preparation of PR #47459

Convert the positional argument arrays passed to onContentPrepare, onContentAfterTitle, onContentBeforeDisplay and onContentAfterDisplay into named arguments (context, subject, params, page).

These events resolve to ContentPrepareEvent (and its AfterTitleEvent / BeforeDisplayEvent / AfterDisplayEvent subclasses), which today rely on the ReshapeArgumentsAware trait to remap positional arrays onto named keys. Once that trait is removed (PR #47459) a positional array would fail the required-key validation with a BadMethodCallException, so these call sites must pass named arguments. The change is compatible with the current code as well, since the constructors accept named arguments directly.

The pass-by-reference markers are dropped: the subject is always an object, so plugin mutations propagate by handle without a reference.

• I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.

Build with help of AI - reviewed.

Summary of Changes

Converts the positional argument arrays in triggerEvent() calls for the four content-display events — onContentPrepare, onContentAfterTitle, onContentBeforeDisplay, onContentAfterDisplay — into named-key arrays (context, subject, params, page), and drops the now-unnecessary & by-reference markers. Pure refactor across 12 files; no behaviour change intended.

Testing Instructions

• Code review and testing:

Testing Instructions

Setup

1. Install this branch on a Joomla 6.2-dev nightly with the default sample data.

   • You can install the prebuild package (at the bottom of the checks list)
   • or you can add the patch with the Patchtester to a Joomla 6.2-dev nightly build
   • or you can checkout this branch from upstream

2. Make sure the core content plugins are enabled so the events output is visible:
   Fields - (custom fields render via the title/before/after events), Content - Email Cloaking, Content - Page Break, Content - Load Modules ({loadposition} / {loadmodule}).

3. Create one custom field each for Articles, Contacts, Users, and Categories, set to render in different positions (after title / before content / after content).

4. In one article's intro text, add an email address and a {loadposition } for a published module.
   Functional checks

For each context below the page must render with custom fields in the correct slots, the email cloaked, and the loaded module visible — proving the events fired and mutated the text:

• Archive (Archive/HtmlView → com_content.archive) — Archived Articles menu item
• Featured (Featured/HtmlView → com_content.featured) — Featured Articles menu item
• Category blog + list (Category/HtmlView → com_content.category) — both menu item types
• Category description (tmpl/category/blog.php + layouts/.../category_default.php → *.categories) — page header shows the category's own custom fields / plugin output
• Shared CategoryView (libraries/.../CategoryView → *.category) — a com_contact or com_newsfeeds category listing
• Single contact (Contact/HtmlView → com_contact.contact) — fields + cloaked email in misc/text
• Contact linked-user fields (Contact/HtmlView → com_users.user) — set the contact's Linked User and enable "show user custom fields"
• User profile (Profile/HtmlView → com_users.user) — front-end profile page shows user custom fields
• Tagged items (Tag/HtmlView → com_tags.tag) — Tagged Items page
• Newsflash module (mod_articles_news → com_content.article) — intro text shows processed plugin output
• Smart Search (com_finder/.../Helper → com_finder.indexer) — rebuild the index (no fatal), then search returns plugin-prepared text
• API single article (JsonapiView → com_content.article) — GET /api/index.php/v1/content/articles/{id} returns prepared content + custom field values

Regression checks (the by-reference removal)

• Enable a third-party content plugin that modifies $article->text (or write a small one) and confirm its changes still appear on an article — proves dropping &$item didn't break mutation.
• With display_errors on, confirm no Only variables should be passed by reference notices and no Undefined array key warnings from the event objects.

Before/after comparison

• Screenshot each view above on unpatched 6.2-dev and on this branch — output must be identical. Any visible difference is a bug.

Actual result BEFORE applying this Pull Request

Site works

Expected result AFTER applying this Pull Request

Site works

Every view renders exactly as on 6.2-dev: custom fields, cloaked emails, loaded modules, and third-party plugin output all appear unchanged, with no PHP notices.

Link to documentations

Please select:

• Documentation link for guide.joomla.org:

• No documentation changes for guide.joomla.org needed

• Pull Request link for manual.joomla.org:

• No documentation changes for manual.joomla.org needed