Skip to main content
Inspiring
Jan 13, 2021 2:32 PM UTC
Answered

Dynamic Content Filter not working in Version: 16.0.1.817

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 is closed to new replies. Start a new post to keep the conversation going.
    Sean Ferenci, P.Eng.Correct answer
    Inspiring
    Jan 14, 2021 7:22 PM UTC

    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.  

    6 replies

    Inspiring
    Jan 13, 2021 3:20 PM UTC

    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.

    Translate
    Adobe Employee
    Jan 14, 2021 8:32 AM UTC

    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

    Translate
    Sean Ferenci, P.Eng.AuthorCorrect answer
    Inspiring
    Jan 14, 2021 7:22 PM UTC

    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.  

    Translate