Old Instance 1.2.19 Error after upgrade to Mantis BT 2.2.0

[saayid]

Hi all,

Need some emergency assistance

I am getting an error while trying to access the old instance of Mantis ( 1.2.19). I was able to perform an upgrade to
SYSTEM WARNING: 'Invalid argument supplied for foreach()' in 'D:\MANTISPRODUCTION\htdocs\MantisBt\core\columns_api.php' line 363

Here are the steps i followed.

1. In XAMPP htdocs folder i pasted the unzipped folder Mantis BT 2.2.0 ( renamed to test2)
2.Ran the install ( No errors during install)
3.Launched the New Instance http://<<Server Name>>/test2 launches without any error
4.Launched Old Instance and i am getting error SYSTEM WARNING: 'Invalid argument supplied for foreach()' in 'D:\MANTISPRODUCTION\htdocs\MantisBt\core\columns_api.php' line 363

Could someone point out how i can resolve this?

Old Version: 1.2.19
New Version: 2.2.0
Windows Server 2012 R2

[atrol]

Do your old instance (1.2.19) and new instance (2.2.0) use the same database instance?

[cas]

This may be due to one of the plugins not being compliant.....

[saayid]

Do your old instance (1.2.19) and new instance (2.2.0) use the same database instance?

How can i check the same? i have used the same DB credentials as the one used for the prior install. Could i fall back/restore to earlier instance?

[atrol]

Check file config_inc.php in 1.2.19 and config/config_inc.php in 2.2.0
Are there the same settings for those three options?

Code: Select all

$g_db_username			= 'root';
$g_db_password			= '';
$g_database_name		= 'bugtracker';

If yes, you are accessing the same database.

Accessing the same database from 1.2.19 and 2.2.0 at the same time is not possible as the database schema has been changed by the 2.2.0 upgrade process.

You have to restore your database backup if you want to go on using 1.2.19.

[saayid]

Check file config_inc.php in 1.2.19 and config/config_inc.php in 2.2.0
Are there the same settings for those three options?

Code: Select all

$g_db_username			= 'root';
$g_db_password			= '';
$g_database_name		= 'bugtracker';

If yes, you are accessing the same database.

Accessing the same database from 1.2.19 and 2.2.0 at the same time is not possible as the database schema has been changed by the 2.2.0 upgrade process.

You have to restore your database backup if you want to go on using 1.2.19.

It's the same, one more issue that i am facing is Custom Strings and Custom Config are not reflecting correctly, prior upgrades this was coming correctly


Custom Strings:

<?php
{$s_status_enum_string = '10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned,80:resolved,85:tested,90:closed';
$s_access_levels_enum_string ='10:Reviewer,25:Reporter,40:Updater,55:Developer,60:CNC,61:Devlead,62:SQAlead,70:Manager,80:SQA,85:UAT,90:Administrator';
$s_resolution_enum_string ='10:open,20:fixed,30:reopened,40:unable to reproduce,50:not fixable,60:duplicate';
}

Config_Inc.php


<?php
$g_hostname = 'localhost';
$g_db_type = 'mysql';
$g_database_name = 'bugtracker';
$g_db_username = 'root';
$g_db_password = 'sqa123';
$g_status_enum_string = '10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned,80:resolved,85:tested,90:closed';
$g_allowed_files = "zip,png,bmp,gif,jpg,tiff,jpeg,txt,pdf,doc,docx,xls,xlsx,ppt,pptx,odt,fodt,ods,fods,odp,fodp,odb,odg,fodg,odf,tcl,dat,mp4,avi,wmv,mpg,mpeg,mp3";
$g_status_colors['new'] = '#1E90FF';
$g_status_colors['feedback'] = '#20B2AA';
$g_status_colors['acknowledged'] = '#CAE1FF';
$g_status_colors['confirmed'] = '#FFFF00';
$g_status_colors['assigned'] = '#e35757';
$g_status_colors['resolved'] = '#E6E600';
$g_status_colors['tested'] = '#9FF781';
$g_status_colors['closed'] = '#B9DFE7';
// Added Tester access level
$g_access_levels_enum_string ='10:viewer,25:reporter,40:updater,55:developer,60:cnc,61:devlead,62:sqalead,70:manager,80:SQA,85:UAT,90:administrator';
$g_resolution_enum_string ='10:open,20:fixed,30:reopened,40:unable to reproduce,50:not fixable,60:duplicate';
//70:no change required,80:suspended,90:won't fix,91:ready for test,92:testing complete,93:ready for uat,94:ready for production';
$g_enable_profiles = OFF;
$g_show_realname = ON
?>

[atrol]

Did you exactlyfollow the upgrade guide https://www.mantisbt.org/docs/master/en ... ll.upgrade
Especially step 3

Copy the configuration files
To preserve your system settings, you should copy the files listed below to subdirectory config of the new directory. ....

[saayid]

Did you exactlyfollow the upgrade guide https://www.mantisbt.org/docs/master/en ... ll.upgrade
Especially step 3

Copy the configuration files
To preserve your system settings, you should copy the files listed below to subdirectory config of the new directory. ....

Yes, Sir i have followed the instruction's to the best of my knowledge but some thing has been wrongly done/missed. I have done a DB restore and have reverted back to the prior configuration. I will perform another test install with more precaution to ensure that i have performed all the steps correctly as documented in the upgrade guide.

Thank you for the excellent support! I really appreciate the swift responses that have always assisted me!