www.archive-org-2014.com » ORG » D » DADABIK

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".

    Archived pages: 608 . Archive date: 2014-01.

  • Title: PHP database front-end / CRUD generator for MySQL SQLite PostgreSQL - Create a PHP online database application / data entry application without coding - DaDaBIK is a DataBase Interfaces Creator
    Descriptive info: .. RSS.. Twitter.. Facebook.. Youtube.. Email.. Home.. Demo.. Buy/Download.. Pricing.. Wordpress plugin.. Support/Forum.. Docs/FAQs.. FAQs.. Manual.. Change log.. License.. Services.. Blog.. Turn your MySQL/pgSQL/SQLite DB in a Web app, now!.. - Last DaDaBIK is 5.. 1.. 2, released July 23, 2013.. What is DaDaBIK?.. Do you want to move your database to the Web without programming a dedicated application? You need a database CMS.. DaDaBIK is a very popular and mature software which makes the creation of PHP online database applications easy.. No coding is required; if you have a MySQL, PostgreSQL or SQLite DB you can create a basic CRUD (Create, Read, Update, Delete) database front-end in minutes or, through a visual interface configurator, a more sophisticated database application.. Features include: forms generation/customization, datagrid generation/customization, datagrid HTML template customization, 12 field types, Wordpress integration, file uploading, master/detail views, duplication checking, authentication, granular permissions, integration with external user/group/password lists, record locking, record ownership authorizations, CSV export, email alert, SQL logging, pre-defined/custom formatting rules, pre-defined/custom validation rules, front-end in 18 languages.. Watch the video to get more information or view the demo.. Start a demo Now.. Latest from the blog.. DaDaBIK 5.. 2 is out: Security and other bug fixes.. Dear all, a new release, DaDaBIK 5.. 2, is out.. It is the 57th version since I started to work at this software and probably the last 5.. x one.. 2 is mainly a maintenance release which f.. Security Alert, DaDaBIK 5.. 1 is out, please upgrade.. Dear DaDaBIK users, we have found a security hole and DaDaBIK 5.. 1 has been published to fix it.. If two DaDaBIK applications were installed under the same domain (e.. g.. http://mysite.. com/dadabik_o.. Another big step forward: DaDaBIK now provides Wordpress integration and LDAP authentication.. Hi everbody, we are glad to announce that dadabik 5.. 1 is out with Two big improvements: 1) Wordpress integration (PRO and ENTERPRISE versions): a DaDaBIK application can now be integrated into a W.. Our Users Say it Best.. Even if you can program in PHP with MySQL, DaDaBik saves an imense amount of time.. And for novices, it requires no knowledge of programming to implement a tight and efficient database front end.. David Serey.. So far, the most comprehensive, fast and easy to use solution for presenting your data online.. No special knowledge needed, no coding.. Fast and friendly support.. A verified customer's review on Hotscripts.. com.. An excellent solution for publishing data from a mySQL database.. No coding required.. Great forum and support (even for a minor error caused by an old php-version on my webserver, they found a workaround very fast).. I can't thank you enough to have put in so much hard work for this type of software.. It has really helped me out!.. James, Canada.. Firstly, thanks for a great product! This is exactly what I was looking for.. I use DaDaBIK as a web frontend to a MySQL database.. I set up the database for a political organization so that they would not have to use dozens of spreadsheets to keep track of the tens of thousands of contacts they have.. They really like the search  ...   from easily accessible and searchable data as enabled by Dadabik.. Mucheru, Kenia.. I’ve enjoyed working with your product on one of my projects.. The learning curve is not too great and I was getting the results I wanted very rapidly.. Larry K.. , California.. I run a fansite for a few online games, and we're developing tools to help users through their play.. We're running the tools off of an sqlite database and using DaDaBIK to allow our contributors to add and edit data about spells/stats/gear/etc.. I also hope to create a front-end install to allow visitors to search our data and generate CSV files for their own tools and spreadsheets.. Running our tools off of a single database is reducing the time required to update multiple applications as data gets added, and DaDaBIK is providing a simple user interface so that my partners can keep the data current without having to learn complicated software.. My PHP skills are not very strong, so it has saved me a lot of time in coding repetive CRUD forms, interfaces, and session/auth scripting, allowing me to focus my time on the more important task of creating new tools.. Nick Steimling, United States.. I am using hte DaDaBIK to enter data into a database used for my iPhone application.. I really love DaDaBIK it does almost all I want.. Michael Widegren, Sweden.. Developed by Professionals.. Eugenio Tacchini, Ph.. D.. , is an Italian software analyst & developer, University lecturer of Information Systems and researcher in Music Recommender Systems.. He has been a visiting scholar at the Freie Universitat Berlin and at the University of California, Berkeley.. Enjoying PHP and open source technologies, he created the very first version of DaDaBIK in 2000, twelve years ago, and he continues developing it to this day.. Mature, Growing and Open.. 51 versions released after the first 1.. 0 beta.. 160,000+ downloads.. A great community, 10,000+ forum posts.. Trusted by many organizations (profite, non-profit and governative) including the University of Cambridge and the University of Yale.. Source code available for further customization, if you need.. Great Customer Support.. Choose between a premium email support or the basic forum support, your questions will be answered, always.. Professional services for: installation, configuration and customization.. Need additional features? We can extend DaDaBIK to meet the needs of your organization and help you move your (legacy) data on a Web-environment.. DaDaBIK is always growing.. Don't find what you are looking for?.. Search this site using Google.. If you want to keep yourself updated about DaDaBIK, you can.. subscribe our newsletter.. , which informs about new releases and gives other announcements about DaDaBIK, just 10/20 messages/year.. Your data will be used and recorded in respect of DL 196/03 (Italian Privacy Law) and will not be sold to anyone; we hate spam as much as you do.. The holder of the data treatment is Eugenio Tacchini, you can contact him at the following address: eugenio dot tacchini at gmail dot com.. Subscribe our Newsletter.. Email Address:.. Connect with us.. Mail.. Copyright 2001-2013 Eugenio Tacchini.. All rights reserved.. DaDaBIK is a deposited trademark.. VAT Number IT01354810333.. Scroll to Top..

    Original link path: /
    Open archive

  • Title: PHP database front-end / CRUD generator for MySQL SQLite PostgreSQL - Create a PHP online database application / data entry application without coding - DaDaBIK is a DataBase Interfaces Creator
    Descriptive info: Contacts.. For technical support:.. If you purchased DaDaBIK Enterprise version, you can write an email to.. support at dadabik dot org.. ; otherwise (DaDaBIK Basic and Pro) you have to use the.. forum.. For pre-sale enquires and all other requests:.. You can send an email to.. info at dadabik dot org.. or use the form below.. *.. Your Name.. Company/Organization.. Your comments.. Form Verification.. (enter the verfication code in the field below)..

    Original link path: /index.php?function=show_contacts
    Open archive

  • Title: PHP database front-end / CRUD generator for MySQL SQLite PostgreSQL - Create a PHP online database application / data entry application without coding - DaDaBIK is a DataBase Interfaces Creator
    Descriptive info: Demo 1: Movies Library.. This is a simple movies library front-end developed with DaDaBIK.. without writing any PHP code.. From this demo you can see some of the DaDaBIK features, including:.. Data Grid HTML Template.. , which allows to deeply customize the.. show items.. page.. In this case, not only the layout of that page has been customized but, again using the template feature, each Amazon Product Code has been transformed in the corresponding Cover Link.. Duplication Checking.. , try to insert a new movie having "2011: A Space Odyssey" as a title (yes, 2011 not 2001).. Quick Search:.. e.. the Title, Director and Year search tools in the movies.. page.. Drop-down lists from table:.. enter a movie's record in edit mode and see the.. director.. drop-down menu.. We are going to create a DaDaBIK demo application on a shared DB for you.. You can use and customize it for one hour.. After one hour or if your session expires, you will be redirected here and your settings will be lost.. Start Movies Library demo Now.. (it can takes a while, just wait until the login screen appears).. Demo 2: Invoicing System.. This is a more complex example, a simplified invoicing system: you can manage customers, suppliers, products and invoices  ...   search tools in the products.. Custom Data Formatting rules:.. the Amazon Product Codes are transformed in Amazon Image Links through a user-defined function.. File Upload:.. enter a customer's record in edit morde,.. Pic.. field.. CSV Export:.. the link at the bottom of each.. This application has also been developed.. , except from the few lines needed to write the validation and the formatting custom functions for Amazon Product Codes.. You can use it and customize it for one hour.. Start Invoicing System demo Now.. Demo 3: Wordpress integration Demo.. The Movies Library demo (demo 1), is in this demo integrated in a Wordpress page.. In this example, authentication is disabled so you can't log-in as admin and modify the application (as you can in the first two demos).. Start Wordpress integration Demo Now.. (it can takes a while, just wait until the demo site appears).. Beginners tutorial.. Should you feel the need to get acquainted with how an application like the above ones are created with DaDaBIK, you can watch the YouTube tutorial first.. While it is based on version 4.. x (version 5 added lots of new features and a new interface), it still serves as a useful tool to understand the basics.. For best results, choose the maximum quality..

    Original link path: /index.php?function=show_company_demo
    Open archive

  • Title: Download DaDaBIK, PHP database front-end / CRUD application generator for MySQL SQLite PostgreSQL
    Descriptive info: Purchase and Download DaDaBIK.. DaDaBIK comes in three versions:.. Basic, Pro and Enterprise.. , each has an increasing number of features and services included (all details in the.. page).. Buy DaDaBIK 5.. 2 (rel.. on July 23, 2013).. BASIC Version €15 (or $20).. PRO Version €45 (or $59).. ENTERPRISE Version €140 (or $189).. Perpetual license.. You can read the full license at the Documentation - License page.. for both personal and business purposes included.. PHP source code included (you can customize it if you want).. Six months of free upgrades included (email payments at dadabik dot org to get your free upgrade).. If yo have..  ...   a database/web development (or related subjects) teacher and want to use DaDaBIK in your class? Apply for a free license writing to.. ; DaDaBIK has been already used in database classes in some colleges around the world.. CLICK BUY NOW TO PROCEED.. , you can start the download after completing the secure purchase with our partner.. Fastspring.. ; both.. Paypal.. and major.. credit cards.. are accepted.. A.. regular invoice.. is always provided after the payment.. You have to enable Javascript in order to proceed.. DaDaBIK is in use.. in many companies, organizations and universities all over the world.. Here are our top 10 customers (countries):..

    Original link path: /download
    Open archive

  • Title: PHP database front-end / CRUD generator for MySQL SQLite PostgreSQL - Create a PHP online database application / data entry application without coding - DaDaBIK is a DataBase Interfaces Creator
    Descriptive info: Pricing and Features.. Choose your Version.. GENERAL FEATURES.. Forms generation.. Automatic generation of customizable insert/edit/search/details forms.. Datagrid generation.. Automatic generation of a customizable datagrid which represents records.. CSV export.. E-mail alert.. A message can be automatically send to a custom address for each insert and/or update.. File upload.. Front-end in 17 languages.. Wordpress integration.. A DaDaBIK application can be integrated into a Wordpress site through a dedicated wrapper plug-in.. Users authenticated through Wordpress can also be automatically authenticated into DaDaBIK too, without doing the log-in again.. UTF-8 support.. Full, unencrypted source code.. Unlimited number of applications.. Buying one license, you can create as many DaDaBIK applications as you want, even for different customers.. SUPPORTED DBMS.. MySQL support.. PostgreSQL support.. SQLite support.. PERMISSIONS-RELATED.. Users and User Groups.. Authentication.. Secure password storage.. Users' passwords are encrypted; three password hashing methods (CRYPT_BLOWFISH, CRYPT_EXT_DES and an md5-based method) are available and the system chooses the best one according to what the current environment can provide.. All three employ salting, stretching, and variable iteration counts.. Granular permissions manager.. For each group you can choose a differnet permissions policy, both at table and field level.. For example you can decide that the group "Agents" can view the table "Customers" but can't delete or edit its records; futhermore, you can decide that the group "Agents" can see all the fields of the table while the group "Marketing" just a few.. Records Ownership.. The ownership of a record (the user who created a record is considered its owner) can be used as a parameter to authorize some operations: for example you can choose that a record can be deleted/modified only by the user who created it.. External users list integration.. DaDaBIK uses by default the table dadabik_users and dadabik_groups to store users information, but you can also use existing user and group tables, even if your users table doesn't use the same password encryption which DaDaBIK uses.. This help the integration of DaDaBIK with existing applications, for example with a CMS.. LDAP authentication.. Both Open LDAP and Microsoft Active Directory supported.. LDAP users are also imported in DaDaBIK to allow permissions setting.. DATA INTEGRITY/SECURITY.. Duplication checking.. During records insertion, DaDaBIK can be set for checking the similarity of one or more fields with existing records fields, to prevent record duplication.. The similarity threshold can  ...   design.. Form layout customization.. For each row, you can choose to represent two or more fields; furthermore you can add titled separator to group fields set.. Customizable search operators.. For each field it is possible to choose a list of search operators amgong a pre-defined set (e.. equals to, like, greater than, less than,.. ).. Form hints.. Form tooltips.. Master/details view.. Each form can be repsented together with one or more related datagrid, e.. an invoice form can have in the same page the datagrid which represents its items (1:N relationship).. DATA VALIDATION FEATURES.. Pre-defined data validation rules.. The validation rules for the following field types are available and built-in: Alphabetic, Alphanumeric, Numeric, URL, Email, Phone, Date, Date time.. Custom validation rules.. The possibility to specify for a field a custom data validation rule (rules can be specified in PHP).. Lenght validation.. Required fields.. AFTER-SALE SERVICES.. Support forum.. E-mail support.. 5 support tickets to use in one year; personal email messages answerd by DaDaBIK experts.. If the user doesn't receive an answer in 24 hours (Mon-Fri), he can cancel the email support and ask for a €50 refund.. Free upgrade.. If the new version number is the same as the one you purchased, you can get a free upgrade even after the free-upgrade period.. For example if you buy v.. 4.. 5 beta (DaDaBIK Basic), you can get v.. 5 final even if it has been published after three months; after three months, however, you can't get, version 4.. 6.. ADVANCED CUSTOMIZATIONS.. Data grid HTML templates.. While the pre-defined data grid layout is the classic tabular presentation, you can specify, through a custom HTML template, a completely different layout.. For example you can provide an HTML template to get the results of a search displayed in a Google-style manner.. OTHER CUSTOMIZATIONS.. Data grid elements hiding.. Quick search.. In addition to the default search form, some textboxes or dropdown menus can be displayed over the data grid for rapid search operations involving one or more fields.. Static pages.. You can add completely custom-content static pages to your DaDaBIK application, for example an help or introductory page.. Homepage customization.. You can customize the static-HTML homepage of the DaDaBIK application created.. Basic.. €15 ($20).. 2 months.. Buy.. Pro.. €45 ($59).. Holiday Offer!.. 6 months.. Enterprise.. €140 ($189).. 1 year..

    Original link path: /index.php?function=show_pricing
    Open archive

  • Title: DaDaBIK and Wordpress, use DaDaBIK as a CRUD plugin for Wordpress
    Descriptive info: DaDaBIK and Wordpress, use DaDaBIK as a CRUD plugin for Wordpress.. While DaDaBIK can be used to create stand-alone applications, versions PRO and ENTERPRISE provide a Wordpress plugin which allows to embed a DaDaBIK app into a Wordpress page using one code line.. You can have a simple searchable DB front-end or a more sophisticated DB app.. embedded in your Wordpress site.. , using wordpress login to automatically authenticate in DaDaBIK as well.. The following is a screenshot, go the.. demo page.. and choose demo n.. 3 to see a real Wordpress-DaDaBIK implementation..

    Original link path: /index.php?function=dadabik_crud_wordpress
    Open archive

  • Title: PHP database front-end / CRUD generator for MySQL SQLite PostgreSQL - Create a PHP online database application / data entry application without coding - DaDaBIK is a DataBase Interfaces Creator
    Descriptive info: Support & Forum.. If you need technical support and you purchased DaDaBIK Enterprise version, you can write an email to.. , you have 5 email support tickets to use in one year.. If you purchased DaDaBIK Basic/Pro or you have finished your support tickets, you have to use the.. instead.. The.. is anyway a great source of knowledge for all users, with 10,000+ posts published by the DaDaBIK community during the last years.. Beside the Support forum (both in English and Italian) there are a Feature requests forum and a General Discussion forum.. Access the DaDaBIK forum..

    Original link path: /index.php?function=show_support_forum
    Open archive

  • Title: PHP database front-end / CRUD generator for MySQL SQLite PostgreSQL - Create a PHP online database application / data entry application without coding - DaDaBIK is a DataBase Interfaces Creator
    Descriptive info: Documentation.. Please choose FAQs, Manual, Change log or license..

    Original link path: /index.php?function=show_documentation_menu
    Open archive

  • Title: PHP database front-end / CRUD generator for MySQL SQLite PostgreSQL - Create a PHP online database application / data entry application without coding - DaDaBIK is a DataBase Interfaces Creator
    Descriptive info: LICENSING AND GENERAL QUESTIONS.. Do I need to buy a license for each DaDaBIK application I produce?.. No, you buy ONE license and you can legally produce as many application as you want.. Do I have to pay again when a new upgrade comes out?.. No, you have a.. free upgrade.. period: 2, 6 or 12 months depending on the version you purchased (Basic, Pro, Enterprise).. What if there is a major upgrade, like from DaDaBIK 5.. x to DaDaBIK 6.. x?.. Still, if you are in your.. period, you'll get it for free, even if the price increases (as it can happen after a major upgrade).. Ok, I am in my.. period, how can I get my free upgrade?.. Just send an email to.. payments at dadabik dot org.. including if possible your order number and you'll receive your upgrade via email.. If you don't receive the file, it probably means that your spam filter have blocked it, write us again.. Can I change the DaDaBIK code to implement a new feature?.. Sure, source code is provided and you can change it.. Do you have a trial verion?.. No, we don't.. You can test almost all the features through the.. on-line demo.. The few features which are disabled in the on-line demo just  ...   send us your skype username.. Does DaDaBIK work on Windows/Mac/Unix/Linux/.. ?.. Yes, DaDaBIK works with any Operating System which supports PHP, the requirements (you can find them.. here.. ) are very low but if you still have doubts about your system send an email to.. TECHNICAL QUESTIONS.. I get [08] Error Message.. I get "Error during query execution".. Please open the file.. include/config.. php,.. look for the variable named.. $debug_mode.. Set it to 1, so that you'll be able to see what the error is.. If you still cannot figure it out request for support.. I can't see the edit/delete record icons in the results view.. You did not set a primary key in the table, so you are able to see the records but DaDaBIK cannot edit/delete them.. I get "your database is empty" error, why?.. You first have to set up a database and then you can install DaDaBIK.. Page not showing after Insert/Update.. Open.. php.. and make sure the variable $site_url is set to the the complete path to your DaDaBIK installation.. (E.. g.. http://www.. yoursite.. com/dadabik_folder/.. ).. I can't login into DaDaBIK.. Before asking for support double check that the parameters $site_url and $site_path in.. are correct.. 99% of the time login problems are due to mistakes in those parameters..

    Original link path: /index.php?function=show_faqs
    Open archive

  • Title: PHP database front-end / CRUD generator for MySQL SQLite PostgreSQL - Create a PHP online database application / data entry application without coding - DaDaBIK is a DataBase Interfaces Creator
    Descriptive info: This documentation is about the 5.. 2 release, if you need the documentation for a previous release please read the documentation file included in each downloaded package; the features described in this file refers to DaDaBIK Enterprise Version, some of these features might be not available for DaDaBIK Basic and Pro versions.. Check the.. features comparison.. for further details.. Table of contents.. What is DaDaBIK?.. Requirements.. Video tutorials.. Installation.. Upgrade from previous versions.. Upgrade from BASIC to PRO/ENTERPRISE or from PRO to ENTERPRISE.. Configuration.. DaDaBIK Wordpress Integration.. LDAP Authentication.. Wordpress Authentication.. Permissions.. Adding a new language translation and fix existing ones.. Export to CSV, risks.. Security.. Known bugs, limitations and unexpected behaviors.. DaDaBIK is a very popular and mature PHP application which allows you to easily create a highly customizable database front-end/application without coding.. You can use it to create in a few minutes a very basic CRUD (Create, Read, Update, Delete) database front-end or to develop a more sophisticated database application.. With DaDaBIK (differently from many similar softwares) you don't produce a PHP script, which would become outdated when you modify the schema of your database, but instead you directly use its abstraction layer that can be easily updated every time you modify your database's schema.. DaDaBIK uses the.. PDO.. extension in order to support as many DBMSs as possible, at the moment it officially suports MySQL, PostgreSQL and SQLite.. The strength of DaDaBIK lies in its ability to be customized.. For example for each table field you can choose:.. if the field must be included or not in search/insert/update forms and data grids.. its label.. its content format (e.. numeric, alphabetic, e-mail, url.. ).. the HTML input type (e.. textbox, dropdown menu.. the possible values, also driven from another table ("foreign key" support).. and much more.. Features include:.. Forms generation/customization.. Datagrid generation/customization.. Datagrid HTML template customization.. 12 field types.. File uploading.. Master/detail views.. Duplication checking.. Granular permissions.. Integration with external user/group/password lists.. Record locking.. Record ownership authorizations.. Email alerts.. SQL logging.. Pre-defined/custom formatting rules.. Pre-defined/custom validation rules.. Static pages.. Front-end in 17 languages (Italian, English, Dutch, German, Spanish, French, Portuguese, Croatian, Polish, Catalan, Estonian, Rumanian, Hungarian, Swedish, Slovak, Russian and Finnish).. The graphic layout of DaDaBIK is customizable to allow the integration into an existing Web site/Web application.. DaDaBIK differs from PHPMyAdmin: it has not been created to offer the complete administration of a database, but rather to allow the creation of a customizable and user friendly database application.. The target of a DaDaBIK application can be the final user instead of a DB administrator.. Since its first release in 2001 it has been downloaded more than 150.. 000 times and its users community has produced about 10.. 000 posts in the forums.. [back to top].. PHP.. version = 5.. 1.. with the mbstring extension enabled if you need to handle Multibyte character.. with LDAP support enabled if you need LDAP authentication.. MySQL.. 0 (PDO_MYSQL PHP driver required).. PostgreSQL.. version = 7.. 4 (PDO_PGSQL PHP driver required).. SQLite.. version = 3.. A pre-existent database with AT LEAST ONE table, with DaDaBIK you create database applications, not the database itself.. For MySQL, a great free tool to crate databases is.. MySQL workbench.. ; the database default charset MUST BE UTF-8 if you need to handle UTF-8 content.. Not sure if your system matches the requirements? Most probably it does, but if you want to be sure.. and we will check it for you.. DaDaBIK is not free software, it is released under the DaDaBIK license (see.. ) and its use requires to purchase a regular license from the Website www.. dadabik.. org.. It is, however, open source in the sense that, after buying a license, you get the full source code of the software.. A beginner video tutorial is available here:.. youtube.. com/watch?v=uPmXoep91Vk.. ; while it is based on version 4.. x, it can still be useful to understand the basics.. Copy everything which is contained in the directory.. program_files.. in a directory under your Web server.. Open the file.. /include/config.. php.. with a text editor and edit it (specify at least $dbms_type, $host, $db_name, $user, $pass, $site_url, $site_path, $timezone).. Run the file.. http://your_host/your_dir/install.. to install DaDaBIK.. http://your_host/your_dir/index.. in your browser and have fun!! You can now start using DaDaBIK.. You have created a basic database application based ont tables and views contained in the database $db_name.. You can customize the application via.. http://your_host/your_dir/admin.. Remember that you must set a primary key for each table managed with DaDaBIK if you want to delete and modify records; other DaDaBIK features (such as duplication checking and email alerts) also require a primary key.. You can upgrade to version.. 5.. 2.. without loosing your configuration if you are running at least version 4.. 3 final:.. Replace all the old files with the new ones (keep your upload folder if you want to save the uploaded files ).. Upgrade the Wordpress plugin in the Wordpress installations where you have used it.. Update your.. file using your old configuration settings.. http://your_host/your_dir/upgrade.. and follow the instructions to upgrade DaDaBIK.. It is not possible to upgrade from DaDaBIK BASIC to PRO/ENTERPRISE keeping your application settings; if you want to upgrade from PRO to ENTERPRISE you have to:.. The configuration of DaDaBIK can be managed at two different levels.. Some general configuration parameters can be directly set from the file.. , just by opening it with a plain text editor and editing it.. The file is self-explanatory.. At that level you can, for example, set the database you want to manage with DaDaBIK or configure some DaDaBIK features (e.. authentication, upload, email notices, language,.. For a more analytic tuning you are supposed to use the admin area.. At this level you can:.. Choose the database tables you want to include in your DaDaBIK application.. Configure your datagrids, choosing between a classic tabular data grid view (default) or a custom results page completely customizable using HTML templates.. Configure your forms: this is the core of a DaDaBIK application configuration; here, for each field, you can set.. its content (e.. how the fields are arranged in each form.. custom formatting and validation functions.. requiredness.. search operators.. and more.. Set the permissions (see the.. sections for more details).. Synchronize your applications if you change the database schema.. The admin area is also self-explanatory.. , so you can read most of the instructions on how to configure DaDaBIK by clicking on the help tooltips.. available in the admin area itself.. That's the reason why this manual is so short.. , you will find everything you need about configuration  ...   files admin.. php, datagrid_configurator.. php, db_synchro.. php, internal_table_manager.. php, permissions_manager.. php and tables_inclusion.. php can also be used to modify your installation.. If authentication is enabled, the access to the files will be protected, otherwise you should remove those files.. For additional security, you can however remove the files even if authentication is enabled.. The HTML content type and the rich_editor field type can lead to high security risks: DaDaBIK uses the popular.. htmLawed.. library to prevent displaying of dangerous HTML/Javascript code but, as the authors state, (.. bioinformatics.. org/phplabware/internal_utilities/htmLawed/htmLawed_README.. htm#s2.. 8.. ), there are some minor cases in which htmLawed can fail.. If a malicious user insert some arbitrary javascript code and the library fails in recognizing it, the code can be then executed by other users just by using the application.. Among other problems, this can lead to XSS attack (.. http://en.. org/wiki/Cross-site_scripting.. ), which in turn can allow an unauthorized access to the application (.. org/wiki/Session_hijacking.. ) and, if the Internet browser of the user contains security holes, even the execution of arbitrary code in the client machine.. Use at your own risk.. Other security-related issues are described in the section.. UTF-8 related:.. DaDaBIK supports UTF-8; however, malformed UTF-8 characters can lead to unexpected results such as content corruption.. The use of the HTML content type or of the rich text editor, in combination with UTF-8 content, is another factor that could lead, theoretically, to unexpected results.. Security/data-integrity related:.. Malicious users can exploit a field with content type set to HTML or field type set to rich_edit to insert arbitrary javascript code, this can lead to security risks if the htmLawed library doesn't filter this content properly (see above, security section, for all the details).. Searching values containing % or _ using the "contains", "starts with" or "ends with" conditions could lead to wrong search results.. Table and field names related:.. Insert/search/update fail if one or more field names contain blank spaces or dots (e.. "my field" or "my.. field" are not allowed, use "my_field" instead).. Quote characters and characters which need to be esacped such as ' ` " \, can lead to problems if used in table and field names.. Using field names containing the value set for $alias_prefix, $null_checkbox_prefix, $select_type_select_suffix, $year_field_suffix, $month_field_suffix, $day_field_suffix, $hours_field_suffix, $minutes_field_suffix, $seconds_field_suffix could lead to unexpected results; you can change the value of the above variables editing /include/config.. User interface related:.. Some language translations are not completed.. The rich editor interface (TinyMCE) is displayed in english only.. PosgreSQL related:.. DaDaBIK needs table names in lower case to work on PostgreSQL.. The insert e-mail notice doesn't work on PostgreSQL.. Insert/update don't work correctly on PostgreSQL if the user choose "Other.. " from a select_single field menu and the field has some linked fields.. Admin section related:.. The field renaming feature of the administration page doesn't work as expected if the renamed field is used in one of the following properties: "Primary key field", "Linked fields", "Order by", "Where clause" in the forms configurator related to any of the tables.. In particular, after the renaming, you will get "[08] Error: during query execution" messages from the DaDaBIK front end; you should edit the above properties by hand, renaming the field in the forms configurator.. The "refresh installation" admin operation doesn't work correctly and could lead to a forms configurator settings loss if the installation is the result of an upgrade from a DaDaBIK version 4.. 1 rc2; the "refresh installation" bug is considered fixed only for tables installed (DaDaBIK installation from scratch or single table installation from the admin interface) using a DaDaBIK version = 4.. 1 rc2.. Master/details related:.. After having accessed (in edit or details mode) a record with master/details view, DaDaBIK will show only the records related to that master record if the details table is accessed in "show items" mode.. A "remove search filter" is needed to remove the incorrect filter.. DaDaBIK does not work correctly if a master/details view is on three or more levels (e.. table A (parent) -> table B (child of A) -> table C (child of B)).. Others:.. The "previous" and "next" buttons don't work correctly after this sequence of operations: - perform a search based on a field A - change the value the field A for a record of the resultset.. Primary keys composed by multiple columns are not handled.. The "check for duplicated" feature doesn't work with file field types: DaDaBIK doesn't warn about similarity when two files have a similar name; furthermore, the "check for duplicated" feature causes uploads to fail during insert, in particular the files are not uploaded if some possible duplicated records are found and the user decides to insert it anyway.. The "check for duplicated" feature also doesn't work with date, date_time, insert_date and update_date field typed and with all fields which are hidden in the insert form.. HTML content is not set correctly as "Default value" (form configurator).. When a new option of a select_single field with linked fields is inserted through the "other.. " option, the current user is not inserted in the ID_user field of the linked table.. This means that the new record in the linked table won't get an owner and the owner permissions won't work as expected.. If, while editing a record, you change the value of the primary keye, DaDaBIK is not able to show you the updated record after saving.. Choosing a separator (~ by default) whose length is more than 1 can lead to unexpected behaviours.. The content type formatting rules is not applied individually to linked fields (select_single field type) for CSV exporting.. Unexpected behaviors (not really DaDaBIK bugs but behaviors which the average user doesn't expect).. DaDaBIK relies on the $timezone parameter for date functions (e.. to produce the current date), which can be different from the client's (user) one.. The value actually inserted in the database during an insert/update, if the value typed in the form is not part of the domain specified during table creation (e.. integer, varchar,.. ), depends on the DBMS settings and on the domain itself.. For example if an integer field is left blank during insert/update (not NULL, blank), MySQL could insert 0 as value, because an empty string is not part of the integer domain and very often the default value for integers is set to 0.. Formatting tags automatically inserted in a field through the HTML editor are not filtered during search so if you search "hey good" and you have " b hey /b good morning" in your field you won't find it..

    Original link path: /index.php?function=show_documentation
    Open archive

  • Title: PHP database front-end / CRUD generator for MySQL SQLite PostgreSQL - Create a PHP online database application / data entry application without coding - DaDaBIK is a DataBase Interfaces Creator
    Descriptive info: 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 can be related just to DaDaBIK PRO OR ENTERPRISE version.. July 23, 2013.. v.. New features.. The users page (admin area) has now a direct link to the users page (front-end).. Fixed bugs.. If a web applications/site X, installed in the same domain as a DaDaBIK application Y, used a session variable name that also the dadabik application used, unexpected and risky effects could happen if the application X or another page set a PHPSESSID cookie valid also in the DaDaBIK application path (e.. valid in the whole domain '/').. For example, if X (which could also be another DaDaBIK application) used the same session variable name to set the current "where clause" for a search, changing the "where clause" in one application could affect the "where clause" in the other.. Now a new parameter (dadabik_session_name) is available in config.. php in order to avoid this kind of problems.. In some cases, for DaDaBIK ENTERPRISE, new users (created via DaDaBIK in addition to the default ones) could not log-in because DaDaBIK thought they were LDAP users (even if they were standard DaDaBIK users).. In addition, the authentication type field was showed in the insert/edit form while it should not have been (in all versions).. Fixed.. If a field had the "Primary key field" set in form configurator but it was not a select_single field, DaDaBIK could produce unexpected results.. During insert if, for a select_single field without a linked table, a new element was added to the list ("other.. ") and the value of this element needed escaping (e.. contained a '), even if the element was already available in the list it was added (resulting in a duplicated item).. The custom formatting functions were not applied individually to linked fields (select_single field type).. Fixed (not fixed for CSV export, see later).. DaDaBIK did not work correctly and could produce error messages in the following cases:.. 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.. DaDaBIK could produce a "[08] Error: during query execution.. " message with some DBMS configurations when trying to install a table.. Page separators did not appear in the details page even if the parameter "Separator before this field (details page)" was set in form configurator.. In form configurator, the use of separator for options, linked fields and master/details (~ by default) whose length was more than 1 could lead to unexpected behaviours; now it is not possible anymore to save a separator having a length more than one.. The bug has anyway been included in the known bugs for DaDaBIK applications which are already installed.. DaDaBIK Enterprise didn't check if the dbms_type parameter was set in config.. Hungarian translation is now complete.. The documentation has been slightly improved.. The content of site_path parameter in config.. php has been better clarified.. Instructions about table inclusions have been improved, in particular it has been highlighted that if you want to delete a table from your DB you should first uninstall it in DaDaBIK and then drop it in your DB.. New known bugs.. A new known bug has been added to the documentation: the content type formatting rules were not applied individually to linked fields (select_single field type) for CSV exporting.. It will be fixed with DaDaBIK 6 because it requires core changes that we are going to apply anyway in DaDaBIK 6.. March 20, 2013.. com/dadabik_one/ and http://mysite.. com/dadabik_two/) and another page X set a PHPSESSID cookie valid in the whole domain (i.. e.. having path / ), a user who visited X and login into one of the DaDaBIK application could access the other DaDaBIK application without logging in.. X could be for example a normal php page having a session_start() statement.. While this bug is related to a known bug, already documented:.. "Malicious users could use PHP scripts for setting session variables to particular values in order to bypass the login procedure and get unauthorized access to DaDaBIK.. These scripts must be hosted on the same domain where the DaDaBIK target installation is hosted.. " the fact that can occur even without the presence of a malicious script made it even worst.. A new parameters ($secret_key) is now available and required in config.. php; its value, which must be secret and different for each DaDaBIK application you create, fixes this known bug, including the case explained above.. The Wordpress plugin has also been upgraded and requires to set a $secret_key variable as well (see installation instructions for details).. January 23, 2013.. A DaDaBIK application can now be integrated into a Wordpress site through a dedicated wrapper plug-in.. Users authenticated through Wordpress can also be automatically authenticated into DaDaBIK too, without doing the log-in again.. (Pro and Enterprise version only).. DaDaBIK now supports LDAP authentication (both OpenLDAP and Microsoft Active Directory).. (Enterprise version only).. Czech language is now available.. Changes.. A user could delete a record (using an appropriate URL) if he had delete permissions, even if the read permissions were set to MY (owner permissions) and he wasn't the owner of the record.. Now, in the same situation, he needed read permissions too for deleting.. After having accessed (in edit/details mode) a record with master/details view, DaDaBIK will show only the records related to that master record if the details table is accessed in "show items" mode.. This was and still is a DaDaBIK known bug; however, version 5 did not show the "remove search filter" link.. (Pro and Enterprise versions only).. In some cases the parameter "Field present in the search form?" did not appear in the forms configurator.. Tooltip content didn't automatically wrap inside the tooltip.. When the edit permissions were set to MY (owner permissions) a user which did not own a record couldn't modify it but it could enter into the edit screen (if he had read permissions).. Fixed, now he can't enter the edit form anymore.. After log-in, if the username was correct and the password wasn't, a PHP warning message were displayed.. DaDaBIK duplicated the last field of each table in datagrids and forms (BASIC version) or duplicated the search permission entry of the last field of each table for the default group (PRO and ENTERPRISE versions).. The configuration file stated that the groups table was used just if $enable_granular_permissions = 1, which was not correct.. Fixed, sentence deleted.. (ENTERPRISE version only).. DaDaBIK produced, in some specific cases, one or more "Notice: Undefined index: in" notice messages.. DaDaBIK produced warning messages and a "[04] Error: it is impossible to run DaDaBIK, probably because you have decided to disable all the tables or the current user doesn't have any permissions set; go to the administration interface and include some tables / set some permissions.. " message if the logged user changed his own username.. Fixed: while the [04] Error is still displayed, because the current user doesn't have permissions anymore, the PHP warning messages are not displayed anymore.. DaDaBIK could produce a "[08] Error: during query execution" when duplication checking was enabled on table_1, table_1 had a select_single field which linked table_2 and table_2 had a field whose name is equals to table_1's primary key.. If a date or date_time dadabik field was hidden from the insert/edit form, during insertion/update DaDaBIK produced some PHP notice messages and the error "You have inserted one or more not valid dates.. ".. With some DBMS configuration, DaDaBIK produced a "[08] Error: during query execution" during installation.. In case of error or warning after an insert or update, when the form was re-displayed, a date_time field lost the value for the seconds listbox and DaDaBIK produced a notice PHP message.. DaDaBIK didn't show an "Item correctly deleted.. " message after the deletion of an item in a master/details view.. The known bug about master/details view was not explained correctly in the documentation, it affects also accessing a record in details mode, not just edit mode.. Documentation fixed.. The documentation "known bugs" section didn't highlight that the "check for duplicate" feature doesn't work not only with file field types but also doesn't work (and produce PHP notice messages) with date, date_time, update_date, insert_date field types and all the fields which are hidden from the insert form.. The documentation did not explain how to upgrade from BASIC to PRO/ENTERPRISE or from PRO to ENTERPRISE and in particular did not highlight that it is not possible to move from DaDaBIK BASIC to DaDaBIK PRO/ENTERPRISE keeping the application settings (DaDaBIK must be installed from scratch).. Documentation Fixed.. After a DB Synchro -> add fields operation, DaDaBIK lost, for that table, all the form configurator values related to:.. - Tooltips.. - Separators (form dividers).. - Custom validation function.. - Custom formatting function.. - Custom CSV formatting function.. - Where clause.. - New line after this field (edit form)?.. The configuration file, in the user and group tables section, stated that "You should leave the following 12 parameters as they are.. ", the parameters were 9 instead.. Configuration file fixed.. November 24, 2012.. 0.. New graphical interface.. A completely new permissions manager which allows to set, for each users group, which operations (read, delete, update, create and details) are allowed on each form and field ($enable_granular_permissions in config.. php).. PHP hooks: for each form-field it is now possible to write a completely custom PHP validation function (used to validate data during insertion/update) and a completeley custom PHP formatting function (used to format data for datagrid and edit views).. HTML templates for data grids: the sytle of a data grid can be customizable using an HTML template, for example it is now possible to get a google-style results view instead of the classical tabular results data grid very easily just by working on the template.. Filter feature: a quick, customizable, search form a the top of the results data grid.. Static pages: the possibility to add static, custom, pages to the DaDaBIK application (e.. an help page).. Form design customization: the possibility to choose if a form field has to be positioned close to the previous one in the same form row or in a new one (default behaviour).. It is now possible to insert titled separators between sets of fields in a form.. It is now possible to specify for a field, as a default value, a value coming from a custom SQL query.. DaDaBIK can now, optionally, show a details page of the record just inserted after an insert operation (option show_details_after_insert in config).. DaDaBIK has a new field type: date_time.. It is now possible, for select_single field having data retrieved from another table, to specify a where clause to use while retreiving the data.. In a master/details view, the details table is correctly showed below the corresponding master table record not only when the edit function is used, but also when the details function is used.. The admin section has now an "about/check upgrade" page which shows information about the DaDaBIK installation and check the availability of upgrades.. It is now possible to specify the default value even for a field not present in the insert form.. It is now possible to separately choose if a field should be displayed in the insert form or in the edit form.. It is now possible to specify help tooltips for text, textarea and file fields.. DaDaBIK provides now a log feature: INSERT, UPDATE and DELETE operations are optionally logged in a logs table.. If database views (instad of tables) were installed in a DaDaBIK application, DaDaBIK allowed to see the data just in datagrid mode and not in edit/details mode.. Now it is possible to use the edit/details too; for views you need to specify the primary key of the table in the admin section.. Tinymce version updated to 3.. 5.. 7.. This can solve bugs and security issues (if any) caused by the version previously provided.. DaDaBIK's footprint drastically reduced: from 400+ files to 100+ files, total size reduced by about 40%.. Three additional search options are now available: "is different", "is not null" and "is not empty".. The parameter enable_delete_authorization_table, enable_update_authorization_table and enable_browse_authorization_table are not global anymore but can be chosen separately for each table.. It is now possible to have a custom homepage for a DaDaBIK application.. The $ask_confirmation_delete and $edit_target_window parameters now works just with the standard data grid, not with template data grids.. The content type is not taken anymore into consideration for "rich_editor" fields.. For a select_single field, the hard-coded options are not considered anymore if there are also options driven from a table.. For select_single fields, the validation in accordance to content_type is not performed any more.. The field type "password" is not supported anymore, you should convert your "password" fields (if any) to the type "text" before upgrading to DaDaBIK 5.. The autosumbit_change_table_control setting in not available any more.. If browse authorization was enabled, users could see just the records they inserted; however, through a select_single which takes the items from another table, all the records were always all visible.. The documentation did not mention that, with the "Other choices allowed?" option set to Yes for a select_single field, the "other" value is used to insert a new record in the relative primary key table EVEN IF INSERT OPERATIONS ARE NOT ALLOWED IN THE PRIMARY KEY TABLE.. The relative help tooltip now mentions this behavior.. When a user, during an insert or update, chose the "other" option for a select_single field, for the new record inserted in the linked table the id_user-type field (if any) was not filled with the username of the user, so DaDaBIK didn't give the user the ownership of the record.. Upgrading from versions before 4.. 5 pl1 produced an error, bringing to an installation which was just partially upgraded to the last version and leaving some bugs unfixed.. Because of some uncaught exceptions in the DaDaBIK PDO abstraction layer, there were some database operations that showed, in case of errors, a PDO back trace which could theoretically reveal some sensible information.. Please note that, using the official DaDaBIK release code, we are not aware of errors on that operations, but still there is the theoretical possibility of producing errors.. Setting a custom users table / custom users table fields didn't work as expected and could lead to unexpected results.. In the Italian translation a sentence had corrupted characters.. DaDaBIK showed a (wrong) search results even if the search operators choosen were not compatible with the fields, for example using a contains operator with a date field or a greater_than operator with a select_single field.. Fixed, now you can see the list of incompatibilities in the documentation and the user gets an unhandled error message in case an incompatible operator is used.. For a select_single field, mixing hard-coded options and options driven from a table could give unexpected results.. Now the hard-coded options are not considered if the options are driven from a table.. The parameter $dadabik_main_file was not used in two links, where the file name index.. php was hard-coded.. Table $table_list_name, which was supposed to follow other tables rules about naming (just the prefix must be changeable from config.. php) , was still entirely changable.. Fixed, it is now highlighted that the name must be kept as it is.. Setting $autosumbit_change_table_control = 0 produced a "Notice: Undefined variable: submit_buttons_ar" message.. The $autosumbit_change_table_control is not available any more.. DaDaBIK produced a PHP notice message if a image_file or generic_file field was SET as NULL during insert or update.. The "literal_english" date format displayed the date in a "day month year" format instead of "month day, year".. On some combinations of PHP version/Operating System DaDaBIK could produce an error during the MySQL connection.. While it was explained in the "Known bugs, limitations and unexpected behaviors" documentation section, the upgrade script did not explicit said that the upgrade does not work correctly with SQLite; a DaDaBIK upgrade using SQLite could bring to unexpected behavior.. Now the upgrade script prevent the use with SQLite.. top.. November 3, 2012.. 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.. 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.. The null checkbox didn't work as expected (enabling/disabling input fields) because of a javascript error.. Prefix and defaut values didn't work correclty if they contained a double quote character.. 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.. A re-installation of DaDaBIK on the same database didn't clean-up the table containing the information about the installation itself.. 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.. 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.. 6 beta but didn't appear in the change log, so re-post: The installation of views diddn't work with MySQL and PostgreSQL.. September 27, 2012.. 6 beta.. New feature/fixed bug.. DaDaBIK now officially supports UTF-8, allowing the correct handling of content in almost any known language and writing system.. While some hacks for adding UTF-8 support have been posted on the forum during the last years, this feature has never been officially introduced because of the drawbacks involved: PHP doesn't offer a complete support for multibyte encoding and using DaDaBIK with UTF-8 content could lead to unexpected and bad results such as content corruption.. The new version of DaDaBIK has been completely revised in order to work well with UTF-8 content; there are still some cases in which the correct handling of UTF-8 is not guaranteed, see Documentation-> Known bugs, limitations and unexpected behaviors for further details.. DaDaBIK does not use the ADOdb library anymore for MySQL and PostgreSQL.. It just uses the PHP PDO extension, as already did for SQLite.. The new requirements are: PHP >= 5.. 1 with the mbstring extension enabled and one of the following: MySQL >= 5.. 0 or PostgreSQL >= 7.. 4 or SQLite >= 3.. The database default charset must be UTF-8 if you need to handle UTF-8 content.. DaDaBIK now uses the last version of HTMLawed, which fixes several bugs affecting the version in use before, for improved security while using the HTML content type or the rich editor field type.. With SQLite, because of some uncaught exceptions, there were some queries that showed, in case of errors, a PDO back trace which revealed some information e.. the path of the PHP file or the query itself.. Please note that, due to the nature of the queries involved, it should have been difficult, for a malicious user, to intentionally cause the queries to fail in order to display those information.. While the documentation said that quote characters can lead to problems if used in table and field names, also all the characters which need to be escaped such as ' ` " \ can lead to the same problems, documentation updated.. DaDaBIK didn't create interfaces on views if used with SQLite.. A date, insert_date or update_date field having just one search operator prevented the display of a "blank option" in the search operators listbox.. This means that it wasn't possible to perform a search without considering such a field, if it was in a form.. Table or field names having the string “from” in the name could lead to query execution error with SQLite.. Registering a new user having a username or password which contained characters which needed to be escaped (e.. ') was not possible.. The check about the max length of a field value didn't work correctly if the user inserted a value containing a character which needed to be quoted (e.. ').. If a field had a prefix, the check about the field type (e.. email checking), which was supposed not to be performed if the user just left the field as it was (filled by the prefix) during an insert/upate, was instead performed on the prefix if the prefix contained a character wchich needed to be quoted (e.. If a field had a prefix, the "check for duplicated" and "check requried" feature didn't work correctly if the prefix contained a character wchich needed to be quoted (e.. If a field had a prefix and the user just left the field as it was (filled by the prefix) during an insert/upate, DaDaBIK inserted in the database the prefix instead of a blank value if the prefix contained a character wchich needed to be quoted (e.. The "check for duplicated" feature didn't work correctly if the user filled one of the field to check with a value containing a character which needed to be quoted (e.. The check type (email, url,.. ) feature could (should be very unlikely) not to work correctly if the user filled the field to check with a value containing a character which needed to be quoted (e.. A select_single field having options set by hand and allowing the choice of additional options added the additional options to the list of the options even if tis was already existent (creating a duplicate) if the option contained a character which needed to be quoted (e.. A master details view didn't show the items record related to the master record and didn't allow to create new items if the primary key field value of the master record contained a character which needed to be quoted (e.. A primary key containing as value a character which needed to be quoted (e.. ') could lead to unexpected results.. If the master/details feature was used, a primary key field name of the master table or its value containing a character which needed to be url-encoded to be passed via querystring (i.. all non-alphanumeric characters except -_.. ) could lead to unexpected results.. Remember that table and field names still have restrictions (see the documentation, known bugs).. A table name containing a character which needed to be url-encoded to be passed via querystring (i.. The table menu in the front-end is now always ordered by the table alias.. Some outdated parts of the documentation has been removed.. The setting $enable_word_wrap_cut is no longer available.. August 15, 2012.. 5 patch level 1 (pl1).. DaDaBIK used to store users' passwords using the encryption provided by md5().. While this approach allows for a first level of security, because passwords are not stored in clear text into the database, it does not prevent some type of attacks which a malicious user can do after having obtained the encrypted passwords, such as attacks based on pre-hashed  ...   the problems related to the CSV creation time limit errors.. Two DaDaBIK buttons are now available ("buttons" folder).. DaDaBIK didn't display correct search result values when the same field name appears in two linked tables as linked field.. This bug, supposed to be fixed in the 3.. 1 beta release, is now really fixed.. DaDaBIK showed a wrong list of result records for a search if $enable_authentication and $enable_browse_authorization were enabled and the user specified more than one search criteria, setting also "Any of the conditions required".. The required property didn't work properly with file types, now the setting of a file-type field as "not required" is not needed any more.. Thanks to alpha2zee (drpatnaik at yahoo dot com) who proposed the first version of the patch.. DaDaBIK produced a "Fatal error: Call to undefined function: newadoconnection()" message if upgrade.. php or upgrade_3.. php were executed.. DaDaBIK produced a "Notice: Undefined variable: upgrade.. " message when upgrade.. php was executed.. In the login.. php script the name of the file index.. DaDaBIK didn't display the "create password" after a user adding if $insert_again_after_insert was set to 1.. DaDaBIK displayed some messages in English even if the language set was "Italian".. June 20, 2005.. 0 alpha.. DaDaBIK produced some "Notice: Undefined variable.. " messages and a "[08] Error: during query execution" error message in the details or edit view (if $enable_browse_authorization was enabled) or after a delete (if $enable_delete_authorization was enabled) or update (if $enable_update_authorization was enabled); only if $enable_authentication was enabled and the current table or the ID_user field name needed to be quoted.. If the $autosumbit_change_table_control parameter was set to 1 the tables listbox form in the administration section was not auto-submitted "on change" and a javascript error was produced when the current table was changed.. DaDaBIK uses now the.. ADOdb.. Database Abstraction Library in order to support as many DBMS as possible, at the moment it has been tested just with MySQL 4.. x and PostgreSQL 8.. x.. SQL logging: it is now possible to configure DaDaBIK for logging all SQL queries in the adodb_logsql table ($enable_sql_logging parameter in config.. The documentation has been revised.. June 4, 2005.. 3.. If two or more DaDaBIK installations were hosted under the same domain, if a user logged into one of them it was possible to access all the others bypassing the login procedure.. DaDaBIK session cookies are now valid only for the directory where DaDaBIK is installed (set through the new configuration variable $site_path).. DaDaBIK produced a parse error if the Portuguese language was used.. Croatian translation is now complete.. DaDaBIK produced a "[08] Error: during query execution" error message in the results view if the table in use or the current "order by" field name needed to be quoted and the current "order by" field hadn't any linked fields.. The possible duplications results view didn't show linked field values and produced a "Notice: Undefined index.. " error message if one ore more fields had linked fields (.. php?f=1 i=4302 t=4154.. Added two known bugs to the documentation, in particular it has been highlighted a possible security problem of the DaDaBIK authentication model.. March 31, 2005.. DaDaBIK produced a "[08] Error: during query execution" error message in the details view if, for a field, the primary key field name of the main table was the same of the primary key field name of the linked table.. All the "Undefined variable" error messages have been fixed, DaDaBIK can now works correctly with error_reporting = E_ALL.. DaDaBIK lost the "Other choices allowed?" option information after a "Refresh installation" procedure (administration interface).. DaDaBIK produced a "[08] Error: during query execution" error message if, during an insert or update, a new option was added to a select_single field with no linked fields and at least one of the preexisting options contained a character to be escaped (e.. DaDaBIK produced a "[08] Error: during query execution" error message if, during an insert or update, there was at least one select_single field with linked fields, $enable_authentication and $enable_browse_authorization were enabled, the table contains an ID_user field and the linked table doesn't contain any ID_user fields with the same field name.. An Italian sentence was not correct.. DaDaBIK produced a parse error message if the German language was used.. (.. php?f=1 i=3432 t=3432.. In the footer page the name of the file index.. php?f=2 i=371 t=371.. Config variable $always_add_blank_option_search didn't work correctly, the variable is not used any more and now DaDaBIK always add a blank option to the select_single fields.. The authentication code has been in part rewritten:.. The class simpleLogin (.. 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.. Six new languages are available: Croatian, Polish, Catalan, Estonian, Rumanian, Portuguese.. A "top" link has been added to the HTML footer.. The documentation has been updated and improved, in particular a FAQ section is now available.. The installation procedure has now more explicative messages.. July 19, 2004.. DaDaBIK produced a "[08] Error: during query execution" when a linked table was referenced more than once in the same table.. DaDaBIK didn't display correct result values when the same field name appears both in a table and in a linked table as linked field or in two linked tables as linked field.. DaDaBIK has now a rewritten engine that perform the select query using joins and aliases (this fixes the bug above).. A basic authorization model is available, it is now possible to allow a user to delete only his own records, modify only his own records, view only his own records.. For the authentication the class simpleLogin (.. ) has been (probably temporary) used, but it is possible to easily customize the authentication.. A new field type is available:.. rich_editor.. ; it is a rich text editor (htmlArea 2.. 03 by interactivetools.. interactivetools.. com/products/htmlarea/.. ) that allows to easily insert/modify HTML content.. A new content type is available:.. html.. , DaDaBIK doesn't perform a conversion from special characters to HTML entities with.. htmlspecialchars.. for the fields having this content type.. DaDaBIK starts now displaying the records of the first table available, without showing the home page menu.. All the application (except from the administration area) uses now just one file index.. php, easily renameable to embed it in a pre-existent Web site.. An upgrade script is now available, it is possible to upgrade from 3.. 0 beta or 3.. 0 to 3.. 1 beta without loosing the interface configurator settings.. A new parameter $enable_delete_all_feature allows to enable/disable the.. delete all.. feature.. May 25, 2004.. DaDaBIK produced a "[08] Error: during query execution" error when a table name contained blank spaces (.. php?f=1 i=2136 t=2136.. DaDaBIK produced a "[08] Error: during query execution" error when the MySQL version was prior to 3.. 23.. 06.. DaDaBIK produced a "[08] Error: during query execution" error when a field has some linked fields associated and the primary key field is not numeric (.. php?f=1 i=2365 t=2365.. DaDaBIK produced a "Call to undefined function: ob_clean().. " fatal error if the export to CSV feature was enabled and the PHP version was 4.. 0 (.. php?f=1 i=2329 t=2209.. ); the export to CSV now works also with PHP version prior to 4.. DaDaBIK produced a parse error when the Italian language was used.. Fixed some translations and added a missing sentence in the Italian language file.. The word "home" in the bottom links menu is now available in each language file and no more hard-coded.. DaDaBIK produced a "Undefined variable: mail_feature.. " notice.. A new parameter $word_wrap_fix_width allows to choose if $word_wrap_col determines also the width of the column in the results table or not.. Notes.. The following two bugs have been discovered during the beta testing:.. DaDaBIK produces a "[08] Error: during query execution" when a linked table is referenced more than once in the same table (.. php?f=1 i=2374 t=2374.. DaDaBIK doesn't display correct result values when the same field name appears both in a table and in a linked table as linked field or in two linked tables as linked field.. These bugs will be fixed in the version 3.. 1 because they require to partially rewrite the engine that produce the SELECT statement.. March 10, 2004.. 0 Beta.. All the code has been revisited and in some case rewritten in order to increase efficiency and clarity.. The primary-foreign key feature is now complete: it is possible to link a field of a table (foreign key) to a number of fields of another table (containing the primary key).. The produced HTML select menu will have the linked field values as "options" and the primary key values as "values".. This allow to use a normalized db design.. The "export to CSV" feature has been added: it is now possible to export the current result records to a CSV file.. The speed of DaDaBIK when the database managed contains a lot of tables is now dramatically increased.. "Delete all" feature is now available: it is possible to delete all the current result records.. It is now possible to handle all the HTML produced by DaDaBIK by the CSS file, which is now very clear and complete, a new CSS file specific for printing has been also added.. It is now possible to order result records both in ASC and DESC.. The HTML produced by DaDaBIK is now more clean and complete than before.. If no order field is specified, the result records are displayed ordered by the first field present in the results table.. Two new select operators have been added: "starts with" and "ends with".. The confirmation message of a delete operation is now a javascript prompt confirmation message (it is possible to disable it through config.. php, however).. After a delete operation DaDaBIK now display again the results page.. The alternate row colors feature is now available.. The record results table is now displayed using alternate row colors.. When you save a record, now the edit form is displayed again on the screen.. When you insert a new record, you can now choose (through config.. php) if you want to see again the insert form, otherwise the results table is again displayed.. Edit, delete and details buttons are now normal links (not HTML forms as before) and pass all the necessary values via GET, so it is now possible to call the detail page of a record from its own unique URL.. Documentation, administration interface and config.. php file are now more clear and complete than before.. Each DaDaBIK error message has now a code, in order to identify it better, especially during bug reports.. DaDaBIK messages are now displayed everywhere needed and are more clean than before.. It is now possible to disable the displaying of the search/insert/update buttons at the top of the form through config.. It is now possible to change the select operator names (is equal/contains/greater than/less than/starts with/ends with) according to the language.. The function that validate URLs now support port numbers, https protocol and four letters primary domain name (e.. info).. The validity of a date field is now checked during insert/update.. The word wrap column choosen in config.. php now determines also width of the columns in the results table; the width is now fixed and equal for all column.. It is now possible to choose (through config.. php) if always wrap words at the $word_wrap_col column, even if it is necessary to cut them.. DaDaBIK now use the $_GET $_POST $_FILES.. variables introduced in PHP 4.. The change table select menu is now an auto-submit one (it is possible to disable this feature through config.. The update statements now use "LIMIT 1" to ensure that only one record is updated, but only if the MySQL version is = 3.. A blank first option is always added to select_single fields when a search form is produced (it is possible to disable this feature through config.. The select_multiple field types are not handled any more, at least for the moment.. Linking tables contained in different databases isn't handled any more.. DaDaBIK no more display automatically a column sign (":") after each label.. Fixed bugs:.. DaDaBIK didn't update correctly a record when the "Other.. " option of a select_single field was used.. DaDaBIK produced an error when tried to display the possible duplicates during an insert operation if some field names need back quotes.. DaDaBIK produced an error when the user clicked on a result page link and the current "order by" field needed to be url encoded.. DaDaBIK produced an error when tried to retrieve values of a select_single from another table if some field or table names need back quotes.. Field order changer didn't work properly: field positions weren't shifted correctly.. DaDaBIK check the similarity of records during and insert operation by using a case sensitive function, this was not correct.. DaDaBIK failed to handle properly the upload when the uploaded file name contained a single quote.. DaDaBIK displayed a broken image link if a record containing an image_file field had no images associated.. This happened only with MS IE as a browser.. Fixed the bug that produced a "Warning: stat failed.. " message sometimes during an upload.. DaDaBIK lost the value associated with the "Other choices allowed" parameter when, from the administration interface, you clicked on "Refresh internal table".. Upload failed when two files with the same name were uploaded in the same time.. Word wrap feature now works also with email and url fields.. Back quotes were used only if the MySQL version was 3.. 6, even if also MySQL 3.. 6 supports them, now are used if the MySQL version is = 3.. 6.. It was possible, by maliciously changing the HTML of a form produced by DaDaBIK when possible duplicated were found and post it, to bypass fields check.. DaDaBIK didn't show the SQL statement ($display_sql set to 1) related to a search if no records were found.. March 11, 2003.. 2.. When a record containing an image_file or generic_file field was updated without uploading a new file, the record loosed the link with the old file; this bug has been fixed.. When a user perform a search in a table containing an image_file or generic_file field the "browse" button was displayed by the browser for those fields, this behavior makes no sense; this bug has been fixed.. The field names of the where clause in the update statements were not back quoted, consequently the update failed if the name of the primary key field needed to be escaped (e.. a reserved word), this bug has been fixed.. The dutch version of DaDaBIK produced a parse error, this bug has been fixed.. It is now possible to choose if you want to delete (both in the database and phisically) a previously uploaded file.. When two or more files with the same name are uploaded, a new name is assigned automatically (e.. my_file.. txt become my_file_2.. txt if my_file.. txt already exists, my_file_3 if also my_file_2 already exists and so on).. It is now possible to configure DaDaBIK to accept all files (regardless to the extensions) coming from upload.. Since DaDaBIK requires to set magic_quotes_gpc = on in php.. ini (which is the default setting), now if magic_quotes_gpc is off DaDaBIK will stop and display an error message.. Novermber 9, 2002.. The bug that caused the lost of the correct search results when the user click on a page number, supposed to be fixed in the previous release, is now completely fixed.. The version of the MySQL server is now correctly checked, in this way the "Your database is empty" bug, supposed to be fixed in the previous release, is now completely fixed.. A known bugs document is now available.. October 22, 2002.. Support for file uploading (images and other) is now available.. The bug that caused the lost of the results order when the user click on has been fixed.. The bug that caused the lost of the correct search results when the user click on a page number has been fiexed.. Fixed the bug that prevented the internal table manager to work correctly when the result order is changed.. The version of the MySQL server is now checked, in this way the "Your database is empty" bug has been fixed.. The numeric type now accepts also float and other numeric fields.. July 31, 2002.. 1b beta.. Web and e-mail fields weren't display correctly in the version 2.. The bug is fixed with tihs version.. July 30, 2002.. A new, lighter and easier to use administration interface (related to the internal table manager) is available.. The form has now a better layout, all the fields are correctly aligned, including dates.. All the translations are now up-to-date.. It is now possible, for select_single fields, to choice "other" during an insert and fill a textbox by hand with an alternative value.. That value also update the select options, unless option had driven with a custom query ("SQL:.. ").. It is now possible to choice if a field has to be displayed in the details page or not.. Completely fixed the bug the caused the warning message: "Warning: Call-time pass-by-reference has been deprecated.. " with particular php.. ini settings.. It is now possible to use the "-" sign and other allowed signs in MySQL table and field names.. Fixed a bug that prevent some text to be displayed if written after a special html char (e.. Fixed a bug that prevent to choose more than 999 characters as maxlength of a field.. Fixed a bug related to the use of the double quote in the include statements, that can cause error messages.. Textbox and password fields are now checked for max lenght also server side.. Select_single fields are now checked for length and type, this improve security because a malicious user could change the html of the form and then post it.. Jun 28, 2002.. DaDaBIK is now compatible with PHP 4.. 2, and works also with register_global directive set to off.. Added two new date display formats, which fix the problem of displaying dates before 1970.. Fixed a bug that caused the insert of a separator if a select_multiple_menu or a select_multiple_checkbox were empty.. The "Any/all" conditions menu now appers also in Netscape and other browsers.. Fixed some minor bugs that caused warnings and notices.. Jun 1, 2002.. Support for multiple tables available.. "View all records" feature.. It is now possible to order a group of record by a field clicking on the corrisponding coloumn.. The pages navigation tool has been improved.. Fixed a bug about size of input field in Netscape.. Fixed a bug that about the color of the required fields in the search form.. Apr 21, 2002.. 1.. Fixed a bug that allowed an attacker to execute arbitrary sql query on the database (e.. insert or delete records even if insert and delete feature were disabled).. Fixed a bug about double quotes handling in the search function.. All DaDaBIK users are encouraged to update to the latest version.. Apr 15, 2002.. Fixed the bug that caused an error during the insert if you didn't enable the check similiarity for any fields.. Fixed the bug that caused a "Required field" message even if a date field was filled by the user.. Fixed the bug the caused a warning message if allow_call_time_pass_reference is set to false in php.. Added Spanish and French versions.. Mar 18, 2002.. The algorithm that scans existing records during an insert in order to find similar records is now more efficient (e.. for a table with 8000 records, 2 fields to check, it is now 5 times faster than before).. Update now works also with a MySQL version 3.. Fixed the bug that caused an error if a date field was initally null.. Feb 28, 2002.. New features:.. A new administration interface is now available and allows you to manage the internal table without any other software!! So you don't need PHPMyAdmin any more in order to customize DaDaBIK.. Configuration is now easier.. Debug mode added.. Feb 11, 2002.. It is now possible to disable the functions: insert, update, delete and details; in this way you can safety use DaDaBIK in a public site.. New administration interface for the internal table.. The installation procedure is now more explicative.. New customizable graphic icons for edit/delete/details buttons.. You can now choice the coloumn at which a text, textarea, password or select sinlge field will be wrapped in the results.. It is now possible to choice the target window for edit/details (self or new).. The graphic layout of the form looks now better with Netscape.. German translation added.. Jan 27, 2002.. 5b.. In the version 1.. 5 I missed the code line that allow to use the dutch version, the version 1.. 5b include a fix to that bug together with a config.. php file more precise.. Jan 26, 2002.. DaDaBIK is now considered out of beta and has some important new features, for this reason I decided to call this release 1.. 5 (the last was 1.. 1 beta).. Partial foreign key support: it is now possibile to drive the possible options of a "select_multiple" or "select_single" field from another table, even with a customized SQL query!!.. It is now possible to select between any/all the conditions during a search.. It in now possible to display a select_multiple field also with a menu (HTML select multiple tag).. For each field you can now specify a prefix value (e.. http://) and a default value.. For each field you can now specify which operator the user can use, including exactly, like, ,.. A Dutch version of DaDaBIK is now available.. An on-line demo is now available.. Minor bug fixed.. The results of a search are now displayed taking the carriage return (\n) into account.. Jan 14, 2002.. According to user's needs, now the internal table and the main table are in the same database, so you don't need two databases in order to run DaDaBIK.. It is now possible to specify the order of a field in the form.. Required fields message now apper only if there are at least one required field.. Search of a "select single" field with exact/like feature enabled now works.. Some updates didn't work, now the bug has been fixed.. Bug about searching by date fixed, now you can search properly a record by date using or.. Time generated by insert_date and update_date are now in 0-24 format.. Dec 9, 2001.. Documentation:.. The configuration file is now more explicative.. The readme file is now more explicative.. A new document about the internal database is now available.. Now you can select between an "exact match" or a "like" search also in the form, on the fly.. (You can also disable this feature).. Hints are now visible even during the update procedure.. Bugs fixed:.. The maxlength property in the internal database now works.. A very small part of the function build_form() rewritten in order to make DaDaBIK more flexible.. Dec 5, 2001.. Two HTML-related bugs fixed:.. the background of an empty cell now appears even with Netscape.. the select input field now appear correctly even with Netscape.. Dec 1, 2001.. Italian version added.. Some english mistakes fixed.. Configuration option (display the "I think that x is similar to y.. " statement during duplication check) added.. Nov 24, 2001.. One bug fixed (creation of the internal database didn't work due to bug in db_functions.. Several bugs fixed (creation of the internal database didn't work, navigation buttons didn't work).. Nov 21, 2001.. V.. The first release of DaDaBIK..

    Original link path: /index.php?function=show_changelog
    Open archive





  • Archived pages: 608