rafa/feadulta
1
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects Releases Wiki Activity

Add conservative Joomla-to-WordPress article link on legacy article pages #17

New Issue
Open
opened 2026-06-28 19:12:52 +00:00 by rafa · 0 comments
rafa commented 2026-06-28 19:12:52 +00:00
Owner
Copy Link
Copy Source

Labels: improvement

Context

  • During GA4 analysis we confirmed that a large share of current production traffic still lands on legacy Joomla article URLs.
  • We want a small migration aid on Joomla article pages: show a link to the same article in the new WordPress site when an equivalent WP URL exists.
  • The priority is to keep risk low because the Joomla legacy stack is fragile and we do not want to break it.

Goal

  • On Joomla article pages, render a visible but lightweight link such as Ver este artículo en la nueva web pointing to the matching WordPress permalink.

Constraints

  • Minimize changes to Joomla templates / runtime behavior.
  • Avoid invasive refactors or broad routing changes.
  • Prefer a narrowly scoped, reversible implementation.
  • If a matching WP article is not known, render nothing.

Possible implementation directions

  1. Use an existing mapping source if available in migration metadata.
    • Candidate keys may include legacy K2/article IDs and imported WP metadata already used by migration scripts.
  2. Inject the link only on article detail views, not on listings.
  3. Implement with the smallest safe hook possible:
    • Joomla template override, or
    • very small plugin/helper layer, or
    • server-side lookup from a static/generated mapping file if safer than live DB logic.
  4. Keep styling minimal and isolated.

Research questions

  • What is the safest place in the Joomla stack to inject this link without destabilizing legacy rendering?
  • Do we already have a reliable mapping from Joomla/K2 item to WP permalink in repo data or DB metadata?
  • Can we generate a static mapping file from WordPress/Joomla data and use that at render time to avoid heavy runtime logic?
  • Should the link appear near the title, near the meta block, or at the end of the article?

Acceptance criteria

  • On a Joomla article page with a known migrated WP equivalent, the page shows one clear link to the WP version.
  • On pages without a known mapping, nothing extra is shown.
  • No visible regressions on Joomla article rendering.
  • The implementation is documented and easy to disable/revert.

Suggested first step

  • Audit existing migration metadata and identify the safest low-touch insertion point before writing any Joomla code.
**Labels:** improvement Context - During GA4 analysis we confirmed that a large share of current production traffic still lands on legacy Joomla article URLs. - We want a small migration aid on Joomla article pages: show a link to the same article in the new WordPress site when an equivalent WP URL exists. - The priority is to keep risk low because the Joomla legacy stack is fragile and we do not want to break it. Goal - On Joomla article pages, render a visible but lightweight link such as `Ver este artículo en la nueva web` pointing to the matching WordPress permalink. Constraints - Minimize changes to Joomla templates / runtime behavior. - Avoid invasive refactors or broad routing changes. - Prefer a narrowly scoped, reversible implementation. - If a matching WP article is not known, render nothing. Possible implementation directions 1. Use an existing mapping source if available in migration metadata. - Candidate keys may include legacy K2/article IDs and imported WP metadata already used by migration scripts. 2. Inject the link only on article detail views, not on listings. 3. Implement with the smallest safe hook possible: - Joomla template override, or - very small plugin/helper layer, or - server-side lookup from a static/generated mapping file if safer than live DB logic. 4. Keep styling minimal and isolated. Research questions - What is the safest place in the Joomla stack to inject this link without destabilizing legacy rendering? - Do we already have a reliable mapping from Joomla/K2 item to WP permalink in repo data or DB metadata? - Can we generate a static mapping file from WordPress/Joomla data and use that at render time to avoid heavy runtime logic? - Should the link appear near the title, near the meta block, or at the end of the article? Acceptance criteria - On a Joomla article page with a known migrated WP equivalent, the page shows one clear link to the WP version. - On pages without a known mapping, nothing extra is shown. - No visible regressions on Joomla article rendering. - The implementation is documented and easy to disable/revert. Suggested first step - Audit existing migration metadata and identify the safest low-touch insertion point before writing any Joomla code.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
inma rafa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rafa/feadulta#17
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?