Skip to main content
emgaucher
Inspiring
July 18, 2018
Answered

RH2017 Indigo layout, topic section blank?

  • July 18, 2018
  • 2 replies
  • 734 views

Switched to the new Indigo layout, works beautifully in my RH-generated output but when we access it from our product the topic area is blank. I made sure I had all the recent RH updates.

Any ideas?

This topic has been closed for replies.
Correct answer emgaucher

Update: turns out development's build machine was running an older version of RH. We had that updated to 2017, and now the topics are displaying as they should.

2 replies

emgaucher
emgaucherAuthorCorrect answer
Inspiring
August 13, 2018

Update: turns out development's build machine was running an older version of RH. We had that updated to 2017, and now the topics are displaying as they should.

Jeff_Coatsworth
Community Expert
Community Expert
August 13, 2018

Glad to hear that you got it fixed, but maybe next time you mention that you used another machine to actually create the output - everyone thought you were talking about your copy of RH and the output YOU generated ;>)

emgaucher
emgaucherAuthor
Inspiring
August 13, 2018

That's because I only recently discovered they were using separate build machines. Our developers are a secretive bunch.

Jeff_Coatsworth
Community Expert
Community Expert
July 18, 2018

Are you seeing the same effect if you launch the index page outside of RH?

emgaucher
emgaucherAuthor
Inspiring
July 18, 2018

No, if I launch the index page from the folder location it opens up as it should. Seems to only be when it's accessed from our product.

I forgot to mention that we're using map IDs to call the help topics, and I have no real option to change that...not sure if that could be causing the issues or not?

Jeff_Coatsworth
Community Expert
Community Expert
July 18, 2018

IIRC, CSH calls to HTML5 topics changed from CSH WebHelp calls, but if it was working before with HTML5 (using just another layout) I don't think it should impact you. Did they include all the files in your \!SSL!\ folder in their build?