Issue Details (XML | Word | Printable)

Key: BUILDER-705
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Alain Moran
Reporter: Guy Fraser
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Confluence Extension: Builder

Unable to add separators in wiki menus

Created: 07/Sep/07 03:21 AM   Updated: 18/Sep/07 11:51 PM
Component/s: Menu Macros and Menus
Affects Version/s: 3.0.0.b9
Fix Version/s: 3.0.0.b10

Time Tracking:
Not Specified


 Description  « Hide
Got a minor issue - I need to allow clients super-simple ability to add in custom navigation (via a navigation page, pulled in via the include macro, wrapped in wikimenu macro).

We used to be able to use notation like this to create a separator in normal wiki markup that's parsed in to a menu via wikimenu macro:

* before separator
* ----
* after separator

The wikimenu macro used to take that, spot the <li><hr></li> and turn it in to <li></li> so that a separator would appear - it doesn't any more?



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Guy Fraser added a comment - 07/Sep/07 03:38 AM
Actually, found that you can do this with the following notation:
* [foo]
* 
* [bar]

(with a space after the * on the middle line)


Alain Moran added a comment - 07/Sep/07 10:44 AM
Why is this issue still open then?

Also ... why are you using wikimenu?


Guy Fraser added a comment - 07/Sep/07 12:47 PM - edited
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".


Alain Moran added a comment - 07/Sep/07 01:53 PM
Released with 3.0 beta 7

Alain Moran added a comment - 07/Sep/07 06:51 PM
Ooops ... looks like this got caught up in a bulk change

Alain Moran added a comment - 07/Sep/07 06:52 PM
So basically you want wikimenu to use the slower way of rendering the content and do a regex into the bargain?

Guy Fraser added a comment - 07/Sep/07 08:03 PM
What's it doing at the moment?

Alain Moran added a comment - 07/Sep/07 08:20 PM - edited
It uses confluence to render it's body and then does replacements on the HTML ... why not just update the documentation?

Alain Moran added a comment - 13/Sep/07 12:16 AM
Code added to convert old style separators to new.

NB: please select the affects version when creating issues


Alain Moran added a comment - 13/Sep/07 05:13 PM
Released with beta 10