collection-type="sequence" and Navigation Buttons

Post by **Eddie** » Fri Dec 01, 2017 5:12 am

Hello,
Using Author 19.1 to output webhelp responsive.
We want to have a clear run of navigation buttons through all topics - preface to glossary.
We've tried various combinations using collection-type="sequence" but always get some messed up links.

First, could you confirm something please. My understanding (from various sources of information online) is that if I have collection-type="sequence" in the map element, it will be inherited by all topics. Is that correct? If I try this with webhelp responsive, I only get nav buttons in part elements.

I've tried setting webhelp.default.collection.type.sequence to yes. This gives me buttons in all topics, but a bunch of strange links.
If I set the parameter only, with no collection-type="sequence" in the map,I get 11 broken links.
If I set the parameter, with collection-type="sequence" only in the map element,I get 10 broken links.
If I set the parameter, with collection-type="sequence" in every part/chapter/topichead/topicref/etc in the map,I still get 2 broken links.

About the links:
All topics are in sample/topics, so are linked in the map as, eg, href="sample/topics/c-topicref-2.dita".
In the output, if I mouseover some nav buttons, the link is shown as eg, "~~~~sample/topics/sample/topics/c-topicref-2.dita" and clicking the link gives "file not found". The TOC link to the same topic has the correct link and jumps correctly.
Author lists the transformation errors as DOTX031E.
In the last instance, with only 2 broken links, the affected files are the preface (which is in frontmatter) and the last file before the backmatter.

Any idea what is happening?

Cheers,
Eddie.

Post by **radu_pisoi** » Fri Dec 01, 2017 10:04 am

Hi,

You can achieve the same functionality by using the webhelp.default.collection.type.sequence=yes parameter. It specifies if the sequence value will be used by default when the collection-type attribute is not specified. This option is helpful if you want to have Next and Previous navigational buttons generated for all HTML pages.

Could you try to use this parameter?

Post by **Eddie** » Mon Dec 04, 2017 1:54 am

Please re-read my initial post.

Eddie.

Post by **Eddie** » Mon Dec 04, 2017 3:47 am

Hello,
As a post script to my initial post...

I managed to get rid of the last two DOTX031E errors. This was by setting collection-type="sequence" in bookmap, frontmatter, backmatter and booklists in addition to all of the previous elements (part/chapter/topichead/topicref/keydef - basically anything that accepts collection-type="sequence").

However, even so, the button sequence skips over any topicheads and any topics they contain when going "forwards" (right arrow button). The sequence correctly links to every topic when going backwards (left arrow button).

Please note that this is with or without webhelp.default.collection.type.sequence set to yes.

Cheers,
Eddie.

Post by **radu_pisoi** » Mon Dec 04, 2017 1:14 pm

Hi,

I cannot reproduce this issue with a small DITA map that I've changed to wrap some topicref in a topichead element.

Code: Select all


<topichead navtitle="Care topics">

	<topicref href="topics/care.dita">

	  <topicref href="tasks/pruning.dita"/>

	  <topicref href="tasks/gardenPreparation.dita"/>

	</topicref>    

</topichead>

I've used the webhelp.default.collection.type.sequence=yes parameter.

Could you send us a small DITA map sample together with the referenced topics to reproduce the problem at support@oxygenxml.com?