Feature Requests

It would be great to have an option to hide all empty fields in the details page. For example my (historical) database consists of different data sets and some have a reference to source A, but not B-E etc. So in the details page there's generally a lot of field decriptions with no values behind them. It would be al lot cleaner if those empty fields were hidden. It could be a general option (hide all empty fields in details page) or an option per field (hide when empty yes/no).

For some applications it would be handy to have the ability to search for a keyword in any field. A "all fields" could be added to the permissions for a table and could be added to either Quick Search or full Search.

Sometimes it is necessary to limit useraccess to the database. A simple checkbox, where the admin can lock a useraccount so that he cannot Login would be nice.

To augment the existing capabilities of creating custom dashboards and reports in PHP for use in DaDaBik web applications, we are curious if there are any possibilities for better integration in calling Dash/Flask/Python based applications that are hosted in the existing web server document tree. Python is becoming a much more commonly used language over PHP in our corporate setting which is driving requests to have DaDabik work with these newer toolsets.

Checkbox in users table/form: "User must change password at next logon". Checked by default when new user is created or when password is changed by administrator. Standard behavior, after user logs in password must be changed before he can continue to the system.

A book that covers, in a single volume: simple database design rules how to build a DaDaBIK app from A to Z some PHP and Javascript knowledge you might need if you want to add your own custom code

Hi Eugenio, I didn't see here a proposal made on the old forum, asking for a caution message when we return from an edition page without having saved the new inputs. This kind of omission is notably done in case of a "master/details view" that we edit just after having made changes in the main form above. Saving the master/details record, doesn't save the changes made above. I often do this galling mistake ;) Even reindex a column in the master/details view, can lose the changes made in the main from if not saved before.

e.g.: /customers/23/edit instead of: index.php?tablename=customers&function=edit&where_field=id_customer&where_value=23

The export will automatically produce a DaDaBIK pre-packaged app (following what is explained in apps/how_to_create_a_packaged_app.txt); this is useful both for backup purposes and for building a package that you can import in another DaDaBIK installation or sell to your customers.

Two-factor authentication