Skip to main content
New Participant
October 1, 2013
Question

RH10 not creating XML files in whxdata

  • October 1, 2013
  • 1 reply
  • 1715 views

We converted from RH7 to RH10 earlier this year, and our application uses the XML files in whxdata to connect help buttons to topics.  It seems that RH10 is not creating these XML files, which is breaking this functionality.

Some searching indicates that these files should be created when the primary WebHelp layout is being built.  I can't find any settings anywhere that indicates whether or not they should be created. 

Is this a consequence of the conversion, or does RH10 not create these files anymore?

This topic has been closed for replies.

1 reply

Captiv8r
Brainiac
October 1, 2013

Hi there

First off, it always helps to check the basics. Are you certain you are looking at the correct location?

Assuming you are, look at the properties for the single source layout. Specifically, the Navigation section on the left side and the "Optimize Speed for" option on the right side.

Click the image below for a larger and clearer view

As far as I'm aware, this is the specific setting that determines whether your navigational elements are broken into smaller chunks.

Lastly, I'm a bit confused. To my knowledge, only the navigational elements (TOC, Index, Glossary and Search) are affected and XML data created for these. I'm rather surprised to hear that your development team is somehow using the XML files created for these in order to establish context sensitive help.

Cheers... Rick

MAHorniakAuthor
New Participant
October 1, 2013

I'm not sure what practice established using the XML files, but I know that they could not connect the help topics if there was not an index entry for the topic.

I have checked all of these settings, and they do not change the output. 

I should clarify, though, that there are files being generated, just not the ones that we would prefer.  See the screenshot below.

Captiv8r
Brainiac
October 1, 2013

Ahhh forgot about that. Yep, the dev team renamed them all from .XML to the .JS. Not sure why.

You might consider submitting a bug report as this affects you.

http://www.adobe.com/go/wish

Cheers... Rick