upgrade 1.x to 2.5.1

What means 1.x exactly?

Is there are column text in table mantis_custom_field_string_tablein the original database before you start the upgrade script?

version 1.2.19 old

i bakup all data and sql

1 i remove old BT
2 i uploaded new verion
3 i run installer
4 done

DB sccren

Unbenannt.PNG (197,558 bytes)   

Unbenannt.PNG (197,558 bytes)   

*+ i upload my old config

There was no text field in 1.2.19, this has been introduced in 1.3.0-beta.1, see 0006626.

Did you patch 1.2.19 to use the new custom field type in 1.2.x?

no

i use patch 1.2.19 and update to 2.5.1

and have sql error last post

I can just repeat what I wrote before:
There was no text field in 1.2.19, this has been introduced in 1.3.0-beta.1, see 0006626.

This means that someone changed your 1.2.19 database (added text field), which is causing the problem when trying to upgrade.

You have to check, if there is any data in the text field.
You could remove the database column, if there is no data in it.
After that, the upgrade should run without the mentioned error.

In case there is data: Change file admin/schema.php
from

$g_upgrade[185] = array( 'AddColumnSQL', array( db_get_table( 'custom_field_string' ), "
    text                    XL      NULL DEFAULT NULL" ) );

to

$g_upgrade[185] = null;

hermann901,

This is not a bug or feature request for MantisBT (you are asking for help on how to deal with problems that you introduced yourself by changing the original database schema). I am therefore resolving this issue as "no change required".

Please use the forums to get support on customizing and using MantisBT (refer to http://www.mantisbt.org/support.php for links and further details).

i change it and next error
ALTER TABLE mantis_bug_monitor_table ADD INDEX idx_bug_id (bug_id)
Duplicate key name 'idx_bug_id'

thx i fixed

thx