Release v1.3.7

Version 1.3.7 is a maintenance release and contains two fixes and additional translations for the frontend.

• Fixed a bug with the IP localization caching. mosparo did not use the cache at all due to a faulty SQL query.
• Fixed a bad migration from v1.3.0. The MySQL migration to add the required tables for the project groups was not correctly creating the table in some cases, and the installation ended in an exception. The exception was ignored, and nobody noticed it. The adjusted migration will resolve these issues and correctly reinitialize the table.
• Added and updated the frontend translations for multiple languages. Thank you to all the translators for their contributions!

Release v1.3.6

This version contains an additional callback for the frontend JavaScript and translation updates.

• Added a callback onGetFormData to the frontend JavaScript to allow filtering of the form data before validation.
• Updated the translations for Hindi and Swedish.

Release v1.3.5

With this version, we’re fixing an issue in the Health check API and updating some translations.

• Fixed the issue when the installation is not completed but the health check API is executed already (for example, by Docker). Reported by Benjaminpr in #326
• Updated the frontend translations for Japanese, Polish, and Vietnamese and the backend translations for Vietnamese.

Release v1.3.4

This new release contains a new environment variable and some translation updates.

• A new environment variable was added to define the path where the shared file cache should be stored. This is useful when using the filesystem cache in multi-node setups.
• Updated the frontend translations for Finnish and added some updates for the German backend translations.

Release v1.3.3

This version contains multiple fixes for the health check. The health check was added to verify the mosparo installation’s health automatically.

• The health check returned an error if an update was not finalized (Database migration was not executed). Now, the health API will return a success message in this case.
• Added an environment variable to bypass the health check if needed.
• Added a command to execute the health check via the CLI.
• Fixed the health check for the cron- and PHP-only Docker containers. Before, the health check would never report healthy containers.

All these issues were found because of the report and support by mad73923 in #302.