Skip to main content
S
Sean Ferenci, P.Eng.
Inspiring
January 13, 2021
Answered

Dynamic Content Filter not working in Version: 16.0.1.817

  • January 13, 2021
  • 1 reply
  • 694 views

I found that Dynamic Content Filtering no longer works when I try to publish in HTML5 in Version: 16.0.1.817

 

I created a simple DITA map to demontrate this.

 

<map>
<title>MAP TITLE</title>
<topicref href="conceptA.xml" type="concept" product="A">
<topicmeta>
<navtitle>Concept A</navtitle>
</topicmeta>
</topicref>
<topicref href="conceptB.xml" type="concept" product="B">
<topicmeta>
<navtitle>Concept B</navtitle>
</topicmeta>
</topicref>
<topicref href="conceptC.xml" type="concept" product="A B">
<topicmeta>
<navtitle>Concept C</navtitle>
</topicmeta>
</topicref>
</map>

 

When I publish, no filter option is appearing.

 

 

 

    This topic has been closed for replies.
    Correct answer Sean Ferenci, P.Eng.

    I am no longer able to reproduce the error.  I am using the same files as before but the HTML5 is being generated properly now with filters.  This isn't a bad thing, but it would have been nice to know what caused the problem.

    Thanks for your help Bhavyaa.  

    1 reply

    S
    Sean Ferenci, P.Eng.Author
    Inspiring
    January 13, 2021

    Update, it looks like the HTML5 template was the culprit here.  The 2019 HTML5 template needs to be updated to support Framemaker 2020.  When I worked off of the default.sts file the filters reappeared.  

     

    It looks like I have to rebuild my slz files for the new update.  Not ideal but at least it offers a solution.

    B
    Adobe Employee
    bbansal
    Adobe Employee
    January 14, 2021

    Hi sean,

    It might be the sts, but the ditamap files use Ditaval option for filtering the content and dita file use DCF. It would be helpful if you could share the file and sts. We will verify and let you know.

     

    Thanks,

    Bhavyaa

      S
      Sean Ferenci, P.Eng.AuthorCorrect answer
      Inspiring
      January 14, 2021

      I am no longer able to reproduce the error.  I am using the same files as before but the HTML5 is being generated properly now with filters.  This isn't a bad thing, but it would have been nice to know what caused the problem.

      Thanks for your help Bhavyaa.  

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices