Confluence User Macro Parameters Greyed Out in Version 7.19.24

[Prudhvi Raju Kanithi]

Hello Atlassian Community,

I am encountering an issue with user macros in Confluence version 7.19.24. The parameters for my user macros are greyed out, preventing me from editing them. Here’s what I have tried so far:

      1.    Removed default=false from the macro parameters, but the issue persists.

      2.    Checked for permissions: I have full admin rights and can edit other parts of the macro without issue.

      3.    Validated macro syntax: Ensured that there are no syntax errors in the macro definitions.

      4.    Cleared browser cache and tried accessing Confluence in an incognito window and different browsers.

      5.    Tested with a new page: The issue still occurs on new pages.

      6.    Checked Confluence logs: No relevant errors or warnings found.

      7.    Verified global settings: No apparent restrictions affecting user macros.

      8.    Re-created the macro: Created a new macro with minimal parameters, but the parameters are still greyed out.

Here are a few additional details:

      •     Confluence version: 7.19.24

      •     Browser: Tested on multiple browsers, including incognito mode

      •     Permissions: Full admin rights

Despite these efforts, the parameters remain uneditable. Has anyone else experienced this issue or have any suggestions on how to resolve it?

Any help or insights would be greatly appreciated. Thank you!

[Martin Runge]

Hi @Prudhvi Raju Kanithi.

Welcome to the Atlassian community.

Has this issue been resolved since July 22, 2024? If not, here is a quick checklist of things to investigate: It looks like you’ve done a thorough job of narrowing this down. Since you’ve already cleared the browser cache and validated basic permissions, the “greyed out” behavior in the macro browser usually suggests that the XHTML editor is failing to map the parameter definitions to the UI fields.

1. In some 7.19.x sub-versions, the editor can hang if there is a mismatch in the Macro Body Processing setting. Go to your Macro definition and check the "Body Processing" option. If it is set to "Rendered," try switching it to "Escaped" or "No Macro Body" to see if the parameters become active.
2. Confluence user macros are sensitive to specific naming conventions. Ensure your parameters are not named like reserved words such as name, type, render, or title. Names must match usage exactly and are case-sensitive.
3. Since this persists across new pages and browsers, the issue might be on the server side rather than your client. Confluence maintains an internal cache for plugin and macro metadata. You could ask your System Admin to perform a Plugin Cache Clear while Confluence is stopped.
4. While the Confluence logs are clean, the Browser Developer Tools (F12) might show a different story. Check the Console tab for JavaScript errors and the Network tab for any 403 or 500 errors.