...
Please test this plug-in with a test task on your translate5 instance. If you getting wired DB errors on re-importing restoring your test task, this is because your DB structure was not correctly updated. Perhaps you have dismissed some minor DB updates.
Also test all features in your test task (MQM, statistics, termtagging etc) and check if all changes are restored after restoring the whole task.
Re-import of the archive
Restore your archive
Currently restoring an Currently the re-import of the archive has to be done manually.
...
Since all numeric IDs are stored in the archived database files, the archive can only be re-imported restored in the same instance of translate5, where the task has been deleted before, or in a new translate5 instance with a empty database structure!
...
If the both entries with the highest IDs are the same in the structure is identical.
Start
...
restore if structure is unchanged:
If the DB and data dump structure is the same, and you are on the same DB instance (or a fresh one), the task can simply be restored by changing to the db_data directory:
...
And thats it. The task should be available again.
...
Restore if structure has changed:
This is possible, but a little bit more complicated:
- Call the install and update script to ensure that your instance is up to date.
- Make a database clone of the instance where you want to re-import restore the task.
- Switch with your instance to the database clone by changing the DB name in "installation.ini". All the following steps must be done in the DB clone!
- Apply all SQL files found in the "db_structure" directory to your cloned DB. All tables are recreated now empty with the old structure. (This is because you have to do it on a cloned DB!)
- Apply all SQL files found in the "db_data" directory to your cloned DB.
- Call the install and update script (or the database updater if no script available) so that all missing DB updates are getting applied. No you have migrated your task from old DB structure to the new one.
- Delete the old archive ZIP.
- Export your task again from your cloned DB.
- Switch your system back to your production DB.
- Now you can simply re-import restore the task as described above for unchanged DB structures.
...