How to Enable Disabled Plugins in JIRA

[Sathish Venkat]

Recently I disabled some of the jira plugins using the plugins console of JIRA.

I tried re-enabling those but it seems the enable button doesnt work.It still remains disabled.

I tried removing those plugins from file system and restarted JIRA,those plugins were gone from the plugins list.

I re deployed those plugins and restarted JIRA.

To my surprise those plugins were in disabled state again.

Could not understand how I can enable those and not sure why it is still in disabled state even after remopving and redeploying.

Am using JIRA 4.4

Any help on this is appreciated.

Regards

[childnode]

old question but also outdated answers, so here is a JIRA 7 answer to the problem:

perhaps someone has a similar problem that he has to enable / disable plugins while JIRA is shut down:

Atlassian JIRA - Plugins - Quick Edit Plugin  : com.atlassian.jira.jira-quick-edit-plugin
              Version                                       : 3.0.18
              Status                                        : disabled
              Vendor                                        : Atlassian
              Description                                   : This is the com.atlassian.jira:jira-quick-edit-plugin plugin for Atlassian JIRA.

...

***************************************************************************************************************************************************************
    The following plugins are required by JIRA, but have not been started: Atlassian JIRA - Plugins - Quick Edit Plugin (com.atlassian.jira.jira-quick-edit-plugin)
    ***************************************************************************************************************************************************************

so, here we go:

tl;dr

the pluginstate has it's own table, called ... pluginstate *wohoo*

Example for an postgreSQL DB:

jiradb=# UPDATE pluginstate SET pluginenabled=true WHERE pluginkey='com.atlassian.jira.jira-quick-edit-plugin';
UPDATE 1

jiradb=# select * from pluginstate;
                              pluginkey                               | pluginenabled 
----------------------------------------------------------------------+---------------
 com.atlassian.jira.welcome.jira-welcome-plugin:show-whats-new-flag   | true
 com.atlassian.jira.whatsnew.jira-whatsnew-plugin:show-whats-new-flag | true
 jira.plugin.minyaa.boot                                              | false
 jira.plugin.minyaa.core                                              | false
 jira.plugin.minyaa.core.gadget                                       | false
 jira.plugin.minyaa.projects                                          | false
 jira.plugin.minyaa.spread                                            | false
 jira.plugin.minyaa.time                                              | false
 jira.plugin.minyaa.time.gadget                                       | false
 jira.plugin.minyaa.time.reports                                      | false
 jira.plugin.minyaa.tools                                             | false
 jira.plugin.minyaa.workflows                                         | false
 jira.plugin.minyaa.workflows.designer                                | false
 com.atlassian.jirawallboard.atlassian-wallboard-plugin               | true
 is.origo.jira.tempo-plugin                                           | false
 com.atlassian.jira-core-project-templates                            | true
 com.atlassian.support.stp                                            | false
 com.atlassian.jira.jira-quick-edit-plugin                            | true
(18 rows)

[Leonid Zvyahintsev]

if you use HSQL find jiradb.script and remove all lines like:

INSERT INTO PROPERTYENTRY VALUES(13912,'jira.properties',1,'jira.plugin.state-.crowd-rest-plugin',5)

INSERT INTO PROPERTYENTRY VALUES(13913,'jira.properties',1,'jira.plugin.state-.crowd-rest-application-management',5)

INSERT INTO PROPERTYENTRY VALUES(13914,'jira.properties',1,'jira.plugin.state-.crowd.system.passwordencoders',5)

This will enable all disabled plugins.

Worked for me in Jira 4.3.3

[Jobin Kuruvilla [Adaptavist]]

Are you seeing any error in the logs when you click on enable?

[Sathish Venkat]

Yes I checked the logs and could not find any exception or activity in it when I click enable.

[Jobin Kuruvilla [Adaptavist]]

Not sure what is happening but I would also try it from a different browser.

[Sathish Venkat]

Tried that too... not working

[Andy Brook [Plugin People]]

which logs are you checking? plugin disablement usually means something died, try tailing the logs/catalina.out file, redeploy your plugin, what happens then?

[Sathish Venkat]

Thanks andy for your interest.

Yes am checking the catalina.out file. I removed the plugins from installed-plugins folder and restarted it.The plugins which I removed were not appearing in the list of plugins.

When I redeployed the plugins again and restarted jira.It were listed in the plugins but disabled?

Does Jira makes any db entry for disabled plugins which is not getting reverted and hence it is disabled again?

Regards

[Nic Brough -Adaptavist-]

Yes, I've seen it do that a few times - I think what happens is when you install a plugin, it stores config information for them when they first run. At the very least, the modules within the plugin, and an "enabled" flag are stored. On subsequent starts, it tries to start any module in the list that is enabled. If it runs into problems, it flags them as disabled. These settings persist, even if you remove the plugin jar file (which will, of course, cause a problem which would cause it to flag the plugin as disabled), because the database has no way of knowing that you've physically removed the files. If you then put the plugin back, although it can find it again, it's got the flag set as "disabled" already and doesn't try to reload them. So you have to go into the plugins page to tell it to try to load them again.