With this release, you can now use the encoding parameter for MySQL data sources to specify the character set and improve error handling and error messages.
We have also fixed a few bugs.
New functions and enhancements
ID 15068: Implement "Encoding" parameter for the connection in MySQL data source
You can now change the encoding of the MySQL data source using the encoding parameterin the Datasource > Mysql setting under encoding. You can now specify the corresponding character set under encoding, e.g. utf8 or another parameter supported by MySQL.
Under encoding in edoc automate, enter the character set (charset) that you have configured in the MySQL database.
If you do not specify an encoding, edoc automate uses the utf8mb4 encoding by default.
ID 15682: Catch PHP error "Throwable" when executing actions and display error
If errors occur when executing actions in edoc automate, e.g. incorrect types, syntax errors etc., the errors are now logged in the logger under the context key exception.
ID 15407: Display meaningful error messages for invalid action calls
If the instance of the action is not found when creating an action, e.g. because a plug-in has not been installed in the app, a meaningful error message is now displayed.
Bug fixes and improvements
High ID 15633: Components in tables may display incorrect value
If you try to access a component in a table that has not yet been rendered, a warning is displayed. All components show the correct value in the table.
High ID 15482: Translations in an app cannot be edited
If you use plug-ins in combination with Composer packages in an app, the queries are now executed correctly and without error messages.
High ID 15867: "FileUpload" does not work with file names containing special characters
The FileUpload component now supports files whose file names contain special characters such as Latin1 character set, Japanese characters, emojis, etc.
Normal ID 15877: Long loading and response times for views with many components
The loading and response times for views with many components have been optimized. This improvement reduces the processing time in edoc automate, but response times of external third-party systems (e.g. databases) still have an influence on the overall performance.