Skip to main content
mmckita
Participant
Jan 11, 2018 3:48 PM UTC
Answered

Why does the keyword Index search capability not work in Responsive HTML5 output with FM 14.0.3.500 upgrade?

Ever since I upgraded FM 2017 to 14.0.3.500 in early December, 2017, the keyword Index search capability no longer works in my Responsive HTML5 output (an online Help system). If you type in the search bar of the Index, nothing happens. Previously, the Index would immediately start offering keywords starting with the string that was input. I did not change anything in my settings files. Any idea why the keyword Index search no longer works?

This topic is closed to new replies. Start a new post to keep the conversation going.
Correct answer
Jan 30, 2018 12:12 PM UTC

In the Tracker, the case has meanwhile been tagged as 'Working as Designed'. 'Working as Designed' obviously means: Applying this patch renders all existing template customizations unusable (without any advance warning) and it is up to the user to do all the customizing again in order to get a help system with a working index keyword search.

Definitely not my expectation of how a patch should work.

8 replies

AbhishekSChauhan
Participant
Jan 29, 2018 12:59 PM UTC

Due to some inherent code change, it's mandatory to pick the latest layouts provided in FrameMaker (2017 release), Update 3.

In case you have some customizations on the older layout, you need to redo it.

Translate
Correct answer
Jan 30, 2018 12:12 PM UTC

In the Tracker, the case has meanwhile been tagged as 'Working as Designed'. 'Working as Designed' obviously means: Applying this patch renders all existing template customizations unusable (without any advance warning) and it is up to the user to do all the customizing again in order to get a help system with a working index keyword search.

Definitely not my expectation of how a patch should work.

Translate
Matt-Tech Comm Tools
Community Expert
Community Expert
Jan 11, 2018 4:07 PM UTC

I haven't checked this, but please post to adobe.com/go/wish

Translate
-Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant
Jan 25, 2018 1:36 PM UTC

I am experiencing this as well with FM 14.0.3.500, and if it worked before, this is definitely a bug that needs to be fixed.

Translate
Jeff_Coatsworth
Community Expert
Community Expert
Jan 25, 2018 1:45 PM UTC

Raise a bug report to get it on Adobe's radar - piling on with "me too" in the forums doesn't get anything fixed.

Translate