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

current wiki-markup macro converts markup on the fly. I would like the wiki-markup macro to not convert and retain the markup as it is

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • 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.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      We found that after the upgrade to 4.0 the wiki-markup editor and all offline-edit functionality was removed. But I noticed, that there is a bug in the conversion process. Macros with capitals do not get converted. They are covered by a special wiki-markup macro. Though being displayed correctly you can see that when going to the edit-mode (see atteched screenshot).
      When it is possible to enter that wiki-markup macro and e.g. have an optional parameter, that keeps it from converting it's content to the new format, the old markup-editor is back and also the offline-edit functionality since the markup code can easily (copy and paste) be taken to some other editor and being edited while offline.

        1. screenshot wiki-markup macro.jpg
          screenshot wiki-markup macro.jpg
          112 kB

            [CONFSERVER-23895] current wiki-markup macro converts markup on the fly. I would like the wiki-markup macro to not convert and retain the markup as it is

            BillA added a comment -

            Hi Christian,

            It's true that there's a workaround that if you use the "insert wiki markup" dialog to insert a macro (like table-plus) that isn't 4.0 compatible, it will wrap that macro in a "unmigrated wiki markup" macro. You could use that workaround for the time being but we don't plan to explicitly add "don't convert this to XHTML" functionality because we don't intend to support wiki markup as a storage format forever. Feel free to use the workaround for the time being, however.

            Best Wishes,
            Bill

            BillA added a comment - Hi Christian, It's true that there's a workaround that if you use the "insert wiki markup" dialog to insert a macro (like table-plus) that isn't 4.0 compatible, it will wrap that macro in a "unmigrated wiki markup" macro. You could use that workaround for the time being but we don't plan to explicitly add "don't convert this to XHTML" functionality because we don't intend to support wiki markup as a storage format forever. Feel free to use the workaround for the time being, however. Best Wishes, Bill

              barconati BillA
              e77ea3f5619e Christian Luebke
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: