loading file '/templates/html/index.xsl' failed.

[georgbez]

[04.10.2013 - 11:56:51] Starting generator

Oups... phpDox encountered a problem and has terminated!
It most likely means you've found a bug, so please file a report for this and paste the stacktrace (if given) along!

Exception: TheSeer\fDOM\fDOMException
Location: phar://C:/xampp/php/phpdox.phar/fDOMDocument-1.3.2/TheSeer/fDOMDocument/fDOMDocument.php (Line 137)

loading file '/templates/html/index.xsl' failed.

[XML-STRING] [Line: 0 - Column: 0] Warning 1549: failed to load external entity "file:///C:/templates/html/index.xsl"
#0 phar://C:/xampp/php/phpdox.phar/phpdox/generator/engine/html/Html.php(80): TheSeer\phpDox\Generator\Engine\AbstractEngine->getXSLTProcess

or()
#1 phar://C:/xampp/php/phpdox.phar/phpdox/generator/engine/html/Html.php(94): TheSeer\phpDox\Generator\Engine\Html->getXSLTProcessor()
#2 phar://C:/xampp/php/phpdox.phar/phpdox/generator/engine/html/Html.php(76): TheSeer\phpDox\Generator\Engine\Html->buildStart()
#3 phar://C:/xampp/php/phpdox.phar/phpdox/generator/Generator.php(151): TheSeer\phpDox\Generator\Engine\Html->handle()
#4 phar://C:/xampp/php/phpdox.phar/phpdox/generator/Generator.php(133): TheSeer\phpDox\Generator\Generator->triggerEvent()
#5 phar://C:/xampp/php/phpdox.phar/phpdox/Application.php(182): TheSeer\phpDox\Generator\Generator->run()
#6 phar://C:/xampp/php/phpdox.phar/phpdox/CLI.php(136): TheSeer\phpDox\Application->runGenerator()
#7 C:\xampp\php\phpdox.phar(406): TheSeer\phpDox\CLI->run()

[chernjie]

I have the same issue on Ubuntu. I suspect it might have something to do with some misconfiguration on my phpdox.xml file.

                ${phpDox.home}            Directory of the phpDox installation
                <template dir="${phpDox.home}/templates/html" />

[theseer]

@chernjie: That's most probably a problem with resolving ${phpDox.home}.
When using phpDox as phar, this is the known issue #105 that has been fixed in git.

[chernjie]

Thanks @theseer. I think this issue can be closed now :+1

[theseer]

This problem should be fixed in the 0.6 release.
Please reopen / comment on this issue in case it re-appears.