What's new in EzyPlatform 1.3.8?

This release migrates the platform to MariaDB Connector/J, improves backward compatibility for existing MySQL configurations, enhances the Admin Guides experience, and increases the stability of the Admin interface.
  1. Migrated to MariaDB Connector/J
    EzyPlatform now uses MariaDB Connector/J 3.5.10 as the default JDBC driver, replacing the previous MySQL Connector/J dependency. The platform also adopts jdbc:mariadb: as the default JDBC URL format for new installations.
  2. Updated default database configuration
    The default setup.properties file has been updated to use the MariaDB driver and connection URL:
    datasource.jdbc_url=jdbc:mariadb://localhost:3306/ezyplatform
    datasource.driver_class_name=org.mariadb.jdbc.Driver
  3. Improved backward compatibility for MySQL configurations
    Added a compatibility implementation for com.mysql.cj.jdbc.Driver, allowing existing configurations that still reference the MySQL driver class to continue working. The compatibility layer automatically converts jdbc:mysql: URLs to jdbc:mariadb: and supports extracting user and password from legacy JDBC URLs.
  4. Added JDBC service loader support
    Added a JDBC service loader for the compatibility driver, allowing it to be automatically discovered through java.sql.Driver without requiring additional configuration.
  5. Added third-party notices
    Added third-party notices for bundled libraries, including MariaDB Connector/J and several commonly used frontend and Admin libraries, providing clearer licensing and dependency information.
  6. Improved Admin Guides
    The Admin Guides page now sends the i18n_lang parameter based on the current interface language when requesting guide content from the Market. Market guide URLs have also been enhanced to support language-specific content.
  7. Improved Admin UI stability
    The Admin layout has been made more resilient when admin or adminRoles data is unavailable, preventing template rendering issues in the sidebar, menu items, and media modal. Permission checks in the media modal, media details, and replacement history have also been improved to avoid errors when role information has not yet been loaded.
  8. Minor Admin UI refinements
    Applied minor CSS improvements to the Admin interface, including ensuring stylesheet files end with a proper newline for better consistency and compatibility.