Hi guys:
I'm trying to create a glossary for confluence by following the follwing article: http://jodiem.com.au/2011/08/13/building-a-glossary-in-confluence/
Becuase this is an old article I'm trying to do the same but in Confluence 4.x and I almost had everything working except for the detail that when the glossary link macro is used within the confluence main document it always shown that it found the page Glossary but not the excerpt.
I created two macros:
The create term macro (this is the one used in the Glossary page):
##############################################################
## @param tooltip:title=Tooltip|type=string|required=true|desc=Tooltip
## @param name:title=Name|type=string|required=false|desc=Name
## @param phrase:title=Phrase|type=string|required=false|desc=phrase
<h3>
<ac:macro ac:name="anchor">
<ac:default-parameter>$paramname</ac:default-parameter>
</ac:macro>$paramphrase
</h3>
<ac:macro ac:name="cloak">
<ac:parameter ac:name="id">$paramname</ac:parameter>
<ac:rich-text-body>
<ac:macro ac:name="multiexcerpt">
<ac:parameter ac:name="MultiExcerptName">$paramname</ac:parameter>
<ac:parameter ac:name="atlassian-macro-output-type">INLINE</ac:parameter>
<ac:rich-text-body>
<a style="text-decoration:none; border-bottom:2px dotted; border-bottom-color:#008000" title="$paramtooltip" href="Glossary#$paramname">$paramphrase</a>
</ac:rich-text-body>
</ac:macro>
</ac:rich-text-body>
</ac:macro>
$body
#################################################################
and the glossary link macro (the one that is used in main pages)
#################################################################
## @param name:title=Name|type=string|required=false|desc=Name
<ac:macro ac:name="multiexcerpt-include">
<ac:parameter ac:name="MultiExcerptName">$paramname</ac:parameter>
<ac:parameter ac:name="PageWithExcerpt">Glossary</ac:parameter>
<ac:parameter ac:name="nopanel">true</ac:parameter>
</ac:macro>
#################################################################
Any help will be appreciated. If more info is needed just let me know
I also just stumbled upon a 2 part blog that outlines how to create this configuration that doesn't rely on the multi-exerpt-include macro that should get this functionality in place for you:
http://blogs.atlassian.com/2013/01/how-to-building-a-company-glossary-with-confluence/
http://blogs.atlassian.com/2013/01/how-to-building-a-company-glossary-with-confluence-part-two/
I tested your user macros locally, and they seem to be fine. I think this is a bug in Artemis's multi-excerpt macro. If you inspect the source of a page with your 'term' macro rendered (via Source Editor), it shows up like this:
<ac:macro ac:name="term"> <ac:parameter ac:name="phrase">My Phrase</ac:parameter> <ac:parameter ac:name="name">Term Name</ac:parameter> <ac:parameter ac:name="atlassian-macro-output-type">BLOCK</ac:parameter> <ac:parameter ac:name="tooltip">My Hover Text</ac:parameter> <ac:rich-text-body>This is a definition of things.</ac:rich-text-body> </ac:macro>
Then, inspect the source of the rendered page in Firebug or Chrome Dev mode, and you can see that the cloak macro and header macro were able to interpret the $paramname object:
<span class="confluence-anchor-link" id="Glossary-TermName"</span> <h3 id="Glossary-MyPhrase">My Phrase</h3> <h3 id="Glossary-TermName">Term Name</h3> <span id="content_Term Name" class="cloak" style="display: none"> <a style="text-decoration:none; border-bottom:2px dotted; border-bottom-color:#008000" title="My Hover Text" href="Glossary#Term Name" rel="nofollow">My Phrase</a> </span>
Anchor correctly created the "Glossary-TermName" id, and cloak created the "content_Term Name" id. Artemis, the creator of the multi-excerpt plugin, has their support contact details and a link to their Marketplace JIRA instance here. They should be able to help you sort it out, or confirm the bug.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.