DaDaBIK 8.1 Lerici is available

Posted by Eugenio on 5 Sep 2017

Hi everybody,
I am glad to announce that DaDaBIK 8.1 is available.

This release contains several bug fixes (thanks for all your feedback!) and some new features.

The most important new features are:

Adoption of the Chosen jQuery plugin
DaDaBIK now optionally provides, for select_single and select_multiple_menu fields, a modern search box that allows to easily find a list element when the number of elements is huge. Furthermore, for select_multiple_menu, a new and more user friendly approach is used to display the selected values.
You can see this new feature in action from the on-line demo, Demo 1. Edit a product in the "products" table and see the "brand" and the "categories" fields.

Before delete hoooks
"Before delete" hooks are now supported.

Exclusion of some tables during installation
It is now possible to exclude from the installation some tables using the $tables_to_exclude and $prefixes_to_exclude parameters in config.php. The $prefixes_to_exclude parameter, in particular, is very useful to easily install and use two or more different DaDaBIK applications using a shared database (e.g. a read-only application that doesn't require authentication + a full-featured app accessible only by admin). The documentation has a new paragraph explaining in details how to share the same database between two or more DaDaBIK applications.

Permissions for autoincrement fields
It is now possible, setting the new $grant_permissions_autoincrement_after_table_installation parameter to 0 in config.php, to hide by default autoincrement fields from all the forms during a table installation or during the application installation.

The list of fixed bugs is long and includes, among the others:

• the fix for a bug that could produce wrong search results where select_multiple_* fields were used
• the fix to a bug related to db synchro: after an "add fields" operation, DaDaBIK lost some of the form configurator settings
• the fix for a bug related to pagination: pagination links didn't work correctly when the results grid was part of a master-details view.