New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-8220
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Dylan Etkin [Atlassian]
Reporter: Jeff Turner [Atlassian]
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Wiki formatting mangles text in {brackets}

Created: 13/Oct/05 12:59 AM   Updated: 30/Jul/06 07:34 PM
Component/s: Renderers
Affects Version/s: 3.4 Beta 1
Fix Version/s: 3.4.1

Time Tracking:
Not Specified

Issue Links:
Duplicate

Participants: Dylan Etkin [Atlassian] and Jeff Turner [Atlassian]
Since last comment: 2 years, 41 weeks, 4 days ago
Resolution Date: 10/Nov/05 09:23 PM
Labels:


 Description  « Hide
When the Wiki renderer is enabled, text like ${JAVA_HOME} in existing fields and comments breaks with:

Unknown macro: {JAVA_HOME}

We should fix the renderer to print literally 'macros' that it doesn't understand.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order

Dylan Etkin [Atlassian] added a comment - 16/Oct/05 10:00 PM
I updated the renderer with a new render mode that allows us to suppress the macro does not exist warning, JIRA now uses this render mode. JIRA will now render the text as it found, applying wiki markup to the internal contents of the macro tag and body.

Jeff Turner [Atlassian] added a comment - 09/Nov/05 01:40 AM

Doesn't appear to be entirely fixed - see description of JRA-7108

Dylan Etkin [Atlassian] added a comment - 10/Nov/05 09:23 PM
The problem was with unknown macros that seem to have a body. This has been fixed up. There is still an issue in that the body of the unknown macro gets rendered as a sub-rendering of the other content. Practically this means that lists may not render correctly if some of the list items are surrounded by matched unknown macro syntax. There is not anything we can do about this in the renderers current incarnation, it is a limitation of how the renderer idetifies macro's and their bodies.