Edit online

Adding Oxygen Feedback to WebHelp Generated from a Command Line

To install Oxygen Feedback in your WebHelp output generated using a transformation from a command line (using the Oxygen XML WebHelp plugin or Oxygen Publishing Engine), use this procedure:

Prerequisites

You must have a licensed version of Oxygen XML WebHelp or Oxygen Publishing Engine.
To install and manage Oxygen Feedback Enterprise, you will need to choose a subscription plan during the installation procedure. To see the subscription plans prior to installing the product, go to: https://www.oxygenxml.com/oxygen_feedback/buy_feedback.html.
Notice: If your subscription expires or if the number of page views allowed by your plan is exceeded for a particular month, you will receive a notification and the comments component will be disabled until the subscription is renewed/upgraded or until the end of the month (in the case of exceeding the page views limit). If an expired subscription is not renewed, the comments are still visible for a limited period of time (e.g. 2 weeks). After that, they will no longer be displayed.

Installation Procedure

Log in to your Feedback account from the login page (https://feedback.oxygenxml.com/login). You can click on Log in with Google or Log in with Facebook to create an account using your Google or Facebook credentials or click the Sign Up tab to create an account using your name and email address.
Step Result: If this is your first time logging in and you have not yet created a site configuration, you are directed to a Welcome page. Otherwise, you are directed to the Dashboard page.
Click the Add your first site button to create a site configuration.
In the Settings page, enter a Name and Description for the site configuration. Some optional settings can be adjusted according to your needs. For more details, see the Settings Page topic. Click Continue.
In the Version page, you must specify a version and the base URL from your website where the WebHelp output is deployed. The Name field is where you specify the version name or identifier. This is helpful if there will be multiple versions for your output. For example, if your published output is documentation for a product that has multiple released versions, each version probably has its own published documentation. In this case, each published version requires a different configuration since the version and base URL would be different for each of them.

The Site base URL field is where you specify the base URL for the website where you publish your output. For WebHelp output, for example, it is the URL where your WebHelp output is deployed. Comments will only be displayed on pages within the hierarchy of the specified base URL. For more details, see the Version Page topic. Click Continue.
In the Installation page, choose the Install Feedback in WebHelp output generated from a command line option.
Create an XML file (for example, feedback-install.xml) on disk with the content generated in that Installation page.
Reference the file you just created in a command-line transformation. There are several options for doing this:
- Specify the path to the newly created XML file using the webhelp.fragment.feedback parameter in your command-line script:
```
dita.bat
...[Other parameters]...
-Dwebhelp.fragment.feedback=c:\path\to\feedback-install.xml
```
- Specify the path to the newly created XML file using an Oxygen Publishing Template:
  1. Create a Publishing Template, if you have not already done so. If you need help, see Working with Publishing Templates.
  2. Copy the newly created XML file to a folder inside the publishing template's root folder.
  3. Open the template descriptor file associated with your publishing template and add a reference to the newly created XML file in the html-fragments section.
```
<publishing-template>
 ...    
  <html-fragments>
    <fragment file="custom-template/feedback-install.xml" 
     placeholder="webhelp.fragment.feedback"/>
  </html-fragments>
```
  4. Reference the Publishing Template in your command-line script using one of the procedures found here (depending on whether your template has one descriptor file or multiple files).
Run the transformation and deploy the WebHelp output to a web server.