Hello,
in case your $prefix_internal_table is not "dadabik_" (the default one) or you are using a custom groups table or a custom name for the id_group field of the groups table, the up/up2 upgrade procedure will generate an error (Foreign key constraint related).
Workaround: if you already tried the up/up2 upgrade, you must restore your application with a full file+db backup, then use the old upgrade/upgrade2 procedure.
Just before launching the upgrade.php script, you must edit the file
/include/dadabik_tables_creation_functions.php
changing this code:
in a way that reflects your $prefix_internal_table and/or your custom id_group field name. For example if your $prefix_internal_table is "xyz_", the code must become
in case your $prefix_internal_table is not "dadabik_" (the default one) or you are using a custom groups table or a custom name for the id_group field of the groups table, the up/up2 upgrade procedure will generate an error (Foreign key constraint related).
Workaround: if you already tried the up/up2 upgrade, you must restore your application with a full file+db backup, then use the old upgrade/upgrade2 procedure.
Just before launching the upgrade.php script, you must edit the file
/include/dadabik_tables_creation_functions.php
changing this code:
PHP:
REFERENCES dadabik_groups(id_group)in a way that reflects your $prefix_internal_table and/or your custom id_group field name. For example if your $prefix_internal_table is "xyz_", the code must become
PHP:
REFERENCES xyz_groups(id_group)