[CONFSERVER-23927] Macros in wiki markup that are in upper case don't get migrated to XHTML

Type: Bug
Resolution: Fixed
Priority: Low
Fix Version/s: 4.3.5
Affects Version/s: None
Component/s: None
Labels:
- editor
- loyalty
- team-ants

Bug Fix Policy:
View Atlassian Server bug fix policy

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

is duplicated by

CONFSERVER-24900 Macro conversion from Confluence 3.x to 4.x fails on mixed case macros

Closed

is related to

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

Closed

relates to

CONFCLOUD-23927 Macros in wiki markup that are in upper case don't get migrated to XHTML

Closed

mentioned in: Wiki Page Failed to load; Wiki Page Failed to load; Wiki Page Loading...

(1 mentioned in)

Julien Michel Hoarau (Inactive) added a comment - 09/Dec/2012 11:55 PM

QA'd using the CODE macro.

Julien Michel Hoarau (Inactive) added a comment - 09/Dec/2012 11:55 PM QA'd using the CODE macro.

JenniferC added a comment - 13/Sep/2012 2:54 AM

This issue has come up during a client upgrade, while there are no visible effects on the page, it could lead users to continue the habit of entering wiki markup using the capitalized macro names instead of using the correct macro placeholders. It also comes up in the number of unmigrated wiki pages, which is misleading and makes it hard to figure out exactly how many serious issues there are.

JenniferC added a comment - 13/Sep/2012 2:54 AM This issue has come up during a client upgrade, while there are no visible effects on the page, it could lead users to continue the habit of entering wiki markup using the capitalized macro names instead of using the correct macro placeholders. It also comes up in the number of unmigrated wiki pages, which is misleading and makes it hard to figure out exactly how many serious issues there are.

Chris Kiehl added a comment - 05/Dec/2011 3:10 AM

We should use the plugin key when looking up macro migrations instead of the macro name

Chris Kiehl added a comment - 05/Dec/2011 3:10 AM We should use the plugin key when looking up macro migrations instead of the macro name

Assignee:: AlexanderA (Inactive)

Reporter:: Chris Kiehl

Affected customers:: 0 This affects my team

Watchers:: 3 Start watching this issue

Created:: 22/Nov/2011 1:06 AM

Updated:: 11/Oct/2018 8:37 AM

Resolved:: 09/Dec/2012 11:55 PM

Details

Description

Attachments

Issue Links

Forms

Activity

Collapse comment: Julien Michel Hoarau (Inactive) added a comment - 09/Dec/2012 11:55 PM

Expand comment: Julien Michel Hoarau (Inactive) added a comment - 09/Dec/2012 11:55 PM

Collapse comment: JenniferC added a comment - 13/Sep/2012 2:54 AM

Expand comment: JenniferC added a comment - 13/Sep/2012 2:54 AM

Collapse comment: Chris Kiehl added a comment - 05/Dec/2011 3:10 AM

Expand comment: Chris Kiehl added a comment - 05/Dec/2011 3:10 AM

People

Dates