Hello, You can use the " webhelp.fragment.welcome " HTML Fragment extension point. You can find more information in our User Manual about Inserting Custom HTML content in the WebHelp Responsive output: https://www.oxygenxml.com/doc/versions/21.1/ug-webhelp-responsive/topics/wh-add-custom-h...

Hello, This is a known issue which has already been resolved in the upcoming version. To overcome this problem you can use the following custom CSS rule in your WebHelp output: .wh-tooltip-container .wh-tooltip, .wh_breadcrumb .topicref .wh-tooltip, .wh_publication_toc .topicref .wh-tooltip { displa...

Hello,

In order to avoid XML well-formedness errors you should wrap the JavaScript content of the <script> element using XML Comment markup.
For example:
Regards,
Alin

Hello, The issue can be fixed by including the following CSS snippet into your generated output: .wh-tooltip-container .wh-tooltip, .wh_breadcrumb .topicref .wh-tooltip, .wh_publication_toc .topicref .wh-tooltip { display: block; } The procedure of using CSS to customize the output is described in o...

Hello, Can you please give us more details about your customization. More specifically, how did you include the JS that retrieves the data from local storage in your output files? Are there any JS errors the browser's console? Also, we would need to know which version of Webhelp are you using. Regar...

Hello, You can use the webhelp.custom.resources parameter and set it to the path of a directory containing the resources that you want to copy to the output folder. All the resources will be copied to the root directory of the Webhelp output. Please see the Copying Additional Resources to the Output...

Hello, You need to adjust your XPath expression in order to concatenate all keywords using a space as separator: <div class="keywords" xmlns:whc="http://www.oxygenxml.com/webhelp/components"> <p>Keywords: <b><whc:macro value="${topic-xpath(string-join(//keyword, ' '))}"...

Hello,

Thank you for reporting this issue. I have logged it in our system and a fix will be available in the next Webhelp release.


Regards,

Alin

With the XPath command map/topicref/topicref/topicmeta/audience/@type it is possible to get the desired result, namely "expert". When I try to achieve the same within sidetoc.xsl with //toc:toc/toc:topic/toc:topic/toc:topicmeta/toc:audience/@type I get the @type values from parents and si...

Hello, You can add custom HTML content in the WebHelp Responsive output by inserting it in a well-formed XML file that will be referenced in the transformation (either from an Oxygen Publishing Template or using one of the HTML fragment parameters ). The XML file can use WebHelp macros, which are va...

Hello,

We managed to reproduce the issue on our side and I have logged it in our issue tracking system.
We will let you know when a solution is available.

Regards,
Alin

Hello, It seems that you are using a custom publishing template that was created starting from one of the templates in v. 20.1 or older. If your custom publishing template contains Custom HTML Page Layout Files please use the following procedure in our User Manual to update the layout files to versi...

Hello, Did you manually copy the HTML Page Layout Files (HTML page templates) in your custom template? If yes, I suppose that you have omitted two additional files that are referenced from the page layout files. These are header.xml and footer.xml and they are not optional. Can you please check that...

Hello, Can you please try to use the following fragment: <whc:macro value="${topic-xpath(if (normalize-space(string-join((//attribute::product), '')) != '') then string-join(('Note: The feature described above is available from release' , //attribute::product), ' ') else '')}"/> Regards, A...

Hello, You can retrieve metedata info from your input map using the macros template components: https://www.oxygenxml.com/doc/versions/20.1/ug-webhelp-responsive/topics/wh-add-custom-html.html#wh-add-custom-html__using_webhelp_macros_inside_a_html_fragment_file. You can add content before and after ...

Hello,

Thank you for reporting this issue. I managed to reproduce the problem and I have logged it in our issue management system to be analyzed (ticket ID: WH-2115).

Regards,
Alin

Hello, I think that the Publishing Template's macros mechanism might help you. The macros are variables that you can use in the HTML Layout Files (https://www.oxygenxml.com/doc/versions/20.1/ug-editor/topics/whr_publishing_template_contents.html#ariaid-title4) or in the HTML Fragment Files (https://...

Hello, In case of the WebHelp Responsive transformation you can use the new template whc:macro component to execute XPath expressions in the context of the DITA map. You can use the whc:macro components in a template HTML Page layout file or in an HTML fragment file . You can read more about macros ...

Hi Julie, The problem is that the '${oxygen-webhelp-output-dir}' macro is expanded by the WebHelp plugin only when it is used in an attribute value. In your case, the macro from the value that is assigned to top.location will not be replaced by the actual path to the output directory. However, in Ox...

Hello, The JavaScript file referenced using the "<js-amd-module/>" element will only be loaded as an AMD module using a "require" call. Furthermore, this JS file should reside in the Publishing Template's root directory. This means that it should be located in the same directory ...

Hello, Thank you for your feedback. I have submitted a task to our documentation team to update the WebHelp macros related topic in our User Guide. You are right. You can use the <whc:macro/> component to expand a ${macro} value in a text node. The <whc:macro/> component can be used in inline JavaSc...

Hello, Supposing that your template directory would look like this: [js-modules] --- the Publishing Template base dir - [js] - [datatables] - datatables.min.js - tables.js - template-main.js The tables.js should look as follows: define(["jquery", "localization", "./datatable...

Hello,

Unfortunately you cannot move the related links without modifying the topic HTML template file. I will log your request in our issue tracking system to be analyzed.

Regards,
Alin

Hello, I hope I have correctly understood your use case. Please correct me if I am wrong. So, you are trying to customize the content of the footer sections in the WebHelp Responsive output HTML pages. I understand that your custom content is not static and you need to regenerate it at each transfor...

Hello, You cannot use XSLT fragments directly in the DITA sources. If you want to customize the PDF output you can have a look at this topic in our User Manual: https://www.oxygenxml.com/doc/versions/20.0/ug-editor/topics/dita_pdf_output_customization.html You can also read more about this subject i...

Hello, There is no out of the box setting that would allow you to insert the current date or time in the generated output. However, for the WebHelp Responsive output, you can achieve this behavior by contributing a custom XSLT extension stylesheet. You can use the following example as starting point...

Hello, Unfortunately, you cannot rerun the WebHelp indexer after the output has been generated. The WebHelp search engine indexes all HTML files found in its output directory. The only way you could force the WebHelp plugin to index your custom HTML files is to manually copy them in the WebHelp's ou...

Hello, There is no predefined option (parameter) that would allow you to instruct the WebHelp plugin to not escape the XML special characters (&, <, >, etc.). The content of the file referenced using the "webhelp.head.script" parameter is included in the output HTML files via XSLT. Whe...

Hello,

You should place your JS content inside an XML comment (<!-- -->): Regards,
Alin

Hello, We're created a customization of the responsive webhelp plugin where we run custom XSLT tasks for generating HTML fragments with localized texts (such as "Last updated" in the footer) from the webhelp localization framework. Is there any easier way to do this, especially with the ne...