Ken McCabe

<p>The Ten&Two XSLT Processor plugin brings the power of PHP’s XSL extension to WordPress.  Once enabled, the plugin creates three (3) shortcodes – <code>[xslt_transform_xml/]</code>, <code>[xslt_select_xml/]</code>, and <code>[xslt_select_csv/]</code> – which can be used separately or in tandem to enrich your site with content from XML and CSV sources.  The plugin also enables two (2) custom post types – <code>XSL Stylesheets</code> and <code>XML Documents</code> – for managing and validating sources within WP Admin.</p>
<p>Detailed documentation and sample code can be found at https://plugins.tenandtwo.com/</p>
<h3>Custom Post Types</h3>
<p>The XSLT Processor plugin provides two (2) custom post types for managing sources within WordPress – <code>XSL Stylesheets</code> and <code>XML Documents</code>.  Both types include basic syntax validation.  XML Documents can be validated further using DTD, XSD, or RNG.  Both types are enabled in Settings > XSLT Processor Settings > Activate Content Types.</p>
<h3>Shortcode : [xslt_transform_xml/]</h3>
<pre><code>[xslt_transform_xml/] is the plugin's primary function.  This shortcode processes XML data using an XSL stylesheet, and then outputs the result as HTML, more XML, or as simple TEXT.
</code></pre>
<ul>
<li><code>[xslt_transform_xml xsl="{file|url|id|slug}" xml="{file|url|id|slug}" /]</code></li>
<li><code>[xslt_transform_xml xsl="{file|url|id|slug}"]<DATA>...</DATA>[/xslt_transform_xml]</code></li>
</ul>
<p>If either the <code>xsl</code> or <code>xml</code> parameter is left unspecified, defaults are used.  The default XML value is <code><NODATA/></code>.  The default XSL stylesheet prints all of the incoming data as HTML.  If extra attributes are specified in the shortcode – eg, <code>mykey="myval"</code> – those keys/values are passed along as parameters to the stylesheet – <code><xsl:param name="mykey"/></code>.</p>
<h3>Shortcode : [xslt_select_xml/]</h3>
<pre><code>[xslt_select_xml/] is a helper function.  It reads XML and returns a selection of the data, based on a supplied XPath expression.  There are two (2) options for specifying the XPath.  First, using the `select` attribute or, second, using the body of the shortcode.  Complex select statements with quotes, square brackets or other special syntax, should use the second pattern :
</code></pre>
<ul>
<li><code>[xslt_select_xml xml="{file|url|id|slug}" select="{XPath}" /]</code></li>
<li><code>[xslt_select_xml xml="{file|url|id|slug}"]{XPath}[/xslt_select_xml]</code></li>
</ul>
<p>If the XPath select parameter is left unspecified, the default <code>/</code> is used, which returns the entire document.  The default output is <code>format="xml"</code>.  If <code>format="json"</code> is specified, the result is encoded as a JSON string.</p>
<h3>Shortcode : [xslt_select_csv/]</h3>
<pre><code>[xslt_select_csv/] is a helper function for converting CSV file data to XML.  The result can be output directly as an HTML `<table>`, or the result can be passed to `[xslt_transform_xml/]` for further processing.
</code></pre>
<ul>
<li><code>[xslt_select_csv csv="{file|url}" /]</code></li>
<li><code>[xslt_select_csv]{csv,data}[/xslt_select_csv]</code></li>
</ul>
<p>Three (3) parameters – <code>separator</code>, <code>enclosure</code>, <code>escape</code> – control reading the input.  See PHP’s <code>fgetcsv()</code> function for details.</p>
<ul>
<li><code>[xslt_select_csv separator="," enclosure="\"" escape="\\" /]</code></li>
</ul>
<p>Two (2) parameters – <code>key_row</code>, <code>col</code> – control writing columns to the output.  The <code>key_row</code> attribute is optional, but allows labels from that row to be used in <code>col</code> and <code>key_col</code>.</p>
<ul>
<li><code>[xslt_select_csv key_row="{num}" col="{num|letter|label}+" /]</code></li>
</ul>
<p>Three (3) parameters – <code>row</code>, <code>key_col</code>, <code>key</code> – control writing rows to the output.</p>
<ul>
<li><code>[xslt_select_csv row="{num}+" /]</code></li>
<li><code>[xslt_select_csv key_col="{num|letter|label}" key="{val}+" /]</code></li>
</ul>
<h3>Nested Shortcodes</h3>
<p>Combine <code>[xslt_transform_xml]</code> with <code>[xslt_select_xml]</code> :</p>
<ul>
<li><code>[xslt_transform_xml][xslt_select_xml/][/xslt_transform_xml]</code></li>
</ul>
<p>Combine <code>[xslt_transform_xml]</code> with <code>[xslt_select_csv]</code> :</p>
<ul>
<li><code>[xslt_transform_xml][xslt_select_csv/][/xslt_transform_xml]</code></li>
</ul>
<p>Combine <code>[xslt_transform_xml]</code> with itself using <code>[/xslt_transform_alias]</code> (WP does not support nested shortcodes with identical names) :</p>
<ul>
<li><code>[xslt_transform_alias][xslt_transform_xml/][/xslt_transform_alias]</code></li>
</ul>
<p>Combine multiple shortcodes/sources to create a single <code>XML Document</code> (see Custom Post Types above) :</p>
<ul>
<li><code><DATA><PART1>[xslt_select_xml xml="f1.xml" /]</PART1><PART2>[xslt_select_xml xml="f2.xml" /]</PART2></DATA></code></li>
</ul>
<h3>Cache Parameters</h3>
<p>When a shortcode specifies a remote file – <code>xml="{url}"</code> or <code>csv="{url}"</code> – that source is cached locally using WP Transients. The default cache duration is set in the XSLT Processor Settings.  To override the default, add <code>cache="{minutes}"</code> to the shortcode.</p>
<ul>
<li><code>[xslt_transform_xml xml="{url}" cache="{minutes}" /]</code></li>
<li><code>[xslt_select_xml xml="{url}" cache="{minutes}" /]</code></li>
<li><code>[xslt_select_csv csv="{url}" cache="{minutes}" /]</code></li>
</ul>
<h3>Namespace Parameters</h3>
<p>Within <code>[xslt_select_xml/]</code> the plugin provides two (2) methods for handling XML containing namespaces.  The first is to add <code>strip-namespaces</code> to the shortcode.  The second method is to add the needed prefixes and namespace URIs using <code>xslns</code>.</p>
<ul>
<li><code>[xslt_select_xml xml="{file}" strip-namespaces="yes" select="//node" /]</code></li>
<li><code>[xslt_select_xml xml="{file}" xmlns="ns1" ns1="{namespace-uri-1}" select="//ns1:node" /]</code></li>
<li><code>[xslt_select_xml xml="{file}" xmlns="ns1 ns2" ns1="{namespace-uri-1}" ns2="{namespace-uri-2}" select="//ns1:node/ns2:node" /]</code></li>
</ul>
<h3>WP-CLI</h3>
<p>All three (3) shortcodes have command-line equivalents. They can be used, for instance, to run quick tests. Or they can be used, by piping the outputs into files, to pre-generate results.</p>
<ul>
<li>
<pre><code>wp xslt transform_xml
    --xsl='{file|url|id|slug}'
    --xml='{file|url|id|slug}'
    --cache='{minutes, if xsl|xml={url}}'
    --tidy='{yes|html}' or tidy or --tidy='xml'
    --{myparam}='{myvalue}'
    --outfile='{filepath}'
    --htmlentities or --htmlentities='yes'
</code></pre>
</li>
<li>
<pre><code>wp xslt select_xml
    --xml='{file|url|id|slug}'
    --cache='{minutes, if xml={url}}'
    --select='{xpath}'
    --root='{nodename|empty}'
    --tidy='{yes|html}' or tidy or --tidy='xml'
    --strip-namespaces='yes' or strip-namespaces
    --strip-declaration='no'
    --format='{xml|json}'
    --htmlentities or --htmlentities='yes'
</code></pre>
</li>
<li>
<pre><code>wp xslt select_csv
    --csv='{file|url}'
    --cache='{minutes, if csv={url}}'
    --separator=','
    --enclosure='\"'
    --escape='\\'
    --key_row='{row number for column labels}'
    --col='{return column number(s), letter(s), or label(s)}'
    --key_col='{col number, letter, or label for key matching}'
    --key='{value(s) for key_col matching}'
    --row='{return row number(s)}'
    --class='{css classname(s) for result table}'
    --htmlentities or --htmlentities='yes'
</code></pre>
</li>
</ul>
<h3>XSL Stylesheets</h3>
<p>The XSLT Processor plugin includes a number of useful XSL templates that you can include and use in your own projects. They are grouped into five files.</p>
<ul>
<li>date.xsl : <code>date-format</code>, <code>date-microtime</code></li>
<li>file.xsl : <code>file-exists-local</code>, <code>file-exists-remote</code></li>
<li>string.xsl : <code>string-replace</code>, <code>string-upper</code>, <code>string-lower</code>, <code>string-title-case</code>, <code>string-trim</code>, <code>string-rtrim</code>, <code>string-ltrim</code>, <code>string-maxlength</code>, <code>string-maxwords</code>, <code>string-add-slashes</code>, <code>string-urlencode</code>, <code>string-strip-tags</code>, <code>string-nl2br</code>, <code>string-entity-decode</code>, <code>string-to-nodeset</code></li>
<li>util.xsl : <code>util-bytsize</code>, <code>util-hash-data</code>, <code>util-print-nodes</code>, <code>util-print-node-names</code>, <code>util-super-global</code></li>
<li>wp.xsl : <code>wp-select-xml</code>, <code>wp-select-csv</code>, <code>wp-post-item</code>, <code>wp-post-meta</code>, <code>wp-sanitize-title</code>, <code>wp-size-format</code></li>
</ul>
<h3>Requirements</h3>
<p>The Ten&Two XSLT Processor plugin relies upon PHP’s XSL extension.  If the extension is installed, the XSLT Processor Settings screen will display a message similar to the first message below.  If <code>LIBXSLT_VERSION</code> is undefined, all plugin options are disabled automatically and the second message is displayed.</p>
<ul>
<li><code>PHP's XSL extension is available : XSLT v1.1.32, EXSLT v1.1.32, LIBXML v2.9.4</code></li>
<li><code>PHP's XSL extension is NOT available</code></li>
</ul>
<p>The XSL extension’s requirements are detailed at php.net – https://www.php.net/manual/en/book.xsl.php</p>
<blockquote>
<p>“This extension requires the libxml PHP extension. This means passing the –with-libxml,<br />
  or prior to PHP 7.4 the –enable-libxml, configuration flag, although this is implicitly<br />
  accomplished because libxml is enabled by default.</p>
<p>This extension uses libxslt which can be found at » http://xmlsoft.org/XSLT/. libxslt<br />
  version 1.1.0 or greater is required.”</p>
</blockquote>


Ten&Two XSLT Processor

Transform and display XML from local and remote sources using PHP's XSL extension.

hsfr

<p>Paloose is a simplified version of Cocoon using PHP5. The original was a simple server working with Apache<br />
to allow a Cocoon environment to be used with PHP5. There are very few ISPs who will<br />
support Java/Tomcat for web sites which Cocoon requires, other than as a very<br />
expensive “professional” addition. Almost all will support PHP5 (sorry, Paloose does not use PHP4) and I have<br />
been using Paloose for some time now and have always found it a good substitute for Cocoon in<br />
all but the most complex sites. Paloose may also encourage others to start using XML and XSL<br />
without having to use extra bits such as Tomcat, Jetty or a full Cocoon installation.</p>
<p>Please note that the technology underlying Paloose does not make it suitable for very large sites. If you<br />
need performance then upgrade to Cocoon — the extra expense of an updated server account<br />
will probably be unnoticeable in the overall cost of<br />
a large site anyway. However, having the ability to try out XML and XSL ideas in a PHP environment with a<br />
subset of Cocoon is very useful.</p>
<p>The Paloose client plugin for WordPress allows the latter to interrogate XML based file systems and integrate them with<br />
normal WordPress pages. There also some non-XML transforms (for example GEDCOM) and it is fairly easy to write<br />
your own extensions to Paloose. The client and server versions of Paloose are identical with only the<br />
wrapper code within the plugin being different.</p>
<p>For more information, visit the <a href="http://www.paloose.org/" rel="nofollow ugc">Paloose project page</a>. All comments appreciated.</p>
<h3>Usage Manual</h3>
<p>Briefly you insert a template tag of the form</p>
<p><?php echo paloose( <page_required>, <query_string> ); ?></p>
<p>However you need to understand what Paloose will do with this before you start.<br />
Consult the <a href="http://www.paloose.org/pp/documentation/wordpress.html" rel="nofollow ugc">Paloose documentation here</a><br />
and especially the <a href="http://www.paloose.org/pp/examples/wordpress/wordpress.html" rel="nofollow ugc">Paloose WordPress Example</a>.</p>


Paloose XML Processor

A means of handling XML files in a similar fashion to Cocoon with sitemaps and XSL transforms.

Ten&Two XSLT Processor vs Paloose XML Processor