Migration from InstantMantis to current (1.2.3)
Moderators: Developer, Contributor
Migration from InstantMantis to current (1.2.3)
Hello,
I installed the current version (1.2.3) on a clean web server and I want to get the data (only the bugs) from my old InstantMantis.
The InstantMantis seems to be a 1.1.1 (regarding the changelog)
Is there a good way to do that ?
I installed the current version (1.2.3) on a clean web server and I want to get the data (only the bugs) from my old InstantMantis.
The InstantMantis seems to be a 1.1.1 (regarding the changelog)
Is there a good way to do that ?
Re: Migration from InstantMantis to current (1.2.3)
Way 1:
- Update your Instant MantisBT to 1.2.3
- Export your database
- Import your database on new server and use your fresh installation
Way 2:
- Export your database
- Import your database on new server (if not needed remove the database of you fresh installation)
- Update to 1.2.3 on new server
- Update your Instant MantisBT to 1.2.3
- Export your database
- Import your database on new server and use your fresh installation
Way 2:
- Export your database
- Import your database on new server (if not needed remove the database of you fresh installation)
- Update to 1.2.3 on new server
Re: Migration from InstantMantis to current (1.2.3)
Forget what I said about "only the bugs".
I've just tried to upgrade, but IM run with PHP 4.4.2 and it say I must have PHP 5.1.
Maybe I can force the database upgrade ? or I really need to install PHP 5.1 ?
I've just tried to upgrade, but IM run with PHP 4.4.2 and it say I must have PHP 5.1.
Maybe I can force the database upgrade ? or I really need to install PHP 5.1 ?
Re: Migration from InstantMantis to current (1.2.3)
Of course you can force it to run by disabling the check in source code.Y-Master wrote: Maybe I can force the database upgrade ? or I really need to install PHP 5.1 ?
I never tried, if the installation/upgrading process of 1.2.x would work with PHP 4.x
Seems that Way 2 is the better one.
Re: Migration from InstantMantis to current (1.2.3)
I'm trying the Way 2, but on the check.php I have :
Code: Select all
APPLICATION ERROR #401
Database query failed. Error received from database was #1146: Table 'mantisbt.mantis_plugin_table' doesn't exist for the query: SELECT COUNT(*) FROM mantis_plugin_table WHERE basename=?.
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: Migration from InstantMantis to current (1.2.3)
The table mantis_plugin_table should exist after upgrading by running admin/install.php
I think there is some confusing documentation around this
I think there is some confusing documentation around this
Re: Migration from InstantMantis to current (1.2.3)
Ok the upgrade suceeded.
Thanks a lot for your help
Thanks a lot for your help
-
- Posts: 9
- Joined: 16 May 2013, 10:14
Re: Migration from InstantMantis to current (1.2.3)
Hi All,
Just want to ask how to export database from InstantMantis-1.1.1 ?
Thank you.
Just want to ask how to export database from InstantMantis-1.1.1 ?
Thank you.
Re: Migration from InstantMantis to current (1.2.3)
I never used InstantMantis and I don't know what is excactly installed with it.
Database export should be something like
mysqldump -u<username> -p<password> <database name> > exportmantis.sql
Database export should be something like
mysqldump -u<username> -p<password> <database name> > exportmantis.sql
-
- Posts: 9
- Joined: 16 May 2013, 10:14
Re: Migration from InstantMantis to current (1.2.3)
Hi Atrol,
Thanks for the reply, i managed to migrate it. i just put down my instant mantis for maintenance then copied the old database to the new setup of new version of mantis.
Then i upgraded the database and it worked.
Thanks for the reply, i managed to migrate it. i just put down my instant mantis for maintenance then copied the old database to the new setup of new version of mantis.
Then i upgraded the database and it worked.