Mantis Bug Tracker - Forums

Hi
in order to check if users are confortable with new version 1.3.5, I would like to point to SAME DB from a 1.2.20 installtion and a 1.3.5

I've got my old 1.2.x DB and run installer/upgrade of 1.2.20 => everything OK.
Login without issues.

I've then run installer/updater AGAINTS same DB using 1.3.5 code, I've had a minor issue because it tries to add a column that already exits:
$g_upgrade[185] => I had to comments it.

If I access using code 1.3.5 => OK, but when I access using 1.2.20 I get issue on

SYSTEM WARNING: 'Invalid argument supplied for foreach()' in '/development/mantis/mantisbt-1.2.20/core/columns_api.php' line 368

I've added a couple of var_dump and got

columns_remove_invalid($p_columns,$p_columns_all)

$p_columns => bool(false)

$p_columns_all =>
array(41) { [0]=> string(2) "id" [1]=> string(10) "project_id" [2]=> string(11) "reporter_id" [3]=> string(10) "handler_id" [4]=> string(12) "duplicate_id" [5]=> string(8) "priority" [6]=> string(8) "severity" [7]=> string(15) "reproducibility" [8]=> string(6) "status" [9]=> string(10) "resolution" [10]=> string(11) "category_id" [11]=> string(14) "date_submitted" [12]=> string(12) "last_updated" [13]=> string(2) "os" [14]=> string(8) "os_build" [15]=> string(8) "platform" [16]=> string(7) "version" [17]=> string(16) "fixed_in_version" [18]=> string(14) "target_version" [19]=> string(10) "view_state" [20]=> string(7) "summary" [21]=> string(17) "sponsorship_total" [22]=> string(8) "due_date" [23]=> string(11) "description" [24]=> string(18) "steps_to_reproduce" [25]=> string(22) "additional_information" [26]=> string(16) "attachment_count" [27]=> string(14) "bugnotes_count" [28]=> string(9) "selection" [29]=> string(4) "edit" [30]=> string(7) "overdue" [31]=> string(29) "custom_Ambiente / Environment" [32]=> string(28) "custom_Anomalia originata da" [33]=> string(16) "custom_Argomento" [34]=> string(22) "custom_Fase Originante" [35]=> string(15) "custom_fixed in" [36]=> string(35) "custom_Installato in / Installed in" [37]=> string(19) "custom_Ore Lavorate" [38]=> string(22) "custom_Segnalatore OBL" [39]=> string(14) "custom_test QA" [40]=> string(22) "custom_Tipo Intervento" }


While on 1.3.5

columns_remove_invalid
p_columns
array(12) { [0]=> string(9) "selection" [1]=> string(4) "edit" [2]=> string(8) "priority" [3]=> string(2) "id" [4]=> string(17) "sponsorship_total" [5]=> string(14) "bugnotes_count" [6]=> string(11) "category_id" [7]=> string(8) "severity" [8]=> string(6) "status" [9]=> string(12) "last_updated" [10]=> string(7) "summary" [11]=> string(14) "target_version" }

p_columns_all
array(41) { [0]=> string(2) "id" [1]=> string(10) "project_id" [2]=> string(11) "reporter_id" [3]=> string(10) "handler_id" [4]=> string(8) "priority" [5]=> string(8) "severity" [6]=> string(15) "reproducibility" [7]=> string(6) "status" [8]=> string(10) "resolution" [9]=> string(11) "category_id" [10]=> string(14) "date_submitted" [11]=> string(12) "last_updated" [12]=> string(2) "os" [13]=> string(8) "os_build" [14]=> string(8) "platform" [15]=> string(7) "version" [16]=> string(16) "fixed_in_version" [17]=> string(14) "target_version" [18]=> string(10) "view_state" [19]=> string(7) "summary" [20]=> string(8) "due_date" [21]=> string(11) "description" [22]=> string(18) "steps_to_reproduce" [23]=> string(22) "additional_information" [24]=> string(16) "attachment_count" [25]=> string(14) "bugnotes_count" [26]=> string(9) "selection" [27]=> string(4) "edit" [28]=> string(5) "notes" [29]=> string(4) "tags" [30]=> string(7) "overdue" [31]=> string(29) "custom_Ambiente / Environment" [32]=> string(28) "custom_Anomalia originata da" [33]=> string(16) "custom_Argomento" [34]=> string(22) "custom_Fase Originante" [35]=> string(15) "custom_fixed in" [36]=> string(35) "custom_Installato in / Installed in" [37]=> string(19) "custom_Ore Lavorate" [38]=> string(22) "custom_Segnalatore OBL" [39]=> string(14) "custom_test QA" [40]=> string(22) "custom_Tipo Intervento" }


BOTH ARE RUNNING ON SAME SERVER with DEFAULT CONFIGURATION


Any hint/idea ?

thanks
Francisco

fmancardi wrote:in order to check if users are confortable with new version 1.3.5, I would like to point to SAME DB from a 1.2.20 installtion and a 1.3.5

This is not possible as there are diffrences in database schema of 1.2.10 and 1.3.5.

May be I'm wrong, but I've exported schema of my current 1.2.x db and compare with 2.0.0 schema and have found not critic differences.
What I've found is that my issue arise because on 1.2.x COMPLEX config options are saved on db using serialize, while in 1.3.5 and 2.0.0 json_encode is used, or at least this seems

The differences are listed in admin/schema.php starting from $g_upgrade[185] to $g_upgrade[209]
IMO this is enough that 1.2.x and 1.3.x should not point to the same DB.