|
Why is this issue still open then?
Also ... why are you using wikimenu? Our docs state to use this:
* ---- ...for a separator - it's more visually representative to end users as well as they'll see the separator line (a <hr>) in their unordered list on the wiki page. Customers using Builder 2.x still use that notation in some places. While I've found a workaround, it should still be fairly easy to "fix" the wikimenu macro to search for <li><hr></li> and simply strip out the <hr> in that specific scenario (NB: <hr>'s may be used in other places such as li's with div's for displaying custom HTML sections in the menu. I'm not sure if there will be any spacing or other tags applied in the <li><hr></li> output by the wiki notation above, but it should be trivial to check. As for using wikimenu, the client wants their nav to be easily editable via the RTE - it's very easy for them to say "create a nested bullet list of links in the Rich Text editor and it will appear in the menu" vs. "learn how to use various macros and the wiki markup editor". Ooops ... looks like this got caught up in a bulk change
So basically you want wikimenu to use the slower way of rendering the content and do a regex into the bargain?
What's it doing at the moment?
It uses confluence to render it's body and then does replacements on the HTML ... why not just update the documentation?
Code added to convert old style separators to new.
NB: please select the affects version when creating issues |
||||||||||||||||||||||||||||||||||||||||||||
(with a space after the * on the middle line)