Skip to main content
New Participant
September 12, 2016
Answered

HTML version won't browse index subentries

  • September 12, 2016
  • 2 replies
  • 944 views

Our document will primarily be used in the html version so we really have to make sure users can search for their problem. We realized quickly that using the regular serach will usually not solve the problem (especially if the keywords used are broad or the user doesn't know the correct term) so we decided to optmize our index to display the correct results.

Now we are the ones experiencing problems: If we browse the index, it won't show sub entries. Ever. It seems like it only browses the first level.

Example: In this case, my search for "aktiver Dozent" will show no results because it's a second level subentry, only "Umfrage" (the first level) is browsable.

Is this a bug or is there anything we can do about it? Do you have any alternative solutions (such as working with search metadata)?

Edit: Used version: FM 15

This topic has been closed for replies.
Correct answer abhi_AdobeTC

Hi,

This is a known issue and surfaced recently. We are working on a fix for the same and it will be available shortly.

Reference: Search Engine Optimization for Responsive HTML Output

~Abhishek

2 replies

abhi_AdobeTCCorrect answer
Adobe Employee
September 13, 2016

Hi,

This is a known issue and surfaced recently. We are working on a fix for the same and it will be available shortly.

Reference: Search Engine Optimization for Responsive HTML Output

~Abhishek

Jeff_Coatsworth
Braniac
September 13, 2016

Really? Ok then…

Jeff_Coatsworth
Braniac
September 13, 2016

OK, so it's FM2015, not FM15 - are you all patched up? What output format are you publishing?

lisa_goAuthor
New Participant
September 13, 2016

Hi Jeff, thanks for replying!

Sure, it's FrameMaker2015.

We are currently using the standard publishing option for HTML. Does that answer your question?

I will check with my team though if we are all patched up.

Jeff_Coatsworth
Braniac
September 13, 2016

Is that the responsive HTML5 option or just regular WebHelp?