What happens when every Confluence developer adds their macro to the "Featured Macros" section in the editor?

[David at David Simpson Apps]

Thanks to @Ryan Thomas for posting his Pimp my Confluence 4 plugin slide desk from Atlascamp, but...

Here's my local system with a a pile of macros added in the system.editor.featured.macros.default section. You guessed it, the dropdown drops off the bottom of the screen.

The obvious answer is that you can disable web-items for each plugin in the plugin configuration screen for that plugin, but that's not exactly user friendly -- Its very unpleasant in fact.

Would it be better for Atlassian to produce single location to perform this operation?

Maybe have a "Configure Featured Macros" screen where an admin can choose which macros are displayed and which are not?

Edit: More importantly, this means that the "Other Macros" option is now hidden off the bottom of the screen preventing access to that menu item.

[David Peterson]

In the meantime you could use the Menu Manager plugin. We haven't officially released the 4.0 compatible version, but I'm pretty sure the trunk works in 4.0. It groups items by location, and allows you to switch individual items on and off. Would work as a holdover until Atlassian adds something more 'macro-specific'. Latest build is here:

https://studio.plugins.atlassian.com/builds/browse/CNFMENUS-TRUNK-10/artifact

Hope that helps!

[Laura Kolker]

I think that things falling off the bottom of the screen (in one form or another) is the biggest UI hurdle I've run into.

[David at David Simpson Apps]

Done: https://jira.atlassian.com/browse/CONF-23368

[Shannon Krebs]

That would be a worth while improvement but probably not a high priority for Atlassian since the workaround you describe is available. I suggest creating a jira issue for it so it can start acumulating votes.