Upgrading to 1.2.0 does not work!

[bbking]

Hello @all,

I upgraded to 1.2.0 (XP, PHP5.3, MySQL 5.1) with executing

admin/upgrade_unattended.php which throw a lot of warnings but no errors at me.

Then called

admin/install.php which went fine.

Now, when I log in and choose "My view" I only get a red error message:

APPLICATION ERROR #1502

Category not found.


Any ideas? The upgrade notes are missing from the docs, by the way.

Shall I post a bug about this?

Thanks
BBKing

[atrol]

I didn't check whether it makes a difference but if I remember right I made my update just by starting admin/install.php
I had no problems with this when upgrading from 1.1.6

[kevindrys]

I just upgraded from 1.1.8 to 1.2.0. The upgrade instructions say to move your configuration files into the new 1.2.0 directory. I did this and ran install.php and kept getting errors regarding a Mantis plug-in. Evidently the new version does not use a plug-in that the old version still referenced. Fixed this by using the new 1.2.0 configuration files and just tweaking to my preferences. Then install.php ran and I was able to update the database.

However, now we're seeing a problem where a new ticket with attachments is fine until you move the ticket to a different project. Then the attachment is missing!

[atrol]

However, now we're seeing a problem where a new ticket with attachments is fine until you move the ticket to a different project. Then the attachment is missing!

Check whether someone entered a bug report for this. If not, please enter a new issue for this.

[jchoover]

On behalf of Kevin, I did some investigation with our install and came up with the following: http://www.mantisbt.org/bugs/view.php?id=11687

[atrol]

thx jchoover for entering the issue, seems this is an old bug. Just today I had the same problem with one of my older (1.1.6) installations.

[jchoover]

For what it's worth, in our specific configuration we configured a project as the "incoming" project. When tickets are analyzed by a project lead, they are then moved to a different project based on version requested.

Our workaround was to change the configuration for the absolute default folder to point to the same folder as the "incoming" project. While the attachments don't get moved, they are still visible once the ticket is moved to a different project due to the means in which file paths are resolved. (Changing this after you notice the bug immediately fixes the mantis instance assuming you don't move tickets between sub projects.)