JoomLeague Docs
JoomLeague 6.2 development documentationNot compatible with the JoomLeague 6.1.x component. Use a clean test installation.

Club, Team, Person & Venue Forms

These are reusable entities. Creating one does not automatically enter it into a project, except for the explicit Club creation switches described below.

Club form

Details

  • Name is the only required identity field.
  • Alias, Short name, Country code, Website and External code are optional.
  • Website uses Joomla URL validation. Country stores a code, not a translated country name.
  • Create new team (create_team, default No).
  • Create new venue (create_venue, default No).

On first save, enabled switches create records named from the club and link them back to that club. The team receives club_id; the venue receives owner_club_id. The switches are choices, not mandatory behavior.

Media

  • Logo is the current single club logo.
  • Media history is a repeatable table. Each row stores required media path, optional alt text, valid-from/to dates and notes. Mark Remove record to delete that history row on save.

Placeholder media does not count as a real uploaded logo in status displays.

History

  • Founded date / Dissolved date describe the organisation itself.
  • Name history repeats required historical name, optional short name, validity dates and notes. Use separate rows for every rename rather than overwriting history.

Description and Publishing

Description is a full-width editor. New clubs default to Published, Public access and ordering 0.

Team form

Details

  • Name is required.
  • Alias, Middle name and Short name support routing and compact layouts.
  • Club is optional; choosing no club stores no association.
  • Website and External code are optional.

A first/primary side should be named explicitly (for example Rakšice A) when the same club also has Rakšice B; do not create a duplicate club or venue to represent the reserve team.

Media

  • Logo is the team's current logo. If absent, presentation may inherit the club logo where supported.
  • Picture is a team photograph, not a second logo.
  • Media history records dated historical logos/media using the same row structure as the club.

JoomLeague stores one current team logo. Legacy JL3 migration maps the largest available club logo as the club source logo; it does not preserve three manually maintained logo sizes.

History, Description and Publishing

Name history supports repeated names with validity ranges and notes. Description is full width. New teams default to Published, Public access and ordering 0.

Person form

Details

  • First name, Last name, Nickname and Alias are optional at XML level, but provide enough identity to distinguish the person.
  • Country code is optional.
  • Contact links an existing Joomla Contact and is optional.
  • Club is optional and represents the person's general association, not a project roster assignment.
  • External code stores a source/federation ID.

Biography

Birth date and Death date are date-only optional values. Do not use placeholder dates for unknown information.

Media and Description

Picture stores one current person image. Description uses a full-width editor. The public visibility chain also respects Published and Access.

Venue form

Details

  • Name is required.
  • Alias, Short name, Nickname and External code are optional.
  • Owner club is optional. One club can own one venue used by multiple teams; do not duplicate a venue for A/B teams.

Location

  • Address, Postal code, City, Region, Country code.
  • Latitude / Longitude accept numeric coordinates.
  • Timezone can override inherited project/system interpretation for the physical location.

Facilities

Capacity is numeric and optional; Website is URL-validated.

Media, Description and Publishing

Picture represents the venue. Description is a full-width editor. New venues default to Published, Public access and ordering 0.

Shared publishing fields

  • Published controls frontend availability but does not enroll the entity in any project.
  • Access is a Joomla view level.
  • Ordering is a fallback list order where semantic ordering is absent.
  • UUID supports stable exchange; ID is the local database key.

After creating entities, add teams/people/groups as project entries from the Project Panel. A club itself is not a project participant.

Custom Field tabs

Published Joomla Field Groups assigned to the current entity context appear as additional full-width tabs in these edit forms. Their values use Joomla's native validation, language and access rules. Configuration and public display are documented in Custom Fields.

← Foundation Form Reference Sport Catalog Form Reference →