| creating a nested table of contents structure [message #648256] |
Wed, 12 January 2011 00:54  |
 jcb
Messages: 12
Registered: September 2010 |
Junior Member |
|
|
Hi.
I am attempting to create a nested toc structure in my help plugin. I want my main toc.xml bring in the nested, modular toc.xml files that exist within the structure of my plugin directory tree.
In my top-level toc.xml I have this:
<topic label="Reference" >
<topic label="my-lib">
<topic label="Version X" href="html/reference/my-lib/version-x/index.html">
<link toc="html/reference/my-lib/version-x/toc.xml"></link>
</topic>
<topic label="Version Y" href="html/reference/my-lib/version-y/index.html">
<link toc="html/reference/my-lib/version-y/toc.xml"></link>
</topic>
</topic>
</topic>
Then, the nested toc.xml files look like this (for example, Version X):
<toc label="Version X">
<topic label="foo function" href="html/reference/my-lib/version-x/foo.html"/>
...
</toc>
(there are more <topic> elements, too many to include here.)
The help table of contents does show the structure correctly down to Reference/my-lib/Version X, but instead of making Version X into a book with subtopics from its linked toc.xml, it only shows Version X as a single topic page (i.e. a page icon), with nothing underneath. When I click on Version X in the tree it does locate the index.html specified in its href attribute. (Same behavior goes for Version Y.)
So it looks like the <link> elements don't do anything. There is no error logged when the help loads.
I have seen this working in a different help plugin. The toc was not nested as deeply, but the mechanism and directory structure is exactly the same.
What are some probable causes for <link> to fail, or at least not work as I'm expecting it to in this case? Is there someplace else to look for debugging output besides the error log?
Thanks for any assistance,
John
|
|
|
] 
Search
Help
Register
Login
Home
