Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-12149

Third-party macros should be able to specify whether macro body should be displayed in Rich Text editor

XMLWordPrintable

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      A macro developer should be able to specify whether the Rich Text editor should display the body as raw wiki markup or as processed wiki markup. Currently, if you want to expand the functionality of your tables by using the

      {table-plus} macro, you lose the ability to edit the content as a table in the Rich Text editor, because the content of the macro is shown as raw wiki markup. Additionally, if you attempt to edit the content of a table in the {table-plus}

      macro from within the Rich Text editor, the editor may remove spaces between the pipe characters in the table, both changing empty cells into header cells and reducing the number of cells in the row.

        1. screenshot-1.jpg
          screenshot-1.jpg
          134 kB

            [CONFSERVER-12149] Third-party macros should be able to specify whether macro body should be displayed in Rich Text editor

            Don Willis added a comment -

            Hi Baris,

            How was this fixed? Can sysadmins configure a list of macros & plugins that should not be altered by the RTE, or does the plugin have to be updated to support this new functionality?

            The plugin has to be updated.

            For example, we are using confluence 3.5 and suffer these issues with the {latex} plugin.

            Then yes, you'll have to discuss it with the developers of that plugin. It's a simple change, although as mentioned above the developers may have to have a pre 3.1 and post 3.1 version of their plugin. There probably aren't too many people using 3.0 now though, so probably not.

            How do we configure it for custom/user macros?

            I don't believe you can configure it for user macros. If by custom macros you mean your own inhouse full plugins, you simply override the getWysiwygBodyType() in your method.

            Note that the fix doesn't technically implement exactly what the summary line of the issue says, but what people requested in the description in comments. Macros can specify whether their bodies should be displayed as raw wiki markup in a preformat block, or rendered into html. The body cannot be completely hidden.

            Don Willis added a comment - Hi Baris, How was this fixed? Can sysadmins configure a list of macros & plugins that should not be altered by the RTE, or does the plugin have to be updated to support this new functionality? The plugin has to be updated. For example, we are using confluence 3.5 and suffer these issues with the {latex} plugin. Then yes, you'll have to discuss it with the developers of that plugin. It's a simple change, although as mentioned above the developers may have to have a pre 3.1 and post 3.1 version of their plugin. There probably aren't too many people using 3.0 now though, so probably not. How do we configure it for custom/user macros? I don't believe you can configure it for user macros. If by custom macros you mean your own inhouse full plugins, you simply override the getWysiwygBodyType() in your method. Note that the fix doesn't technically implement exactly what the summary line of the issue says, but what people requested in the description in comments. Macros can specify whether their bodies should be displayed as raw wiki markup in a preformat block, or rendered into html. The body cannot be completely hidden.

            Baris Acar added a comment -

            How was this fixed? Can sysadmins configure a list of macros & plugins that should not be altered by the RTE, or does the plugin have to be updated to support this new functionality?

            For example, we are using confluence 3.5 and suffer these issues with the

            {latex}

            plugin.

            How do we configure it for custom/user macros?

            Baris Acar added a comment - How was this fixed? Can sysadmins configure a list of macros & plugins that should not be altered by the RTE, or does the plugin have to be updated to support this new functionality? For example, we are using confluence 3.5 and suffer these issues with the {latex} plugin. How do we configure it for custom/user macros?

            Don Willis added a comment -

            Hi Bob, glad to hear table plus will be supporting the new format. Would you mind raising that bug as a new issue?

            Don Willis added a comment - Hi Bob, glad to hear table plus will be supporting the new format. Would you mind raising that bug as a new issue?

            Bob Swift added a comment - - edited

            Created CONF-18748 to cover a case where RTE throws away data.

            Bob Swift added a comment - - edited Created CONF-18748 to cover a case where RTE throws away data.

            Bob Swift added a comment - - edited

            Supported in Table plugin release 4.0.0

            Bob Swift added a comment - - edited Supported in Table plugin release 4.0.0

            Andreas Schmid (TNG Technology Consulting GmbH) added a comment - - edited

            For a patched version see https://studio.plugins.atlassian.com/browse/TBL-66?focusedCommentId=30025&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_30025. Also a diff to the current tag of table plugin 3.4.0 is there provided.

            The patch works only for Confluence 3.1.

            Andreas Schmid (TNG Technology Consulting GmbH) added a comment - - edited For a patched version see https://studio.plugins.atlassian.com/browse/TBL-66?focusedCommentId=30025&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_30025 . Also a diff to the current tag of table plugin 3.4.0 is there provided. The patch works only for Confluence 3.1 .

            Bob Swift added a comment -

            We are upgrading to 3.1 this month, so I am hoping to get it done before that.

            Bob Swift added a comment - We are upgrading to 3.1 this month, so I am hoping to get it done before that.

            Fabian Breuer added a comment -

            Hi Bob,

            thanks for this quick reply. Can you tell me when you can do the fix? This month? Next month?

            Thanks & Greetz
            Fabian

            Fabian Breuer added a comment - Hi Bob, thanks for this quick reply. Can you tell me when you can do the fix? This month? Next month? Thanks & Greetz Fabian

            Bob Swift added a comment -

            The change requires another table-plus update . Will get to it soon.

            Bob Swift added a comment - The change requires another table-plus update . Will get to it soon.

            Fabian Breuer added a comment -

            Hi there,

            table-pus marco worked well in Confluence 3.0. The table was rendered in the RTE. After we upgraded to Confluence 3.1 it doesn´t work anymore. Can anybody confirm this?

            Fabian Breuer added a comment - Hi there, table-pus marco worked well in Confluence 3.0. The table was rendered in the RTE. After we upgraded to Confluence 3.1 it doesn´t work anymore. Can anybody confirm this?

              don.willis@atlassian.com Don Willis
              01fc6e9af467 Jim Dibble
              Votes:
              38 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: