Date not displayed after upgrade from 1.1.6 to 1.3.18
Moderators: Developer, Contributor
Date not displayed after upgrade from 1.1.6 to 1.3.18
Howdy,
I upgraded to the last 1.x version, 1.3.18 from 1.1.6.
Everything's fine so far, and i can now specify timezone in config, great.
But now I have two issues:
1,
my issues are all in 01-01-1970 as date of creation and update.
I still have access to the 1.1.6 install and it show's the date fine.
Am i missing something or it's needed something extra?
2,
Line breaks are not working in 1.3.18, in the old 1.1.6 works.
Check the attach's images.
Thanks in advanced,
I upgraded to the last 1.x version, 1.3.18 from 1.1.6.
Everything's fine so far, and i can now specify timezone in config, great.
But now I have two issues:
1,
my issues are all in 01-01-1970 as date of creation and update.
I still have access to the 1.1.6 install and it show's the date fine.
Am i missing something or it's needed something extra?
2,
Line breaks are not working in 1.3.18, in the old 1.1.6 works.
Check the attach's images.
Thanks in advanced,
Re: Date not displayed after upgrade from 1.1.6 to 1.3.18
Hum, checking the tables, not the order that is different, but the type of fields, for some how they're using different formats.
Can you help me with SQL's to convert, if this is whats needs to be fixed.
Current schema for mantis_bug_table:
CREATE TABLE `mantis_bug_table` (
`id` int(10) UNSIGNED NOT NULL,
`project_id` int(10) UNSIGNED NOT NULL DEFAULT '0',
`reporter_id` int(10) UNSIGNED NOT NULL DEFAULT '0',
`handler_id` int(10) UNSIGNED NOT NULL DEFAULT '0',
`duplicate_id` int(10) UNSIGNED NOT NULL DEFAULT '0',
`priority` smallint(6) NOT NULL DEFAULT '30',
`severity` smallint(6) NOT NULL DEFAULT '50',
`reproducibility` smallint(6) NOT NULL DEFAULT '10',
`status` smallint(6) NOT NULL DEFAULT '10',
`resolution` smallint(6) NOT NULL DEFAULT '10',
`projection` smallint(6) NOT NULL DEFAULT '10',
`category` varchar(64) NOT NULL DEFAULT '',
`date_submitted` datetime NOT NULL DEFAULT '1970-01-01 00:00:01',
`last_updated` datetime NOT NULL DEFAULT '1970-01-01 00:00:01',
`eta` smallint(6) NOT NULL DEFAULT '10',
`bug_text_id` int(10) UNSIGNED NOT NULL DEFAULT '0',
`os` varchar(32) NOT NULL DEFAULT '',
`os_build` varchar(32) NOT NULL DEFAULT '',
`platform` varchar(32) NOT NULL DEFAULT '',
`version` varchar(64) NOT NULL DEFAULT '',
`fixed_in_version` varchar(64) NOT NULL DEFAULT '',
`build` varchar(32) NOT NULL DEFAULT '',
`profile_id` int(10) UNSIGNED NOT NULL DEFAULT '0',
`view_state` smallint(6) NOT NULL DEFAULT '10',
`summary` varchar(128) NOT NULL DEFAULT '',
`sponsorship_total` int(11) NOT NULL DEFAULT '0',
`sticky` tinyint(4) NOT NULL DEFAULT '0',
`target_version` varchar(64) NOT NULL DEFAULT ''
) ENGINE=MyISAM DEFAULT CHARSET=utf8;
Can you help me with SQL's to convert, if this is whats needs to be fixed.
Current schema for mantis_bug_table:
CREATE TABLE `mantis_bug_table` (
`id` int(10) UNSIGNED NOT NULL,
`project_id` int(10) UNSIGNED NOT NULL DEFAULT '0',
`reporter_id` int(10) UNSIGNED NOT NULL DEFAULT '0',
`handler_id` int(10) UNSIGNED NOT NULL DEFAULT '0',
`duplicate_id` int(10) UNSIGNED NOT NULL DEFAULT '0',
`priority` smallint(6) NOT NULL DEFAULT '30',
`severity` smallint(6) NOT NULL DEFAULT '50',
`reproducibility` smallint(6) NOT NULL DEFAULT '10',
`status` smallint(6) NOT NULL DEFAULT '10',
`resolution` smallint(6) NOT NULL DEFAULT '10',
`projection` smallint(6) NOT NULL DEFAULT '10',
`category` varchar(64) NOT NULL DEFAULT '',
`date_submitted` datetime NOT NULL DEFAULT '1970-01-01 00:00:01',
`last_updated` datetime NOT NULL DEFAULT '1970-01-01 00:00:01',
`eta` smallint(6) NOT NULL DEFAULT '10',
`bug_text_id` int(10) UNSIGNED NOT NULL DEFAULT '0',
`os` varchar(32) NOT NULL DEFAULT '',
`os_build` varchar(32) NOT NULL DEFAULT '',
`platform` varchar(32) NOT NULL DEFAULT '',
`version` varchar(64) NOT NULL DEFAULT '',
`fixed_in_version` varchar(64) NOT NULL DEFAULT '',
`build` varchar(32) NOT NULL DEFAULT '',
`profile_id` int(10) UNSIGNED NOT NULL DEFAULT '0',
`view_state` smallint(6) NOT NULL DEFAULT '10',
`summary` varchar(128) NOT NULL DEFAULT '',
`sponsorship_total` int(11) NOT NULL DEFAULT '0',
`sticky` tinyint(4) NOT NULL DEFAULT '0',
`target_version` varchar(64) NOT NULL DEFAULT ''
) ENGINE=MyISAM DEFAULT CHARSET=utf8;
Re: Date not displayed after upgrade from 1.1.6 to 1.3.18
Dates should have been migrated to integer by the upgrade script.
https://github.com/mantisbt/mantisbt/bl ... a.php#L582
https://github.com/mantisbt/mantisbt/bl ... a.php#L582
Re: Date not displayed after upgrade from 1.1.6 to 1.3.18
Hi Atrol,
Thanks for your reply, for some reason it wasn't, i'll handle this manually, no problem, and will do a table by table check to confirm the schema for all of them.
And what about the newline issue, that appears ok in 1.1.6 and not in 1.3.18, do you have any suggestion?
Thanks for your reply, for some reason it wasn't, i'll handle this manually, no problem, and will do a table by table check to confirm the schema for all of them.
And what about the newline issue, that appears ok in 1.1.6 and not in 1.3.18, do you have any suggestion?
Re: Date not displayed after upgrade from 1.1.6 to 1.3.18
Thank you!!
There was no table!!!
Fixed, copy from the old db.
Sometimes i have this error when i click "view issues", what can it be?
[update]
when i click "view issues" or then i click the "ID" column to order,
SYSTEM ERROR
'Argument 1 passed to filter_ensure_valid_filter() must be of the type array, null given, called in /home/hosting/decimal.pt/bugs/core/filter_api.php on line 869 and defined' in '/home/hosting/decimal.pt/bugs/core/filter_api.php' line 486
Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.
There was no table!!!
Fixed, copy from the old db.
Sometimes i have this error when i click "view issues", what can it be?
[update]
when i click "view issues" or then i click the "ID" column to order,
SYSTEM ERROR
'Argument 1 passed to filter_ensure_valid_filter() must be of the type array, null given, called in /home/hosting/decimal.pt/bugs/core/filter_api.php on line 869 and defined' in '/home/hosting/decimal.pt/bugs/core/filter_api.php' line 486
Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.
Re: Date not displayed after upgrade from 1.1.6 to 1.3.18
You will get problem after problem as there is obviously something complete wrong with your upgrade.
It seems you never run the upgrade script or it stopped because of errors.
Check the the result of
Code: Select all
SELECT value FROM mantis_config_table WHERE config_id = 'database_version';
If not, start from scratch using a copy of your 1.1 database.
Re: Date not displayed after upgrade from 1.1.6 to 1.3.18
I did a clean install of 1.3.18 and i'm comparing and adjusting every table/field manually, seems that my 1.1.6 install had some db problems also and never noticed it, it has about 11 years!!
Some fields were in wrong order also, not problematic as mantis seems to be specifying the fields, but i took the oportunity to make everything right.
I'll let you know the result after confirming the db schema,
Some fields were in wrong order also, not problematic as mantis seems to be specifying the fields, but i took the oportunity to make everything right.
I'll let you know the result after confirming the db schema,
Re: Date not displayed after upgrade from 1.1.6 to 1.3.18
Changing the database schema is not enough.
You have also to migrate data the same way it's done by the upgrade script.
You have also to migrate data the same way it's done by the upgrade script.
Re: Date not displayed after upgrade from 1.1.6 to 1.3.18
Atrol,
db version, 209.
My install even on 1.1.6 has some issue i'm aware of that, i'm just asking for help to have it all good.
I confirmed all tables, fields and converted all date fields with the unix_timestamp, everything's fine so far, dates are show'n ok.
Till now i just have that issue, when i try to order in the columns, where can i search for? maybe some parameter in the defaults or config_inc.php ?
db version, 209.
My install even on 1.1.6 has some issue i'm aware of that, i'm just asking for help to have it all good.
I confirmed all tables, fields and converted all date fields with the unix_timestamp, everything's fine so far, dates are show'n ok.
Till now i just have that issue, when i try to order in the columns, where can i search for? maybe some parameter in the defaults or config_inc.php ?
Re: Date not displayed after upgrade from 1.1.6 to 1.3.18
As told before, you will encounter even more problems as adjusting the schema is not enough.
In this case, I assume that the problem is caused by filter data (mantis_filters_table) which has not been migrated.
You could delete your filters or try to reimplement what the upgrade script would have done.
https://github.com/mantisbt/mantisbt/bl ... i.php#L430
Re: Date not displayed after upgrade from 1.1.6 to 1.3.18
Got it, perfect now!!
Thanks Atrol, If i need anything else I'll let you know.
Jorge,
Thanks Atrol, If i need anything else I'll let you know.
Jorge,
Re: Date not displayed after upgrade from 1.1.6 to 1.3.18
Atrol,
Don't get me wrong, Personally don't like the design of 2.x
But, this is me, i tried it in a clean install and so, it's cute, but i preffer the 1.x design of Mantis.
As i said, it's *just* my personal opinion,
Don't get me wrong, Personally don't like the design of 2.x
But, this is me, i tried it in a clean install and so, it's cute, but i preffer the 1.x design of Mantis.
As i said, it's *just* my personal opinion,
Re: Date not displayed after upgrade from 1.1.6 to 1.3.18
Understand.
I found that especially users who worked a very long time with the old design don't like the new design that much at first sight (including myself).
After working a while with the new design (and some of the new / improved functionalities) most of the users don't want to go back any longer.
What's your most annoying design change in 2.x?
Keep in mind that 1.3.x will just get updates for major security issues.
I found that especially users who worked a very long time with the old design don't like the new design that much at first sight (including myself).
After working a while with the new design (and some of the new / improved functionalities) most of the users don't want to go back any longer.
What's your most annoying design change in 2.x?
Keep in mind that 1.3.x will just get updates for major security issues.