Patch #2265
closedRevert a specific plugin migrations
100%
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
Related issues
Updated by Jean-Baptiste Barth over 15 years ago
- File deleted (
migrate_plugins.diff)
Updated by Jean-Baptiste Barth over 15 years ago
- File migrate_plugins.diff migrate_plugins.diff added
My proposal wasn't very beautiful.. Sorry for the double post.
Updated by Markus Knittig over 15 years ago
+1
I have also failed to get the Engines uninstall routine work.
Updated by Stephanie Collett over 15 years ago
+1 This will be handy when experimenting with plugins.
Updated by Eric Davis over 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 (http://github.com/courtenay/tentacle/tree/master) and it had the same error.
Updated by Thomas Löber over 15 years ago
- File engines.rake.diff engines.rake.diff added
As the Engines plugin is part of Redmine's source tree shoudn't we fix the error there? (See patch.)
Updated by Benjamin Baroukh over 15 years ago
Any news about an integration into Redmine core ?
Updated by Javier Barroso over 15 years ago
I tried uninstall budget plugin, but table 'deliverates' is still on db. did I lose something ?
Thanks
Updated by Eric Davis almost 15 years ago
Updated by Eric Davis almost 15 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.