Configuring XSL Formatter module

Some usage examples.

You will
  1. Construct a content type, eg "Updates".
  2. Attach a field to that content type to hold the XML data.
  3. Edit the display settings to provide an XSL template that transforms the XML into something readable.

Configuration

  1. Enable the XSL formatter module. This provides a new 'Format' called "Transformed by XSL" that can be applied to text, file and link field types.
  2. Create or edit your chosen content type. ( Home » Administration » Structure » Content types ) to add your field.

    Content type Manage Fields UI

  3. "Manage Display" of your content type, and select "Transformed by XSL" as the format. In the display settings, choose or upload your XSL file.

    Content type Manage Display UI

    Uploaded XSL files will be available for re-use in other fields.
  4. It's recommended to start by choosing one of the 'verbatim' or 'pretty-print' XSL files that comes with the project before adding your own. This will demonstrate how the base system works before introducing the complexity of XSL debugging.

Troubleshooting

XML and XSL are very picky syntaxes, and it's easy for things to go wrong. Debugging info should be available in the Watchdog logs, with explanations of errors found during parsing.

Using the remote URL source for your data can be problematic. A network request to the original is made on each pageload, and if the target is slow or offline, your page will be also.!
The module uses the DOMDocument::load function directly, so all issues related to that apply. No additional headers, proxy configs or authentication are supported here.

As this request happens in realtime (on render request) it can be terribly inefficient if you display this field in a list of views or anything.
Drupal-level caching *may* help somewhat, but for performance you are probably better to switch to using Feeds module (plus Feeds XPath Parser) to do your XML importing instead.