JoomLeague 6.2.0-dev7 is available for testing

Announcements
1

JoomLeague 6.2.0-dev7 is now available for testing.

This release is another major step towards JoomLeague 6.2. It expands the administration interface, strengthens the sport-neutral data model and adds further frontend views, modules and fixes identified during testing.

Highlights

  • expanded and modernised administration,
  • bundled sport profiles for 15 sports,
  • global profile templates and project-specific template settings,
  • integration with Joomla Custom Fields,
  • additional sport-neutral frontend views,
  • a complete suite of 16 frontend modules,
  • improvements to canonical URLs, Open Graph metadata and Schema.org output,
  • fixes and validation improvements identified during migration and demo testing,
  • verified installation and database behaviour on both MariaDB/MySQL and PostgreSQL.

Important compatibility notice

JoomLeague 6.2 uses a new architecture and database model. It is not directly compatible with JoomLeague 6.1.x.

Do not install it as a normal in-place upgrade over a production JoomLeague 6.1.x website. Existing data must be converted with the new migration service:

migrate.joomleague.eu

Always create and verify a complete website and database backup before testing a development release. We strongly recommend performing the first migration on a separate testing website.

Preliminary release schedule

  • Beta: 15 September 2026
  • Release Candidate: 1 October 2026
  • Stable: planned for the Joomla 6.2 stable release date, currently expected on 13 October 2026

These dates are targets rather than guarantees and may change depending on testing results and the final Joomla 6.2 release schedule.

Download and feedback

The latest package and update information are available at:

downloads.joomleague.eu

Please test this release on a non-production website and report reproducible problems in the Bugs & Issues category. Include the Joomla version, PHP version, database driver and exact steps needed to reproduce the problem.

Thank you to everyone testing JoomLeague and providing feedback.

2

Clean install give a erorr.
JInstaller::Instalacja: Błąd SQL Can’t create table `DBXXX`.`mqqnk_joomleague_project_stage` (errno: 150 “Foreign key constraint is incorrectly formed”).

3

Hello,

Thank you for reporting this error. I verified a clean installation of the same package on MariaDB 11.4, where the project_stage table was created successfully.

To identify the exact cause, please provide:

  • your Joomla version,
  • your PHP version,
  • the database server and its exact version (MySQL or MariaDB),
  • whether this was a completely new installation or another attempt after an earlier installation failure,
  • any SQL error displayed before the error involving the project_stage table.

The problem may be related to a different database version or to tables left behind after an earlier failed installation attempt. Once I have this information, I will test the installation in the same environment and address the specific cause.

4

Uninstall and I remove all table and new install.
Ok. Now i see. Not all table is delete.
#1451 - Cannot delete or update a parent row: a foreign key constraint fails
mqqnk_joomleague_club
mqqnk_joomleague_league
mqqnk_joomleague_playground
mqqnk_joomleague_project
mqqnk_joomleague_season
mqqnk_joomleague_sports_type

5

After this delete table (disable check key)
the installation was complete

6

Hello,

Thank you for the additional information. The cause is now confirmed. The first failed installation left part of the database schema behind. JoomLeague currently preserves database data intentionally during uninstallation, so these tables were not removed automatically. The following installation then failed because of the incomplete schema and its foreign key relationships.

JoomLeague 6.2.0-dev8 will include detection of remnants from a failed installation, a clearer error message, and a safe tool for removing an incomplete schema. Data preservation during a normal uninstallation will remain in place to prevent accidental loss of competitions and other data.

Thank you for testing and for identifying the exact cause.