DaDaBIK Change Log

Please note that in the "Fixed bugs" sections, the bugs are not just related to the previous version, most of the time they also affect other old releases. Please also note that some new features or changes could be related just to DaDaBIK PRO OR ENTERPRISE version.

Dec 19, 2017
v. 8.2 Lerici

• Ajax autocomplete for dropdown lookup menu: DaDaBIK can now load on demand (AJAX) the options related to a dropdown lookup menu (select_single or select_multiple_menu) while the user is typing on the menu form element. This is extremely useful to avoid delay in form creation when the number of options is very huge: the menu are in fact created without loading any options, the options are loaded only when the user starts typing. This feature has been implemented using the Select2 jQuery plugin (https://select2.github.io/), which replaces the Chosen jQuery plugin we used in the past.
• It is now possible to define through config.php the default function to execute for menu items related to pages based on tables/views; for example you can set, for the table 'customers', to show the insert form instead of the results grid.
• For PostgreSQL, DaDaBIK can now be installed choosing a specific schema (before, it worked only in the 'public' schema). Please note that creating a DaDaBIK application having tables/views coming from different schemas is still not possible.
• Chinese language is now available.
• The table dadabik_users was not ready to be extended so when, from DB synchro, new fields were added, the synchronization didn't work and the form configuration settings of the table were lost. Fixed. Now the schema of the dadabik_users table can be extended as any other table but this works only for fresh DaDaBIK installation, for DaDaBIK installations made with DaDaBIK v. <= 8.1 and then upgraded it doesn't work.
• The back and prev next buttons are not displayed anymore when printing a record details page.

• The parameter 'User-friendly searchable' impacted only on the search form, not on quick filters. Fixed.
• Table names used in master/details form were not correctly quoted so DaDaBIK produced SQL errors if they contained special characters (e.g. my-table). Fixed
• The 'copy settings' feature in form configurator didn't copy the value of the 'user-friendly searchable' parameter. Fixed.
• DaDaBIK didn't apply custom validation functions to date and date_time field types. Fixed.
• A new config parameter, $results_display_mode_menu, allows to chose if the results display mode menu (classic_grid, list) needs to be displayed or not and if not which is the default results grid display mode.
• A new config parameter, $default_order_type, allows to choose the default sorting type (ascending or descending) for the results grid.
• For several languages, the sentences 'Page x of n' was not correctly translated anymore. Fixed.
• The in-line help in form configurator let the developer assume that custom validation functions were applied to all field types except from select_single and select_multiple. It has been highlighted that they are actually applied only to text, textarea, rich_editor, date and date_time field types.
• Documentation: in form configurator, min width parameter, on-line help, it has been highlighted that also affects the way text is arranged in the results grid.
• Documentation: it has been highlighted that DaDaBIK automatically assignes a unique file name to the file the user uploads.
• When you installed a table/view from the pages section, DaDaBK produced an error if the list of installed tables/views was empty. Fixed.
• DaDaBIK + MySQL produced a 'Specified key was too long' error message if used with some multibyte charsets other than utf-8. Fixed. Please note, however, that the use of utf-8 is still STRONGLY recommended for MySQL and PostgreSQL and it is compulsory for SQLite. (This bug was suppoesed to be fixed with DaDaBIK 8.1 but it was fixed only for applications upgraded to 8.1, not for fresh installations).
• The form settings copy function didn't copy the value for the parameter 'Min width (in px) of the results grid column'. Fixed.
• DaDaBIK produced a Notice: Undefined variable: linked_table_installed warning in the results grid page when a select_multiple field had a NULL value. Fixed.

Sep 5, 2017
v. 8.1 Lerici

• Chosen jQuery plugin
  DaDaBIK now optionally provides, for select_single and select_multiple_menu fields, a 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. These new features are implemented using the Chosen jQuery plugin (https://harvesthq.github.io/chosen/) and can be enabled for each field in form configurator (parameter 'User-friendly searchable').
• Before delete hooks
  "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: for each application you need a different $prefix_internal_table and you need to set, for $prefixes_to_exclude, all the prefixes used by the other applications. A typical example is the creation of a view-only app that doesn't require authentication e.g. mysite.com/public and another - full-featured - app accessible only by admin, e.g. mysite.com/admin, sharing the same database.
• 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. This is often useful because normally you don't want to see 'ID' fields in your forms, especially in the insert forms (you want the value to be automatically generated and assigned). Of course you can alwasy remove the permissions (and hide a field from a form) later. This parameter currently works only with MySQL.
• The documentation has a new paragraph explaining how to share the same database between two or more DaDaBIK applications.
• In addition to "contains", a new search operator, "doesn't contain" is available.
• Norwegian language is now available.
• A new config.php parameter, $open_url_field_type_new_window, allows to open URL field type links in a new page (target _blank).
• For lookup fields, the link to the related record now opens the details page instead of the edit page. A new config.php parameter ($function_link_to_record) allows to choose between edit and details.
• A new config.php parameter, $open_blank_generic_file, allows to choose how to open a generic_file/image_file link (_self or _blank).
• It is now possible to specify in config.php a custom function (parameter $function_user_values ) that DaDaBIK applies before INSERT and UPDATE to all the values inserted by users through textboxes.
• In-line help in form configurator related to search operators and select_multiple_* field types provides now a clearer explanation.
• During the installation producere, when PostgreSQL is used, a message now reminds that by default queries are case sensitive.
• Added some instructions to the DB Synchro page.

• During a search, a select_multiple_menu/select_multiple_checkbox field was always connected to the next search parameter using the AND boolean operator, regardless of the operator chosen for the search (any condition Vs. all condition). This, therefore, could produce wrong search results if a search form or a quick filter contained a select_multiple_menu or select_multiple_checkbox field. Fixed.
• After a db syncro -> add fields, DaDaBIK lost the settings related to the related table for the following properties: Calculated field function / Show link to record? / Min width (in px) of the results grid column. Fixed.
• Graph report generation didn't work properly and produced an error if the field chosen for the X-axis was a lookup field and its name was different from the dadabik 'Lookup table primary key field'. Fixed.
• Calculated fields were disabled in search forms. Fixed.
• DaDaBIK + MySQL produced a 'Specified key was too long' error message if used with some multibyte charsets other than utf-8. Fixed. Please note, however, that the use of utf-8 is still STRONGLY recommended for MySQL and PostgreSQL and it is compulsory for SQLite.
• The example of hook function in custom_functions.php was wrong, there was a missing code line. Fixed.
• Pagination links didn't work correctly when the results grid was part of a master-details view, only page 1 was displayed correctly. Fixed.
• After installation, pages -> menu order was numbered starting from 3 instead of 1. Fixed.
• DaDaBIK image_file and generic_file field types didn't work correctly if the related table didn't have read permissions and was part of a master/details view as the item table.
• The check_sessions script produced an error messages. Fixed.
• [fix] DaDaBIK produced an 'undefined index' notice when an insert or update was executed in a form containing a calculated field. Fixed.
• The 'Copy settings' function in form configurator showed a button 'Copy permissions' instead of 'Copy settings'. Fixed.
• The installation code was not showed in the about page if PHP short tags weren't enabled. Fixed.
• Under particular circumstances DaDaBIK produced a 'PHP Notice: Undefined variable: site_url' message. Fixed.
• DaDaBIK during edit and insert operations produced, under certain circumstances, a 'PHP Notice: Undefined index' message. Fixed.
• Permissions copy on Postgres produced a 'Indeterminate datatype: 7 ERROR'. Fixed.
• DaDaBIK on PostgreSQL produced a 'ERROR: bind message supplies 1 parameters...' when the copy permissions feature was used without specifying a table. Fixed.
• Even when authentication was disabled, on small screens DaDaBIK showed the 'logout' and 'your account' buttons. Fixed
• In some PHP environments, the online registration of a DaDaBIK installation didn't work. Fixed.
• Under certain circumstances, DaDaBIK produced a '[08] Error: during last ID fetching. ' error with PostgreSQL during insert. Fixed.
• With DaDaBIK PRO edition, custom pages having type internal or external link didn't work. Fixed.
• DaDaBIK produced a deprecated warning if used with PHP7. Fixed. The issue was related to phpass 0.3, now upgraded to the last 0.5 (see the phpass release notes to get details about other issuses fixed from 0.3 to 0.4)
• An insert_date_time or update_date_time field could produce a required error even if the field was not displayed in the form and automatically filled by DaDaBIK. Fixed.
• DaDaBIK, if used with PostgreSQL, produced a 'Unique violation: 7 ERROR: duplicate key value violates unique constraint' error when an admin added a user, a group or a custom page. Fixed.
• Fields having a custom formatting function set and NULL value were displayd as blank instead of NULL and therefore the option didn't apply. The same for select_multiple fields having a NULL value. Fixed
• The in-line help in form configurator related to field types now highlights that, for the unique_id field type, the corresponding database field type must be varchar(50). A length less than 50, depending on the server settings, can lead to problems such as silently truncate the string produced for the unique_id field before storing the string itself in the database.
• Form configurator, in-line help: it has been highlighted that you cannot specify as linked field a select_multiple field or a field that has, in turn, linked fields associated. This limitation was not clear in the documentation.
• SQL logging: the config.php documentation now clarifies that the operations executed through hooks or other custom functions are not logged.
• Documentation: it has been highlighted that, when you save a report link for future use, if the report has been generated after a search, the search filter is not saved together with the link.
• In the in-line help, form configurator, it has been highlighted that, for select_multiple lookup fields, the lookup table primary key field values cannot contain the character set as FORM_CONFIGURATOR_SEPARATOR.
• In the configuration file, it has been highlighted that the lenght of the parameter FORM_CONFIGURATOR_SEPARATOR must be 1.
• Form configurator, in-line help: it has been highlighted that the cascade feature only works in EDIT and INSERT forms, not in search forms.
• A known bug has been added to the documentation: if an image_file or generic_file field is used as a linked field for a lookup field, the file is not showed if the user doesn't have read permissions on the corresponding linked table.
• The update_date_time fields are now automatically excluded from insert forms. Despite the in-line help said they were excluded, DaDaBIK showed them unless explicitly hidden.

Apr 24, 2017
v. 8.0 Lerici

• New, responsive, front-end
  DaDaBIK has a completely new, responsive, front-end. The front-end provides four graphic themes, three different modalities to handle the results grid layout overflow and two options for the menu: the classic dropdown list and a left side menu. You can choose a value for all these parameters in config.php.
  DaDaBIK also provides two display modes for the results grid: 'classi grid' and 'list', the latter displays each field+value couple in a single row and it is useful when you have a lot of columns (to avoid the horizontal scrollbar) or when you are accessing DaDaBIK from mobile.
• A complete graph reporting tool
  DaDaBIK now provides a complete graph reporting tool, which allows to easily produce Pie charts, Bar charts and line charts based on the application data. Both a simple mode (create a graph in two clicks) and an advanced mode (write your custom SQL query as source of the graph) are provided.
• Calculated fields
  DaDaBIK now provides calculated form fields, whose value is not directly provided by the user but calculated according to a custom PHP function. For example you might have a total_price field, which is calculated according to the values of other fields, e.g. as price + tax.
• Smart installation / configuration guessing
  A new smart installation procedure allows to save a lot of time during the DaDaBIK application configuration: DaDaBIK tries to guess the correct parameters for a field according to database field type, database constraints and even field name. For example if you have a referential integrity constraint in your schema, DaDaBIK chooses a select_single field type for the foreign key and set the correct linked fields; if you have a NOT NULL field, DaDaBIK sets the field as required, if your field contains the word "email", DaDaBIK set the field content to "email". All the rules are expressed in a PHP function guess_field_dadabik_settings() that the users can customize.
• Hooks
  DaDaBIK now provides HOOKS: a feature that allows you to write some PHP code to be called under certain circumstances. DaDaBIK currently supports after insert, before update, after update and after delete hooks. For example you can easily add some code that, when a new order is register to the system (after insert hook on table orders) automatically updates your stock in a table warehouse. Hooks are defined in the file custom_functions.php.
• Improved admin section
  The admin section has been drastically improved, in particular:
  • The tables inclusion page (now called 'pages') has been completeley redeisigned, and allows now to handle all the settings related to DaDaBIK pages: pages based on Tables, on Views or Custom pages. It is also possible to create database VIEWS directly from this page.
  • The usability of the form configurator has been improved a lot, for example when you set a lookup table, primary key, linked fields and other fields are now chosen from a list, without the need of typing field names manually. Furthermore, it is now possible to copy form settings from one table to another in one click, if the tables have exactly the same fields.
  • Permissions manager: it is now possible to set the permissions to Yes/No for all field/permission type combinations in one click.
  • Permissions manager: the copy permissions feature now allows to copy the permissions from one group to another choosing a specific table.
  • Permissions manager: once a table is selected, the current permissions are now showed without clicking on the submit button.
  • When, from the front-end, you open the admin area, the working table is now the one you were using in the front-end. This helps during the development process, when you often go back and forth between front-end and admin. Furthermore, DaDaBIK now remembers the last page you were working on in the admin area, and takes you back there when you access the admin area again.
• Users can now change their own password. You can disable this feature from config.php.
• It is now possible to specify in the form configurator, for each field, the min width (in px) of the corresponding column in the results grid.
• A draft of the update_records API method is now available in the new api.php file. The idea is to improve in future the API provided, in order to let other applications talk with DaDaBIK.
• Each custom page can now be enabled/disabled; this is useful when you create a new custom page and you don't want to show it before finishing the setup or when you temporary want to hide a custom page.
• A new custom page type, LINK, allows you to add a custom link (internal to the application or external) to the menu. This is particularly useful when you create a graph report and you want to easy access it later from the menu, in one click.
• DaDaBIK now accepts default values also for select_single / select_single_radio field types
• For select_single lookup fields, DaDaBIK allows now to show a link, in results grid and details page, that opens a page containing all the data of the linked record.
• A new config parameter: grant_permissions_after_table_installation allows you to automatically grant all permissions to all groups (or only to the admin group) when you install a table in DaDaBIK.
• It is now possible to set in config.php, for results grid and details page, the max width and/or max height in px the browser must use when displaying uploaded pictures.
• DaDaBIK now check and provide alerts for table and field names containing blank spaces or dots during installation and other operations.
• DaDaBIK now supports VIEWS also for SQLite
• DaDaBIK has a brand new installation page.
• It is now posssible to override language translations specifying them in a separate file. This is useful to avoid loosing your custom translations during the upgrade of DaDaBIK. It is also possible to differentiate your custom translations according to the table the user is using.
• Telugu translation is now available.
• New and more user friendly dialog boxes for the in-line help of the admin area, based on jQuery dialog
• It is now possible to hide the logout link, useful if DaDaBIK is embedded in Wordpress and the Wordpress authentication is enabled.
• When you access the edit form or the details page of a record that doesn't exist, DaDaBIK now redirects to the results grid page
• insert_date_time and update_date_time fields are not showed anymore in, respectively, insert and update form, regardless of the user's settings
• insert_date and update_date field types are now called insert_date_time and update_date_time, since they actually store date and time if the corresponding DB field is datetime
• It is now possible to choose a custom separator to display linked field values. The separator can be customized using $separator_display_linked_field in config.php
• Improved sicurity for PHP custom pages, now it is not possible to execute a file if the file is outside the directory custom_php_files
• The use of an external users table is now better explained in config.php
• The CSS file specific for print (styles_print.css) is not token into consideration anymore

• Escape/Unescape of values coming from POST GET COOKIES were not handled correctly for PostgreSQL and SQLite when custom pages or cascade fields were used, this could caused unexpected behaviour. Fixed.
• Unless the developer wrote some code to check the user authentication, custom PHP pages can be called and executed directly (calling the URL), bypassing the DaDaBIK authentication system. A proper line of code is now provided in /include/custom_php_files/example.php, this line must be added to the top of any PHP custom page created and prevents the page from being called directly.
• A table name containing characters which needed to be url-encoded to be passed via querystring (i.e. all non-alphanumeric characters except -_.) could lead to unexpected results if the table was a master in a master-details view and the user clicked on the sort-by links of one of the items tables. Fixed. Remember that table and field names still have restrictions (see the documentation, known bugs).
• Emails (insert notices/update notices) sent by DaDaBIK were text emails having HTML formatting, this produced weird content. Fixed, emails now contain just text, as exported CSV files.
• Successful logins to the application were always logged into the logs table, regardless of the setting in DaDaBIK Enterprise. The setting parameter was available in DaDaBIK Pro's config.php, even if the feature was not available. Fixed.
• The email field content now accepts also long Top-Level domains such as .media or .photography
• DaDaBIK didn't show an insert_date field in a edit form, even if the field was set to be displayed. Fixed.
• DaDaBIK, when a CSV was produced, added a carriage return at the end of each cell value if the corresponding field had a custom CSV formatting function . Fixed.
• Czech language was available but didn't appear in the languages menu. Fixed.
• Russian language is now complete.
• The upgrade script didn't allow to upgrade from Pro to Enterprise if the DaDaBIK version was the current one. Fixed.
• Due to a iOS Safari bug, users could not properly select options from a select multiple field. Fixed.
• The size of the password crypter popup was too small for certain browsers (e.g. Safari). Fixed.
• The Danish translation is now complete.
• The documentation provided in /include/custom_php_files/example.php contained two mistakes: it said to use the prefix _cs_ (the right one was actually _cp_) and that the database field names can't start with _cp_test (the right one was actually _cp_). Fixed.
• DaDaBIK could produce a 'Fatal error: Uncaught Error: Call to undefined function ereg()' error wihen used together with PHP 7.x. Fixed.
• DaDaBIK now accepts, for phone numbers, also numbers without the + sign at the beginning and numbers containing spaces or hyphens.
• DaDaBIK showed a blank choice for date fields search operator menus, removed.
• During a record update, checking the 'delete' checkbox doesn't actually phisically delete the file from the filesystem. Fixed.

July 26th, 2016
v. 7.3.3

• The vulnerability fixed with DaDaBIK 7.3 was even worst than we described: an authenticated user (or a user of a DaDaBIK application having authentication disabled) could execute arbitrary SQL queries (even INSERT/DELETE/UPDATE) on the DaDaBIK database (or on other databases if the database user used by DaDaBIK had the needed permissions). This vulnerability WAS actually fixed with DaDaBIK 7.3. Another similar vulnerability, however, was found in the last days; this one fixed by the 7.3.3 version; again, the vulnerability allowed an attacker to execute arbitrary queries on the DaDaBIK database or on other databases (if the database user used by DaDaBIK had the needed permissions). In this case, if authentication was enabled, not only the attacker needed to be authenticated to exploit the vulnerability, but also he/she needed to belong to the administrators group.

July 6th, 2016
v. 7.3.2

• Export to CSV, performances improved: the performance gain depends on the number of columns; for a typical table, the CSV build process can be 7x faster than before.
• The crypter link showed warnings messages and was not usable. Fixed.
• Microsoft Excel was unable to correctly represent utf8 characters if used to open CSV files created by DaDaBIK. Fixed. You can still have problems with old MS Excel versions on Mac OS. In config.php it has been highlighted that the csv_separator parameter needs to be set to ; if you want to directly open the files with MS Excel.
• For content edited using old Mac computers (when \r alone was used as line break character), the export to CSV feature removed the line breaks included in a field value. Fixed.
• If a date/date_time field contained a NULL value, DaDaBIK produced a PHP error message after an Export to CSV process and the field was not correctly represented in the CSV file. Fixed.
• If a custom CSV formatting function was used for a field, DaDaBIK didn't correctly separate the field from the next one; the result was a broken CSV file. Fixed.
• During the installation, DaDaBIK didn't accept 'postgresql' as dbms_type, even if it is a correct parameter value. Fixed.

June 7th, 2016
v. 7.3.1

• Table install/uninstall in Admin->Table inclusion didn't work in DaDaBIK 7.3. Fixed.
• DaDaBIK 7.3 produced a "Warning: date(): It is not safe to rely on the system's timezone settings." message. Fixed.
• Known bugs in documentation fixed: not only field names but also table names cannot contain blank spaces or dot; not only Insert/search/update operations fail but also other operations.

May 24th, 2016
v. 7.3

• DaDaBIK suffered from an SQL injection vulnerability which allowed an attacker to see unauthorized data:
  
  1) data coming from tables the user hadn't the read permissions for
  2) data coming from disabled (not enabled in DaDaBIK) or not installed tables
  3) data coming from records the user didn't own (enabled table having read permissions set to MY for the user)
  
  For 1) and 2) the tables could also be in another Database respect to the one where DaDaBIK was installed.
  
  The vulnerability has been fixed.
  
  1) and 2) should occurs only in a particular situation: when your DaDaBIK installation has at least a table exposing just ONE field to the attacker in the results grid; however at the moment we can't guarantee it so you are STRONGLY encouraged to upgrade in any case. 3) instead can always occur.
  
  It's important to highlight that the attacker, to exploit the vulnerability, needs to be authenticated in your DaDaBIK application (or access a DaDaBIK application having authentication disabled).
  
  It has also been highlighted that, to prevent SQL injection vulnerabilities (even after this fix) you have to follow these rules:
  - for PostgreSQL, standard_conforming_strings must be ON (if you have a recent PostgreSQL, it should be ON by default)
  - for SQLite, the database must be in UTF8. UTF8 is the character set strongly recommended also for MySQL and PostgreSQL.
  
  If you used to create links to pre-filtered grid views using custom URLs, please note that this approach won't work anymore after the application of this fix. You can use VIEWS instead.
  
  The fix for this vulnerability is also available as a separate patch here: http://dadabik.org/patch_sql_2016.txt
  
  
• In some cases, the previous/next buttons did not bring the user to the correct record, considering the order the records had in the results view. Fixed.
• If $use_id_group_for_ownership was set to 1, the count of the total number of records in a table was not correct. Fixed.
• In some cases, DaDaBIK produced a "Notice: Undefined index" message during update if a file field wad required.
• The French language is now complete and some typos have been fixed.
• DaDaBIK produced a "Notice: Undefined variable" message in results grid if a table hadn't a primary key set. Fixed
• Sometimes the DaDaBIK execution was blocked by the ModSecurity Web application firewall because of the word "table_name" in URLs, producing a "Forbidden" error message. Fixed.
• The check about the max length of a field value didn't work correctly for select_multiple_* fields if the user inserted value containing a character which needed to be quoted (e.g. '). Fixed.
• Text flow in textbox/textarea was not handled correctly by Internet Explorer 10. Fixed.

• The installation process has been improved, providing specific and meaningful error messages if any configuration parameter is missing or wrong. Furthermore, $site_url and $site_path are not required anymore.
• When the user tries to access an admin page but the login screen appears because the session is expired, after a successful login DaDaBIK redirect the user to the section she was trying to access and not to a default page.
• It is now possible to specify the years range to use in the datepicker
• The final user can now change the language on the fly, while using the application.
• It is now possible to upgrade from DaDaBIK Pro to DaDaBIK ENTERPRISE just by running the upgrade script, even if the version number is different.

March 16th, 2016
v. 7.2

December 14th, 2015
v. 7.1

October 5th, 2015
v. 7.0

• Engine optimization
  The display of results grids is now much faster if you have several select_single or select_multiple fields in your grid, especially if granular permissions are enabled and if your database is big in terms of number of tables and number of fields. Example: for a DaDaBIK application having 18 tables installed, the display of the results grid is about 43% faster than before for a table having four select_single fields in the grid.
• Cascade dropdown fields
  It is now possible to populate a dropdown menu (select_single) according to what the user selected from another dropdown menu. For example you can have two menu: country and city; when the user selects the country, the system automatically populates the content of the city dropdown with the list of the cities related to the country selected.
• Custom required functions
  Until now, you could only set a field as "required" or "not required"; it is now possible to specify, for each field, a custom PHP function to use in order to evaluate if the field is required or not; in particular, you can specify the requiredness of a field according to the value of other fields in the form. For example let's say you have a table customers and for each customer you have several fields, including country (a dropdown menu), address, city and state; you want to make the "state" field required only for customers from U.S.A.: using a custom required function you can very easily specify that "state" is required only if the value of country is = "U.S.A.":
  
  

  function dadabik_required_state_customer($parameters_ar)
  {
  	
  	if ($parameters_ar['country_customer'] === 'U.S.A.'){
  	
  		return true;
  	}
  	else{
  		return false;
  	}
  }
  

  The check is performed through an Ajax call so, in this case, you will see an asterisks near "state" as soon as you select "U.S.A" from the country dropdown menu.
• Permissions copy
  From the admin area is now possible to copy all the permissions from one group to another in one click (DaDaBIK Enterprise only).
• Others
  The time needed to save permissions in permissions manager is now much less than before.
  
  DaDaBIK now requires PHP >= 5.2
  
  

• select_multiple fields were not correctly handled
• formatting rules related to linked fields were not correctly handled
• if a field of the table had the "Primary key field" set in form configurator but it was not a select_single/select_multiple field, DaDaBIK could produce unexpected results.

Dec 22, 2014
v. 6.3

June 24, 2014
v. 6.2

June 2, 2014
v. 6.1

March 25, 2014
v. 6.0

July 23, 2013
v. 5.1.2

• Insert or Search in a form having a select_single field whose linked table had read permissions set to MY
• Edit of a record having a select_single field whose linked table had read permissions set to MY and having the selct_single field name different respect to the "Primary key field" parameter of the linked table

March 20, 2013
v. 5.1.1

January 23, 2013
v. 5.1

November 24, 2012
v. 5.0

November 3, 2012
v. 4.6

September 27, 2012
v. 4.6 beta

August 15, 2012
v. 4.5 patch level 1 (pl1)

June 25, 2012
v. 4.5

May 31, 2012
v. 4.5 beta

May 5, 2012
v. 4.4 patch level 1

April 3, 2012
v. 4.4

February 14, 2012
v. 4.4 beta

February 2, 2011
v. 4.4 alpha

December 8, 2010
v. 4.3 final

November 28, 2010
v. 4.3 beta RC2 (release candidate 2)

November 23, 2010
v. 4.3 beta RC1 (release candidate 1)

November 15, 2010
v. 4.3 beta3

November 11, 2010
v. 4.3 beta2

October 21, 2010
v. 4.3 beta

September 14, 2010
v. 4.3 alpha

February 18, 2007
v. 4.2

February 8, 2007
v. 4.2 beta

January 18, 2007
v. 4.1 final release

January 14, 2007
v. 4.1 release candidate 3

January 14, 2007
v. 4.1 release candidate 2

November 13, 2006
v. 4.1 release candidate 1

October 24, 2006
v. 4.1 beta

October 04, 2006
v. 4.0

January 24, 2006
v. 4.0 beta 2

January 24, 2006
v. 4.0 beta

June 20, 2005
v. 4.0 alpha

June 4, 2005
v. 3.2

March 31, 2005
v. 3.2 beta

• The class simpleLogin (http://www.phpclasses.org/browse/package/1492.html) is not used any more
• DaDaBIK stores now user information in the database and passwords are now md5 encrypted
• It is also possible to use a pre-existent users table
• You can use DaDaBIK itself in order to add and delete users, show and modify users information
• The admin pages (admin.php, install.php) are not login-protected any more, you have to provide your own protection
• A select_single field with linked fields now shows a listbox with all the corresponding linked table records, regardless of the ownership.

July 19, 2004
v. 3.1 beta

May 25, 2004
v. 3.0

March 10, 2004
v. 3.0 Beta

March 11, 2003
v. 2.2.1

Novermber 9, 2002
v. 2.2.1 beta

October 22, 2002
v. 2.2 beta

July 31, 2002
v. 2.1b beta

July 30, 2002
v. 2.1 beta

Jun 28, 2002
v. 2.0.1 beta

Jun 1, 2002
v. 2.0 beta

Apr 21, 2002
v. 1.9.1

Apr 15, 2002
v. 1.9

Mar 18, 2002
v. 1.8

Feb 28, 2002
v. 1.7

Feb 11, 2002
v. 1.6

Jan 27, 2002
v. 1.5b

Jan 26, 2002
v. 1.5

Jan 14, 2002
v. 1.1 beta

Dec 9, 2001
v. 1.0.5 beta

Dec 5, 2001
v. 1.0.4 beta

Dec 1, 2001
v. 1.0.3 beta

Nov 24, 2001
v. 1.0.2 beta

Nov 24, 2001
v. 1.0.1 beta

Nov 21, 2001
V. 1.0 beta