#19062 [Opn->Csd]: Display Sablotron version number to help diagnose problems

ID: 19062 Updated by: sniper@php.net Reported By: pmoulding@tedis.com.au -Status: Open +Status: Closed Bug Type: Sablotron XSL Operating System: Solaris and Linux PHP Version: 4.2.2 New Comment: Someone just recently added xslt_backend_version() and xslt_backend_name() in CVS..just try this snapshot: http://snaps.php.net/php4-latest.tar.gz Previous Comments: ------------------------------------------------------------------------ [2002-08-23 01:22:36] pmoulding@tedis.com.au I use PHP XSLT on Solaris, Linux, NT, and Windows 2000. On NT and Windows 2000 the version of Sablotron is usually in sync with PHP because they are installed form the same binary. On Linux and Solaris they may be miles apart because Sablotron is not automatically updated with PHP. phpinfo() does not display the Sablotron release so I do not know if the problems are caused by Sablotron being out of date. In cased where I do not have administrative access, 78.45301% of the time, I cannot tell why Sablotron is refusing to process XSLT that works on other servers. If phpinfo() reported the Sablotron release, that would be a help. The alternative might be an xslt_info(). One thing I noticed on a server with a recent PHP, one that uses the new XSLT interface to Sablotron, and an older version of Sablotron, was the lack of error messages. There were many cases where the XSLT process returned false but there were no error messages. I ripped out a few hairs before realising it might be an old Sablotron release. If this suggestion is not feasible then perhaps we could have a note on the PHP XSLT page along the lines of "PHP 4.2.2 tested with Sablotron 0.95". ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=19062&edit=1