Site Views

Standings

Shows a competition table for one project, built from the shared StandingsReader domain service — the same reader used by the admin Standings screen and by mod_joomleague_standings. The page only renders data where the project, its competition, season and sport type are all published (and the stage too, if one is set).

Menu item setup (request fields):

project_id — required, dropdown of published projects.
stage_id — number, defaults to 0 (whole project rather than one stage).

Menu item params (grouped into a Standings fieldset plus separate zones and form fieldsets):

highlight_entry_id — an entry to highlight in the table.
highlight_style — row, text, or none.
highlight_color_row / highlight_color_text — hex colors (fall back to #ffc107 / #000000 if invalid).
highlight_bold, highlight_italic, highlight_underline — toggles for the highlighted row/text.
limit — number of rows to show; when set and the table is longer than the limit, the visible window centers on the highlighted entry if one is set.
metric_codes — which metric columns to show, and in what order.
combined_score_format — collapses paired *_for/*_against metrics (e.g. goals for/against) into a single "x:y" column.
short_labels / short_label_tooltips — abbreviate column headers, with the full name as a tooltip.
responsive_columns — allow columns to collapse on narrow screens.
zone_top_enabled / zone_top_count (default 3) / zone_top_color (default #28a745) — highlight the top N rows (e.g. promotion/qualifying places).
zone_bottom_enabled / zone_bottom_count / zone_bottom_color (default #dc3545) — same for the bottom N rows (e.g. relegation).
form_enabled / form_count (default 5) — show a recent-form strip per entry. Only computed when the standings type isn't race_results and the sport profile's contest type is head-to-head.

Results

Lists a project's matches, grouped by round, with final scores where available. Requires the project (and its competition/season/sport type) to be published; only matches whose round and stage are both published are shown. Scores are only loaded for matches whose result status is final, read from the top-level score segment (parent_id IS NULL). Each match links through to its Program Item page.

Menu item request fields:

project_id — required, dropdown of published projects.
stage_id — dropdown of stages for the project (with an "all stages" option), shown only once a project is selected (showon="project_id!:0"); defaults to 0 (all stages).

Menu item params:

show_events — default on; when on, match events are loaded and shown.
show_venue — default on; when off, venue name and attendance are omitted from the listing.

Bracket

Renders a sport-neutral single/multi-round progression bracket for one stage of a project — built from published rounds, matches, participants and (for matches with a final result) their top-level score values. At least two published rounds are required in the stage or the view reports an empty bracket.

The page includes horizontal round-by-round navigation (prev/next buttons that scroll the bracket into view) and lands on the requested stage's position rather than the top-left corner. Clicking a participant's name highlights that entry's full path through the bracket — every match card containing that entry, and every connector line between two highlighted cards, is highlighted; clicking the same entry again clears it. This is tracked by the participant's stable project-entry ID, not by name, so it isn't confused by duplicate names.

Menu item request fields (both required):

project_id — dropdown of published projects.
stage_id — dropdown of stages, labeled <project name> - <stage name>.

This view has no params fieldset.

Team Plan

A single project entry's own fixture list — past and future matches, in schedule order — built on the same MatchesReader domain service intended to be shared with a future matches module and clubplan/nextmatch views. "Upcoming" is determined by scheduled start time being at or after now and the match being unplayed (not merely lacking a recorded result, which would otherwise wrongly flag old, never-entered historical matches as upcoming). Each fixture links through to its Program Item page.

Menu item request fields:

project_id — required, dropdown of published projects.
entry_id — the entry whose plan to show; not marked required because, like the standings module's entry field, its options depend on project_id which isn't known until the item has been saved once. Real enforcement happens server-side in TeamplanModel::getPlan().

Menu item params:

scope — all, upcoming, or played.
order_desc — reverse chronological order.
limit — number of matches to display (0 = no limit).
highlight_next — default on; highlights the next upcoming match.
show_round — default on; shows the round name per fixture.
show_venue — default on; shows the venue per fixture.

Program Item

The detail page for a single match: participants, final score (if the result status is final, broken down by score segment), match events, officials, lineup members, and any recorded statistics. Requires the match and its project/competition/season/sport type/stage/round to all be published.

Menu item request field:

match_id — required, dropdown listing matches as <project name> - <round name> #<match id>, most recent first.

This view has no params fieldset — it always shows everything it has data for (events, officials, lineup, statistics are simply omitted from the page when there's nothing to show).