Patch #2265
closed
Revert a specific plugin migrations
Added by Jean-Baptiste Barth over 15 years ago.
Updated almost 15 years ago.
Description
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.
Usage:
$ 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 ?
Files
- File deleted (
migrate_plugins.diff)
My proposal wasn't very beautiful.. Sorry for the double post.
+1
I have also failed to get the Engines uninstall routine work.
+1 This will be handy when experimenting with plugins.
- Status changed from New to 7
- Assignee set to Eric Davis
As the Engines plugin is part of Redmine's source tree shoudn't we fix the error there? (See patch.)
Any news about an integration into Redmine core ?
I tried uninstall budget plugin, but table 'deliverates' is still on db. did I lose something ?
Thanks
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.
- 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