Patch #2265


Revert a specific plugin migrations

Added by Jean-Baptiste Barth almost 15 years ago. Updated about 14 years ago.

Plugin API
Target version:
Start date:
Due date:
% Done:


Estimated time:


There's a topic on the forum here where the person asks how to revert plugin migrations easily. I think it would be useful if people want to try plugins and then uninstall it.

Engines seems to be able to do that but I didn't managed to make it work. Anyway, I think it's the same as the task to migrate all plugins : Engines know how to do this but a redmine specific task has been added. So I suggest to add a redmine specific task to migrate just one plugin.

I leave a patch in attachment, which is nearly a copy/paste from Engines db:migrate:plugin task.

$ rake db:migrate_plugin NAME=my_plugin : migrate to last version of "my_plugin"
$ rake db:migrate_plugin NAME=my_plugin VERSION=X : migrate to version X (and 0 when you uninstall)

Any opinion about that ?


migrate_plugins.diff (830 Bytes) migrate_plugins.diff Jean-Baptiste Barth, 2008-12-02 22:47
engines.rake.diff (587 Bytes) engines.rake.diff Thomas Löber, 2009-02-20 16:30

Related issues

Related to Redmine - Feature #3597: Rails 2.3.4 supportClosedEric Davis2009-07-082009-09-13

Has duplicate Redmine - Feature #3329: New rake test: Allow migrating plugin to a specific versionClosedEric Davis2009-05-10

Actions #1

Updated by Jean-Baptiste Barth almost 15 years ago

  • File deleted (migrate_plugins.diff)
Actions #2

Updated by Jean-Baptiste Barth almost 15 years ago

My proposal wasn't very beautiful.. Sorry for the double post.

Actions #3

Updated by Markus Knittig almost 15 years ago

I have also failed to get the Engines uninstall routine work.

Actions #4

Updated by Stephanie Collett almost 15 years ago

+1 This will be handy when experimenting with plugins.

Actions #5

Updated by Eric Davis almost 15 years ago

  • Status changed from New to 7
  • Assignee set to Eric Davis

Great workaround. I'd like fix this in Engines and submit a patch to the Engines project. I just tried to migrate a plugin on a separate Engines project ( and it had the same error.

Actions #6

Updated by Thomas Löber almost 15 years ago

As the Engines plugin is part of Redmine's source tree shoudn't we fix the error there? (See patch.)

Actions #7

Updated by Benjamin Baroukh over 14 years ago

Any news about an integration into Redmine core ?

Actions #8

Updated by Javier Barroso over 14 years ago

I tried uninstall budget plugin, but table 'deliverates' is still on db. did I lose something ?


Actions #9

Updated by Eric Davis about 14 years ago

For the Rails 2.3.4 upgrade (#3597) I had to upgrade Engines which will fix this bug. I'll close it once #3597 is ready.

Actions #10

Updated by Eric Davis about 14 years ago

  • Status changed from 7 to Closed
  • Target version set to 0.9.0
  • % Done changed from 0 to 100

This should be fixed in the latest Rails Engines upgrade, r2887.


Also available in: Atom PDF