DaDaBIK 5.0

v4.6 [11-06-12]

Fixed bugs and other changes The documentation section about multiple instances of DaDaBIK has been (at least for the moment) removed. That section was not up-to-date and referred to a version of DaDaBIK which still didn't have the authentication feature: the result is that if users followed those instructions having authentication ON, a user authenticated on the first (not admin) instance could also access the /admin instance without authentication. This is not a proper bug but could lead to a false sense of security. Most of the language translations got corrupted after the 4.6 beta utf-8 move. Fixed. DaDaBIK could silently truncate some of the parameters values in interface configurator if the lenght of the parameter value length was greater than a threshold which depended on the parameter itself. Fixed. The null checkbox didn't work as expected (enabling/disabling input fields) because of a javascript error. Fixed. Prefix and defaut values didn't work correclty if they contained a double quote character. Fixed. The amount of time before a record is automatically unlocked is now 4 minutes (it was 2). Authentication is now enabled by default. The Russian language was not specified in the languages list to choose from (config.php). Fixed. A re-installation of DaDaBIK on the same database didn't clean-up the table containing the information about the installation itself. Fixed. This bug shouldn't have had any effect on the user side, though. The importance of the parameter $site_path for security reasons has been highlighted in config.php. The authentication section of the Documentation was not clear. Improved. Due to SQLite limitations, the script for upgrading DaDaBIK to a new release is not anymore available for SQLite. The following fix was implemented in 4.6 beta but the quotes in the sentences appeared corrupted in the change log, so re-post: Table or field names having the string "from" in the name could lead to query execution error with SQLite. Fixed. The following fix was implemented in 4.6 beta but didn't appear in the change log, so re-post: The installation of views diddn't work with MySQL and PostgreSQL. Fixed.

v4.5 [09-20-12]

Fixed bugs

In some cases you could get a "Specified key was too long; max key length is 1000 bytes" or similar error during installation. Fixed. Thanks to Alonzo for having reported it. Furthermore, in some cases (probably quite uncommon), where a table name or its unique field name or a unique field record value are longer than expected, the record locking feature could work not correctly. Now DaDaBIK produces an error if the lenght is not supported. Using the rich_editor field type led to incorrect search results because the HTML editor add fomatting tags by default to the search text. Now a normal textearea is used for search forms to avoid this behavior. Thanks to user Funbird for the report. Please note that, still, the formatting tags inserted in a field through the HTML editor are not filtered so if you search "hey good" and you have "hey good morning" in your DB, of course you won't find it. This has been added to the "unexpected behaviors" section of the documentation. The "refresh installation" operation lost settings about master/details views: table and linked items. Fixed. DaDaBIK had a typo in the German translation. Fixed. (Thanks Heinz for the report) A bug about the default date 1968-01-01 was listed in the "Known bugs" documentation section even if it was already solved. Fixed. Choosing Estonian as language led to a parse error message. Fixed. Other changes During installation, a warning message is now displayed about the risks of enabling the CSV export feature in a public site. A note in the documentation has also been added. Thanks to user dh for having reported it. A minor bug about record editing when an identifier field value is changed has been added to the known bugs section of the documentation.

v4.3 [03-13-12]