show.profiling.attributes Option Has No Effect

[dreifsnider]

Hi,

We're trying to use the show.profiling.attributes option, as mentioned in the User Guide: https://www.oxygenxml.com/doc/versions/ ... tions.html

However, it seems to have no affect on whether or not the actual profiling attribute and value is displayed. We have it set to false in our options.xml file as you can see:

image.png (369.37 KiB) Viewed 695 times

However, the profiling attribute and its value (if <attribute> is <value>) still displays, for example:

image.png (314.66 KiB) Viewed 695 times

Does this option serve another purpose? If so, is there another way to hide these profiling attribute statements, perhaps using CSS?

Thanks!

Daniel

[cosminef]

Hello,

We have also tested adding that rule to the options.xml, and indeed, it does not work.
We have logged an issue (WA-7017) regarding this matter, and when it is resolved, you will be notified here, on the forum.
As a workaround, you can extend the DITA framework using Oxygen XML Editor. [1] and delete the URI to "profiling.css" (click on it and select "x" - delete)

dita-extend.PNG (44.83 KiB) Viewed 671 times

After your .framework file is created, you can archive it and upload it to Content Fusion (upload framework) [2]

The output should look like this, after the changes:

profiling-output.PNG (59.72 KiB) Viewed 671 times

[1] https://www.oxygenxml.com/doc/versions/ ... nding.html
[2] https://www.oxygenxml.com/doc/versions/ ... works.html

[dreifsnider]

Hi Cosmin,

Thank you for confirming that the option doesn't work as expected! Thank you for also mentioning the workaround.

I believe we'll ultimately end up customizing the profiling.css to have more granular control over how certain profiled content as well as attributes and their values are displayed in Content Fusion. For now though I will use your workaround to hide the profiling attributes entirely.

(For what it's worth, this was the option I was trying to use when I mistakenly believed the entire options.xml file wasn't working as I indicated in my support email. )

Thanks again!

Daniel