Sorry but I was not able to reproduce your problem.

I installed a fresh 1.1.7, created a few test issues, ran the upgrade. All the history dates are migrated OK, and I don't get empty dates when updating issues.

Please additional information that allow to reproduce the issue.

I think the only way to show you that is to give you the code and the DB (more than 12Go)...
I've resolved this problem changing a few part of the source code, forcing to display/save the date from field "date_modified_int" (unix timestamp date) and not from "date_modified" (windows date).
Maybe this problem is coming from our Regional Culture Setting...

Xavier,

The field 'date_modified_int' should not exist in your database if the upgrade process ran successfully.

It is a temporary field, which is created by the installer, to manage the conversion of dates into the new (unix) format.

Considering the size of your database, it is possible that the upgrade did not execute or complete properly (maybe due to timeout)

Can you please confirm, what is your current schema version (see Manage overview page) - should be 183 for 1.2.11

Thank you for your feedback,
I'm on schema 113.
If you have any idea how to resolve that and have a stable version, I'm in :-)

Another solution for us is to install a fresh and new version of mantis and integrate a link of the current mantis (in readonly) with all the history...
But I'm not sure that my team will be agree with that.

you can change manually type of field date_modified from date to int, and copy data from date_modified_int to date_modified with only 2 sql requests ;)

Right Animal Killer, it can be down like donw :-)
I will make those changes...
Thanks

PS:
Maybe they will have many others problem like that if the installation script end not correctly...
I cross my fingers

Actually I strongly recommend NOT to attempt a manual update of your database as LapinKiller said.

If you're on schema version 113, there are many other schema upgrade steps which are missing in your setup, and you will be facing other problems down the line, not to mention that you risk breaking the upgradability of your system.

I think you should try to do a clean upgrade from scratch. Make sure to note down and report any error messages that may occur. If you get a timeout, try increasing the relevant PHP settings to avoid that, and restart the upgrade. I believe it will resume from where it left off (see 0012735).

Hi,
Thank Dregad, I will test that and give you a feedback when it's done.
Regards

xavier_de_potter,

You did not provide any feedback; I am therefore resolving this issue as "no change required".

Feel free to reopen the issue at a later time and provide the requested information.

Hi,
I was in holliday for 2 weeks :-)
I planned to do that this week and I will give feedback after that.
Regards

Sorry,
I don't understand very well and didn't find any documentation about that.
Where does I need to write that? In wich file?
mod - admin/install_functions.php
I'm not a "Linuxien", so could you explain me how and where execute this query?
Regards,
Xavier

Xavier

There should not be anything to do, change or write. In particular, do not touch anything in admin/install_functions.php.

Timeouts during date conversions are a known problem on large databases (see 0012601) but the code was modified so that it can resume from the point of failure when restarted (see 0012735).

Therefore I suggest you try again the complete upgrade from scratch (i.e. using a fresh copy of your 1.1.7 database). If the installation/upgrade process times out, just restart it as many times as needed, until normal, successful completion. At the end your schema version should be 183.

I was asking you to note down errors and messages, as this is not something I can reproduce here. This could help in better documenting the upgrade process.

Hi,
I've execute the intallation and now I have the good schema version.
I've also seen the message "installation complete successful"
After a few test, seem that all my bugs have disappeard!
Thanks for all and the support.
I will push my boss to made a donation for all you work and I'm sure he will do it.
Thanks for all!
Regards,
Xavier

Glad I could help, and thanks for thinking of donating.

I am still interested in the actual errors you received while upgrading (screenshots, messages, etc), to better document this process for other people who might experience the same problems.

Ok, Tonight, I replicate the same steps but this time it's for the mantis on our Production server.
I will document all my steps and join it to this Issue.

Here is the basic tutoriel to resolve that
Regards

Merci Xavier.

EDIT:
Looking at the doc you provided, it does not match with the error that you reported earlier with failure on date conversion; the adding of user_id column in mantis_bug_file_table is schema version 173, while you mentioned having an issue in schema version 113 before.

Did you get the same error at that time ?

Yes, it was the error (on test and production system)