Attachment Actions Plugin Disabled

Attachment Actions Plugin Disabled. The notation says it should never be disabled but on our system it is. Is there any reason for this? If not what should be done?

6 answers

1 accepted

This widget could not be displayed.

Arsenale Lockpoint Plugin disables the Atachment Actions Plugin

This widget could not be displayed.

When you are in your general configuration, you can check out your attachement storage page. did you take a look in there to make sure that everything is looking good? Point to a valid directory etc? Also, do you have permission in the space in question to work with attachments (space admin -> permissions)?

Checked attachments storage and it is ok. Space permissions is not a problem either.

This widget could not be displayed.

Hi Craig,

May I know if this is an upgraded instance? If that is the case, there is a probability that Conflluence disabling this plugin in upgrade process in mistake. In order to fix this you would need to modify the plugin state on the database.

The easiest way is to made the plugin manager state back to default, this means all of your plugins configuration (disabled/enabled) back to default. Please try the following steps to fix this issue

  1. Create a database backup dump for a safety precaution
  2. Shutdown Confluence
  3. Execute this SQL query to Confluence database
  4. UPDATE BANDANA SET BANDANAVALUE = '<map/>' WHERE BANDANAKEY = 'plugin.manager.state.Map';
  5. Restart Confluence

Again, the above steps will make your plugin manager state back tod efault. If you would like to enable only the mentioned plugin, please provide me the result of the SQL query below, so that I could compose the necessary steps for you

SELECT BANDANAVALUE FROM BANDANA WHERE BANDANAKEY='plugin.manager.state.map;

Hope it helps.

Cheers,

Septa Cahyadiputra

Hi Septa:

I would like to enable only the mentioned plugin. Attached is the SQL query

Output from SQL command <tt>SELECT BANDANAVALUE FROM BANDANA WHERE BANDANAKEY='plugin.manager.state.map';</tt> ..


<map>com.atlassian.confluence.whatsnew:show-whats-new-flag true nl.avisi.confluence.plugins.numberedheadings false com.adaptavist.confluence.formMailNG false confluence.extra.userlister false org.swift.confluence.excel false com.stiltsoft.confluence.talk.confluence-talk-plugin false confluence.sections.attachments:edit false confluence.sections.attachments false com.gliffy.integration.confluence:gliffy-attachment-edit-link-newwindow false confluence.extra.impresence2 false com.gliffy.integration.confluence:gliffy-attachment-edit-link false org.swift.confluence.sql false com.atlassian.confluence.extra.officeconnector:editattachmentinworditempathauth false confluence.extra.cipe false com.atlassian.confluence.extra.officeconnector:editattachmentinworditem false confluence.sections.attachments:remove false confluence.extra.masterdetail true confluence.macros.html:html true atlassian-gadgets-shared-3.1.5.jar true com.comalatech.workflow true com.comalatech.workflow:publishedTransformer true </map>

Hi Craig,

It seems that the given result is edited as there supposed to be some tag differentiating each plugin and their boolean. Anyway, I have tried to add the necessary tag into the result and comes up with the following SQL query to solve your issue:

As always, please create a database dump before updating your database directly for safety precaution. Execute the SQL query below in shutdown mode

UPDATE BANDANA SET BANDANAVALUE='&lt;map&gt;
&lt;entry&gt;
	&lt;string&gt;com.atlassian.confluence.whatsnew:show-whats-new-flag&lt;/string&gt;
	&lt;boolean&gt;true&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;nl.avisi.confluence.plugins.numberedheadings&lt;/string&gt;
	&lt;boolean&gt;false&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;com.adaptavist.confluence.formMailNG&lt;/string&gt;
	&lt;boolean&gt;false&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;confluence.extra.userlister&lt;/string&gt;
	&lt;boolean&gt;false&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;org.swift.confluence.excel&lt;/string&gt;
	&lt;boolean&gt;false&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;com.stiltsoft.confluence.talk.confluence-talk-plugin&lt;/string&gt;
	&lt;boolean&gt;false&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;
	confluence.sections.attachments:edit&lt;/string&gt;
	&lt;boolean&gt;false&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;com.gliffy.integration.confluence:gliffy-attachment-edit-link-newwindow&lt;/string&gt;
	&lt;boolean&gt;false&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;confluence.extra.impresence2&lt;/string&gt;
	&lt;boolean&gt;false&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;com.gliffy.integration.confluence:gliffy-attachment-edit-link&lt;/string&gt;
	&lt;boolean&gt;false&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;org.swift.confluence.sql&lt;/string&gt;
	&lt;boolean&gt;false&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;com.atlassian.confluence.extra.officeconnector:editattachmentinworditempathauth&lt;/string&gt;
	&lt;boolean&gt;false&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;confluence.extra.cipe&lt;/string&gt;
	&lt;boolean&gt;false&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;com.atlassian.confluence.extra.officeconnector:editattachmentinworditem&lt;/string&gt;
	&lt;boolean&gt;false&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;confluence.sections.attachments:remove&lt;/string&gt;
	&lt;boolean&gt;false&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;confluence.extra.masterdetail&lt;/string&gt;
	&lt;boolean&gt;true&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;confluence.macros.html:html&lt;/string&gt;
	&lt;boolean&gt;true&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;atlassian-gadgets-shared-3.1.5.jar&lt;/string&gt;
	&lt;boolean&gt;true&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;com.comalatech.workflow&lt;/string&gt;
	&lt;boolean&gt;true&lt;/boolean&gt;
&lt;/entry&gt;
&lt;entry&gt;
	&lt;string&gt;com.comalatech.workflow:publishedTransformer&lt;/string&gt;
	&lt;boolean&gt;true&lt;/boolean&gt;
&lt;/entry&gt;
&lt;/map&gt;' WHERE BANDANAKEY='plugin.manager.state.map';

Restart Confluence afterwards.

The basic idea is to remove the following lines from the previously returned result

&lt;entry&gt;
	&lt;string&gt;confluence.sections.attachments&lt;/string&gt;
	&lt;boolean&gt;false&lt;/boolean&gt;
&lt;/entry&gt;

Hope it helps.

Cheers,

Septa Cahyadiputra

This widget could not be displayed.

The entry is still there, even after the SQL update. Any advice? Is there any reason this plugin should be disabled? Mybe it is superseeded by another plugin such as the "Confluence Attachments Plugin 3.2"?

Here's the current value of the field:

&lt;map&gt;
  &lt;entry&gt;
    &lt;string&gt;com.atlassian.confluence.whatsnew:show-whats-new-flag&lt;/string&gt;
    &lt;boolean&gt;true&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.adaptavist.confluence.formMailNG&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;nl.avisi.confluence.plugins.numberedheadings&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;confluence.extra.userlister&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;org.swift.confluence.excel&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.stiltsoft.confluence.talk.confluence-talk-plugin&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;confluence.sections.attachments:edit&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.gliffy.integration.confluence:gliffy-attachment-edit-link&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.gliffy.integration.confluence:gliffy-attachment-edit-link-newwindow&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;confluence.extra.impresence2&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;confluence.sections.attachments&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;org.swift.confluence.sql&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.atlassian.confluence.extra.officeconnector:editattachmentinworditempathauth&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;confluence.extra.cipe&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.atlassian.confluence.extra.officeconnector:editattachmentinworditem&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;confluence.sections.attachments:remove&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;confluence.extra.masterdetail&lt;/string&gt;
    &lt;boolean&gt;true&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;confluence.macros.html:html&lt;/string&gt;
    &lt;boolean&gt;true&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;atlassian-gadgets-shared-3.1.5.jar&lt;/string&gt;
    &lt;boolean&gt;true&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.comalatech.workflow&lt;/string&gt;
    &lt;boolean&gt;true&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.comalatech.workflow:publishedTransformer&lt;/string&gt;
    &lt;boolean&gt;true&lt;/boolean&gt;
  &lt;/entry&gt;
&lt;/map&gt;

This widget could not be displayed.

Hi Craig,

Seems like I did not clear all of it on my previous query, please try the following on shutdown mode. As always, create a database backup dump before executing this update for safety precaution

UPDATE BANDANA SET BANDANAVALUE ='&lt;map&gt;
  &lt;entry&gt;
    &lt;string&gt;com.atlassian.confluence.whatsnew:show-whats-new-flag&lt;/string&gt;
    &lt;boolean&gt;true&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.adaptavist.confluence.formMailNG&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;nl.avisi.confluence.plugins.numberedheadings&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;confluence.extra.userlister&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;org.swift.confluence.excel&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.stiltsoft.confluence.talk.confluence-talk-plugin&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.gliffy.integration.confluence:gliffy-attachment-edit-link&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.gliffy.integration.confluence:gliffy-attachment-edit-link-newwindow&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;confluence.extra.impresence2&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;org.swift.confluence.sql&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.atlassian.confluence.extra.officeconnector:editattachmentinworditempathauth&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;confluence.extra.cipe&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.atlassian.confluence.extra.officeconnector:editattachmentinworditem&lt;/string&gt;
    &lt;boolean&gt;false&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;confluence.extra.masterdetail&lt;/string&gt;
    &lt;boolean&gt;true&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;confluence.macros.html:html&lt;/string&gt;
    &lt;boolean&gt;true&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;atlassian-gadgets-shared-3.1.5.jar&lt;/string&gt;
    &lt;boolean&gt;true&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.comalatech.workflow&lt;/string&gt;
    &lt;boolean&gt;true&lt;/boolean&gt;
  &lt;/entry&gt;
  &lt;entry&gt;
    &lt;string&gt;com.comalatech.workflow:publishedTransformer&lt;/string&gt;
    &lt;boolean&gt;true&lt;/boolean&gt;
  &lt;/entry&gt;
&lt;/map&gt;' WHERE BANDANAKEY='plugin.manager.state.map';

Restart Confluence afterwards. I don't think this is cause by another plugin since your plugin state manager mentioned that the plugin is indeed in false state which means Confluence won't enable it by default. Since this is a system plugin, enable/disable button won't be available on UPM hence you need to update it trough database manually.

Please try the above query and let me know how it goes.

Cheers,

Septa Cahyadiputra

This widget could not be displayed.

I' ve applied the SQL fix, but it reverted to the original value upon Confluence restart. Maybe this configuration is stored somewhere else. A config file perhaps?

Hi Craig,

Just want to avoid any misunderstanding here. Do you mean your 'plugin.manager.state.map' value in the database revert back to the previous value (unmodified) after Confluence restart?

Plugin enable/disable configuration saved at the mentioned row and it should not revert back upon restart . May I know if you applied the SQL fix during the shutdown mode?

If the SQL fix applied while Confluence is still alive, database cache might rewrite the changes back to the previous value.

Please let me know if the UPDATE applied on shutdown mode.

Cheers,

Septa Cahyadiputra

Can you please describe further what is meant by shutdown mode?

Hi Craig,

You would need to shutdown Confluence before executing the mentioned UPDATE sql query.

Cheers,
Septa Cahyadiputra

Steps followed were:

1. shut down confluence

2. apply changes database

3. check values database (everything ok)

4. startup confluence

5. check plugin manager (Attachment Actions Plugin) still disabled

6. check values database (reverted to orginal values)

Hi Craig,

Consider this our last try before creating a support ticket at our support channel to investigate this thoroughly

  1. Shutdown Confluence instance
  2. Remove the following directories (backup if necessary)
    • <confluence-home>/bundled-plugins
    • <confluence-home>/plugin-cache
    • <confluence-home>/plugins-osgi-cache
    • <confluence-home>/plugins-temp
    • <confluence-home>/bundled-plugins_language
  3. Apply the database fix again
  4. Check values
  5. Startup Confluence
  6. Check if attachment action is still disabled
  7. Check database values

If the issue still persist, please create a support ticket at our support channel so that our support engineer would be able to investigate it throughly for you.

Please attach the result of this SQL query

SELECT * FROM PLUGINDATA;

Hope it helps.

Cheers,
Septa Cahyadiputra


The given query, "SELECT * FROM PLUGINDATA;", results in a 84Mb output file. Compression does not really shrink it either. Is this expected?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 17, 2018 in Confluence

Why start from scratch? Introducing four new templates for Confluence Cloud

Hi my Community friends!  For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...

590 views 7 6
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you