1 person found this helpful
Your webhelp will work fine without it. Tell your webmaster to go back to sleep.
See www.grainge.org for RoboHelp and Authoring tips
I conducted a Forum search on contentlist.xml that identifed your response, above. Unfortunately, Dynamic User-Centric Categories isn't clear to me. A search on that phrase brought me back to your reponse. I searched on Dynamic Categories and found too many items to easily distinguish your reference. Could you clarify the reference?
My developer is encountering a contentlist.xml not found error... even though contentlist.xml is referenced in whtbar.js.
var svTitle="Select a content category";
var contentListPath = "contentlist.xml";
var xmlreader = new XmlReadWriteHelper();
xmlreader.strFilePath = contentListPath;
var xmlDoc = xmlreader.getXmlDoc();
if(xmlDoc != null)
He wants to know where contentlist.xml ought to be found, when applicable. And my initial question was intended to help us determine whether I can / should make the project adjustments needed to produce a functional contentlist.xml .
Essentially, he is building url-based context sensitive functionality into a flagship product and doesn't want to use Map IDs. Parenthetically, he has been able to make this function work in an old version of the my help project that incorporated a single level Project Manager directory. His system seems to be stumbling on the multi-level directory that now exists in the project.
I think Peter maybe "offline" today so let me interfere :-)
Dynamic User-Centric Categories or DUCC for short is a feature that came in with RH9. It has been described as conditional build tags on steroids. It allows you to add a dropdown to your TOC that can be used to filter the topics displayed. For example if you have a help file with different procedures depending on whether the user is US, European or Asia based. If you are not using this feature, there is absolutely no need for the contentlist.xml file.
You were sooo close with the acronym!
DUCC = Dynamic User-Centric Content
Additionally, the drop-down is inserted into the Navigation Mini-Toolbar that sits between the TOC and Index and Glossary and Search. It's not within the TOC. (It's still visible when viewing the Index and the Search.)
Certainly Conditional Build Tags might be used with the feature, but they don't have to be. Lest there be confusion with this feature, it does not "dynamically apply Conditional Build Tags". In reality, what it does is cause multiple versions of WebHelp output to be created. (Each with its own little swarm of files) Then when the end user chooses one of the other outputs from the drop-down, it redirects to that version of the help. This allows a unique TOC and Index and Search for whatever version of the help the author has created and the end user wants to see.
Helpful and Handy Links