-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to uninstall in Redmine 2.1.0 #92
Comments
Check this #75 |
Hi Mani, thanks, but I already checked that out to no avail unfortunately. Thanks anyways! |
+1 for that matter! Uninstall also not possible with RedMine 2.2 (same error). |
Has anyone found a way how to fix this particular issue? |
Any updates? I still can't uninstall and it prevents me from using other plugins. Please help? Redmine 2.2 here. |
+1 on updates. This is a bit of a problem for us sadly :( |
I had the same problem, uninstalling Scrumbler from Redmine using migrate VERSION=0 was not possible and physically removing the Scrumbler directory resulted in the 500 error leaving Redmine unusable. I managed to resolve this with a temporary fix of Redmine's plugin code: When Redmine registers plugins it uses the plugin's id, see plugin.rb: When it then tries to find a registered plugin it uses id.to_sym, see plugin.rb: A puts() of id and id.to_sym both returned 'redmine_scrumbler'
This worked ok and after that i could remove the Scrumbler directory from plugins without Redmine giving a 500 page. Finally i removed the temporary fix in plugin.rb ( And now Redmine (2.2.2 by the way) seems to work OK. |
Thank you, JeroenValkonet !! |
Hi,
have been trying to get this plugin to work in RM210 without luck. Now I would like to remove it, but that seems an problem too..
rake db:migrate:plugin NAME=redmine_scrumbler VERSION=0 RAILS_ENV=production
or:
rake redmine:plugins:migrate NAME=redmine_scrumbler VERSION=0 RAILS_ENV=production
Results in:
Plugin redmine_scrumbler was not found.
... leaving me with a buggy redmine.
Any suggestions?
The text was updated successfully, but these errors were encountered: