-
Bug
-
Resolution: Timed out
-
Low
-
None
-
3.1.1
-
2
-
Severity 3 - Minor
-
Attachments Macro is Broken after disabled Attachment Checkout plugin.
Since both plugins (Confluence Attachment plugin (bundled) and attachment checkout plugin) have the same macro (attachments), by default confluence will disable the bundled plugin once you install (enable) the Attachment Checkout plugin.
It will do the same thing when you disable the attachment checkout plugin (Confluence will re-enable the bundled plugin).
However, the attachments macro stops working even though all of the modules of confluence attachment plugin are re-enabled.
Here are the steps to reproduce this problem:
1. Upload attachment checkout plugin.
2. Disable attachment checkout plugin.
3. Verify confluence attachment plugin is enabled.
4. View a wiki page with attachments macro, you will receive a warning
"unknown macro - {attachments}".
Workaround
The workaround is to disable and re-enable Confluence Attachment plugin:
- Go to Administration as a Confluence system administrator
- Click on 'Plugins' in the navigation menu on the left hand side
- On the 'Manage Existing' tab, click the link to 'Show System Plugins'
- Search for 'Attachments', and find the 'Confluence Attachments Plugin'
- Click the 'Disable' button to disable the plugin
- Click the 'Enable' button to reenable the plugin.
[CONFSERVER-18754] Attachments Macro is Broken after disabled attachment checkout plugin due to duplicate {attachments} macro
This is unlikely to be fixed any time soon in Confluence. We don't expect two macros with the same name to be enabled at the same time. It's completely unpredictable which one you'll end up getting when you restart Confluence1.
You should use the workaround mentioned above: disable and reenable the Attachments macro via Plugins in the Confluence administration area.
I'll reword this issue so it reflects the more general problem, and I've also raised a separate ticket for the (unsupported) Attachment Checkout plugin to not use the same macro name: CHKOUT-77.
1Not entirely true. Custom plugins are loaded after bundled plugins, so the Checkout plugin will normally win. For two installed plugins, I believe it depends on the filename of the plugin. If you upgrade a bundled plugin from PAC, it converts the plugin into a custom one and uses an unpredictable filename for the plugin. All this means it's a bad idea to have the same macro name in two plugins, so we'll try to get the Checkout plugin fixed.
Farhad Khan
added a comment - Hi,
I noticed the same issue - our
{attachments}macro is broken after uninstalling the checkout plugin. Is there a fix for this?
Thanks,
Farhad
Farhad Khan
added a comment - Hi,
I noticed the same issue - our
{attachments}
macro is broken after uninstalling the checkout plugin. Is there a fix for this?
Thanks,
Farhad 
Thank you for taking the time to raise, comment or vote on this Bug. We regret to inform you that due to a limited number of reports and based on our current backlog of higher impact issues that we are closing this issue as Timed Out.
If this issue is still impacting you on a recent version please feel free to comment with the affected version. Any further details you may be able to provide regarding reproduction or impact of this issue may help us better address this issue.
Thanks again.
Regards,
Confluence Development