I was just starting to test a glossary in HTML5 and ran into a problem where when you click the Glossary tab, you get a never ending spinner. The glossary is a test glossary with only one entry. The help system is a "merge by target" system consisting of about 40 different projects. Has anyone else seen this?
Thanks,
Tim
HTML5 Glossary Issue
Re: HTML5 Glossary Issue
I am testing HTML5 and am experiencing this same glossary problem: in the HTML5 output, the glossary file doesn't load and the spinner keeps spinning.
The glossary is built by linking to topics, rather than by entering the definition into the glossary file. My output does include merged TOCs from 3 different projects. The glossary works fine in WebHelp, the current output we are using.
Has anyone else encountered this problem, and found a resolution?
Thanks...
The glossary is built by linking to topics, rather than by entering the definition into the glossary file. My output does include merged TOCs from 3 different projects. The glossary works fine in WebHelp, the current output we are using.
Has anyone else encountered this problem, and found a resolution?
Thanks...
Re: HTML5 Glossary Issue
I contacted Flare support about this and wanted to share the way to handle the glossary not loading in case anyone else has this issue. The issue can occur if you are merging subprojects to create your output.
Our project has a master project and 3 subprojects that are merged using TOC links.
We have been generating WebHelp. Our glossary is in the main project and includes links to topics in the subprojects. With WebHelp, each subproject did not need to have a glossary attached. With HTML5, each subproject needs to have a glossary attached - not the glossary from the main project (I couldn't get the gloassary to load when attaching this glossary to the child project), but a glossary file you add for this project with at lease one term. Whatever term you use in this glossary will show up in the output, so it needs to be a valid term and not the default "My Term."
When each subproject has a glossary (with at lease one term) attached to its taget, then the glossary loads correctly in the HTML5 output.
Our project has a master project and 3 subprojects that are merged using TOC links.
We have been generating WebHelp. Our glossary is in the main project and includes links to topics in the subprojects. With WebHelp, each subproject did not need to have a glossary attached. With HTML5, each subproject needs to have a glossary attached - not the glossary from the main project (I couldn't get the gloassary to load when attaching this glossary to the child project), but a glossary file you add for this project with at lease one term. Whatever term you use in this glossary will show up in the output, so it needs to be a valid term and not the default "My Term."
When each subproject has a glossary (with at lease one term) attached to its taget, then the glossary loads correctly in the HTML5 output.