Hi,

Sorry for the delayed response. I did managed to reproduce the error in Oxygen 23.1.
I have submitted a task (ID: EXM-47764) to analyze what is the cause of this behavior.

Regards,
Alin

Hello, In my opinion this a classpath issue. You should check the order of Saxon libraries listed in the transformation's console output and check that the Saxon jar file from {OXYGEN-INTSALL_DIR}/lib is listed before the one bundled in your current DITA-OT. Please see this topic post . You can also...

Hello, It seems that you need to follow this procedure and update your transformation scenario. Cannot find a 1-argument function named Q{http://expath.org/ns/file}last-modified() The file:last-modified function is available only in Saxon EE and PE distributions and the DITA-OT bundled in Oxygen use...

Hello, The Publication TOC (Side TOC) is generated based on the structure of the expanded DITA map (that is the DITA map created in the WebHelp transformation's temporary directory). The profiling attributes declared at topic level are not being transferred by default to the associated topicref elem...

Hello,

What you want can be achieved using the following property: https://developer.mozilla.org/en-US/doc ... -transform

Regards,
Alin

Hello, In the DITA topic you can use the @outputclass attribute on a DITA element to generate a custom class on the associated HTML element in the WebHelp output. For example, the following DITA content: <p>And above all, <ph outputclass="red">remember</ph> that many flower gardens fail because they...

Hello, Your HTML fragment is not well-formed because the associated DTD contains broken references. When performing an well-formedness test in Oxygen, the check fails with the following error: https://www.oxygenxml.com/forum/files/not-well-formed-broken-dtd.png Please remove the DTD declaration and ...

Hello, Please check that the content of your file (javascript.xhtml) is well-formed. If you contribute this file using a transformation parameter, you need to set that parameter to the absolute path of the file. If you contribute the file in your Publishing Template please provide more details about...

Hello, The recommended way to change the HTML structure of the WebHelp Responsive output is to use an XSLT Extension: https://www.oxygenxml.com/doc/versions/23.0/ug-webhelp-responsive/topics/whr-responsive-override-xslt-dita-xslt-import.html This way you can override the default XSLT processing that...

Hello, You can automatically add DITAVAL profiling attributes for your use case using a custom XML Refactoring Operation (XRO): https://www.oxygenxml.com/doc/versions/23.0/ug-editor/topics/refactoring-xml-documents.html https://www.oxygenxml.com/doc/versions/23.0/ug-editor/topics/custom-refactoring-...

Hello, You can achieve this behavior by contributing a custom JavaScript that registers a 'click' event handler on each tile that opens the associated link. The procedure is described in our User Manual:https://www.oxygenxml.com/doc/versions/22.1/ug-webhelp-responsive/topics/wh-add-custom-html.html ...

Hello,

You should instruct the Publishing Template that the parameter's value represents a relative file path by setting the @type="filePath" attribute on the <parameter> element.

Regards,
Alin

Hello, You should use the following XSLT functions: fn:adjust-dateTime-to-timezone - to convert the date & time to your time zone fn:format-dateTime - to format the date & time Please update your XSLT file with the following snippet: <time datetime="{$lastModified}"> <xsl:value-of select="format-dat...

Hi Toolie, The problem is in your Publishing Template's descriptor file. You have two XSL files registered for the same XSLT Extension Point ( com.oxygenxml.webhelp.xsl.dita2webhelp ): <extension file="xslt/generation-time.xsl" id="com.oxygenxml.webhelp.xsl.dita2webhelp"/> <extension file="xslt/last...

Hi Toolie, According to your error-log.txt the transformation scenario does not promote the Saxon library bundled with Oxygen ( oxygenxml\lib\oxygen-patched-saxon-9.jar ) before the Saxon library bundled in the DITA-OT distribution ( DITA-OT3.x\lib\Saxon-HE-9.9.1-4.jar ). Please see the screenshot b...

Hello Toolie, There is no need for additional information to be included in the topics. The date and time should have been displayed at the bottom of each topic. I have retested the solution mentioned above and the timestamp is there. I have included all the resources in a sample Publishing Template...

Hello, You can use one of these two placeholders to insert a custom fragment containing the product name and version near the <whc:webhelp_publication_title/> webhelp.fragment.before.logo_and_title webhelp.fragment.after.logo_and_title You can use the map-xpath macro to extract the data from the boo...

Hello Graham, If you are setting your fragment directly as parameter value, then that fragment should be a well-formed XML fragment . In your case you should have declared the XML namespace for the whc prefix, that is: xmlns:whc="http://www.oxygenxml.com/webhelp/components" If you are using an HTML ...

Hello, This is how your XSLT extension should look like: <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:whc="http://www.oxygenxml.com/webhelp/components" xmlns:file="http://expath.org/ns/file" exclude-result-prefixes="xs file whc" v...

Hello,

You can achieve this by contributing your own custom CSS to the WebHelp Responsive output.
You can find the procedure here: https://www.oxygenxml.com/doc/versions/ ... h-css.html

Regards,
Alin

Hello, Can you please provide some detailed instructions about the context in which you replicate the issue (browser version, any particular steps you followed, search term, current publication language or anything specific that you consider might influence the search behavior)? Do you have any cust...

Hello, You can use a custom XSLT file to insert your content at the end of the topic. For example: content-after-topic.xsl <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:whc="http://www.oxygenxml.com/webhelp/components" exclude-resu...

Hello, Here are the links: 22.1: https://www.oxygenxml.com/doc/versions/22.1/ug-webhelp-responsive/topics/wh_getting_started.html#wh_getting_started__d257e55 21.1: https://www.oxygenxml.com/doc/versions/21.1/ug-webhelp-responsive/topics/wh_getting_started.html#wh_getting_started__d257e55 Regards, Alin

Hello, I have tried the scenario you have described using Oxygen WebHelp 22.1 but I couldn't reproduce the problem. Here are the resources I have used: main.ditamap : <map> <title>main</title> <topichead navtitle="x"> <topicref href="x.ditamap" format="ditamap"/> </topichead> <topichead navtitle="y"...

Hello,

To hide the Top Menu you should set the webhelp.show.top.menu parameter to no.

Regards,
Alin

Hi Syed, By design the tiles component contains only entries for the first level topics. If you want to customize it in order to display the child topics you have to contribute an XSLT extension file that overrides the built-in template that generates each tile. You can use the following XSLT snippe...

Hello, You can use the map-xpath WebHelp Macro to execute an XPath expression on the DITA map and count all the topicrefs . You can contribute your custom content using an HTML Fragment file, like the one below: <?xml version="1.0" encoding="UTF-8"?> <div xmlns:whc="http://www.oxygenxml.com/webhelp/...

Hello, There is no available setting that disables the footer of a page. However, if you want to remove the default content of the footer section, you can set the webehelp.fragment.footer parameter to " " or to "<span/>". In order to hide the footer entirely you should add a custom CSS rule to your ...

Hello, The recommended procedure for inserting additional content in your output files is via HTML fragment files and it is described here: https://www.oxygenxml.com/doc/versions/22.0/ug-webhelp-responsive/topics/wh-add-custom-html.html There are no specific placeholders for the Search Page. However...

Hy Syed, You can use an XSLT extension file to alter the HTML structure generated for the Search component. For example, the XSLT extension file may look as follows: <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:whc="http://www.oxy...