ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Forums » Discuss »

De-activating Plugins

Added by Harald Klimach at 2012-04-13 05:21 am

In Chiliproject 3 I now ran into the problem, that it is not possible to create a project in my upgraded installation from chiliproject 2.
I have the suspicion, that this is due to installed plugins, thus I guess, I have to deactivate them. And narrow the problem down.
Now I do not too regularily play around with that stuff, and always forget, what is actually needed to do that.
It would be nice if this could be documented in the Plugin-Section. Is it sufficient to move / rename the directory of he plugin?
What happens to the Database additions from the plugin?

Thanks!


Replies (3)

RE: De-activating Plugins - Added by Felix Schäfer at 2012-04-13 06:25 am

To deactivate a plugin: "remove" it from the vendor/plugins directory, either by moving it away from there or by removing access rights for the chiliproject process (I personally just chmod 000 some_plugin). To deinstall a plugin from the DB, run rake db:migrate:plugin NAME=some_plugin VERSION=0.

Regarding the docs, feel free to extend those in the Wiki :-)

RE: De-activating Plugins - Added by Harald Klimach at 2012-04-13 07:58 am

Thanks a lot, I added this to the wiki: Plugin_Uninstall.

RE: De-activating Plugins - Added by Felix Schäfer at 2012-04-21 01:25 pm

I hate to have to say this, but we're getting too much spam here, closing.

(1-3/3)