XSLT macro - Cloud
Removal notice:
Please note that the URL user and URL user password parameters were removed (see Deprecation notice: URL user and URL user password parameters). We recommend using profiles to access external data.
Features
Uses XSLT to transform XML to HTML, XHTML, or wiki markup.
Provides backward compatibility till XSLT 1.0 version.
Supports capabilities for including data similar to other scripting macros.
Supports find and replace for adjusting resulting output.
Allows administrators to restrict the usage of Javascript in the XSLT macro (based on Allow JavaScript in Configuration settings). The Confluence page throws a rendering error if this parameter is not enabled, and Javascript is inserted while using the macro.
With this release, nested macros within the XSLT macro are supported. To make this work, select the Transformed output format macro parameter as Xhtml.
Parameters
Macro editor label | Default | Description | Macro parameter |
---|---|---|---|
Transformed output format | html | Specify how the output is treated. The options are as follows:
| output |
Profile |  | Enter the profile name to be transformed. Refer to profile configuration settings to know more about profiles. Contact your Confluence administrator for further information about the profiles available in your instance. | profile name |
Location of XML code | macro body | Enter the location of data. By default, the macro transforms the code entered in the macro body.
| source |
Location of XSL code | macro body | Enter the location of XSL code. This field becomes mandatory if source XML code is entered in the macro body. By default though, the content in macro body is considered.
| style |
Find regex patterns |  | Enter a comma separated list of regex patterns to repair and modify XML prior to processing by the XSLT processor with find and replace logic. Example: (google\.dtd) | find |
Replacement strings |  | Enter a comma separated list corresponding to find patterns via index position in list. If a comma is a part of an entry, use single quotes around it. Example: http://www.google.com/$1 | replace |
Error Level | NONE | Specify the level at which the data process fails. If the XSLT transformer produces a message of this level or higher, this value determines whether the action taken by the macro. The options are:
| Â |
File encoding | system default | Specify the encoding for an external file, if different from the system default handling. Example: UTF-8. | encoding |
User id for URL connection (Removed) |  | Enter the user name for URL access via basic authentication. Removal notice: Please note that the URL user and URL user password parameters were removed (see Deprecation notice: URL user and URL user password parameters). We recommend using profiles to access external data. | user |
Password for URL connection (Removed) |  | Enter the password for URL access via basic authentication. | password |
Timeout in milliseconds | Â | Enter time in milliseconds such that URL connections do not timeout before getting data. Use this to increase time needed for slow connections. Note that if a zero is given, the connection may wait infinitely. | timeout |
XSLT Version | 1.0 | Select the version based on your style (XSLT) input document. This list box contains the XSLT versions that the macro is compatible with. | xsltVersion |
 |  | Only available when specifying XSLT macro via wiki markup. See Passing parameters to the XSLT engine below. | <transformer parameters> |
Usage
Download a copy of the cdcatalog.xsl
 from https://www.w3schools.com/xml/cdcatalog.xsl and attach it to your page.
{xslt:style=^cdcatalog.xsl}
<catalog>
<cd>
<title>Empire Burlesque</title>
<artist>Bob Dylan</artist>
<country>USA</country>
</cd>
<cd>
<title>Maggie May</title>
<artist>Rod Stewart</artist>
<country>UK</country>
</cd>
</catalog>
{xslt}
Â
{xslt:source=^cdcatalog.xml|style=#http://www.w3schools.com/xsl/cdcatalog.xsl}
{xslt}
Â
{xslt:source=xslt - basic^cdcatalog.xml|style=#http://www.w3schools.com/xsl/cdcatalog.xsl}
{xslt}
Passing parameters to the XSLT engine
Parameters that are not interpreted by the XSLT macro are passed through to XSLT. You must use wiki macro syntax to take advantage of this.
Consider the following example provided by Johan Nagels:
The output is: The value of winnersOnly is "lala"
.
If you omit the parameter, then the output is: The value of winnersOnly is "no"
.
Â
Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.