This is a static dump of issues in the old "Flyspray" bugtracker for DokuWiki. Bugs and feature requests
are now tracked at the issue tracker at Github.
Closed
Works for me
FS#737 css.php and js.php not working in safe mode
Backend
2006-03-07Andrea
I have tried the latest release on my usual host and I have found that two files use functions "disabled for security reasons".
Note that I have run the previous versions on the same host for some time, with no problem.
css.php fails with warnings:
<b>Warning</b>: parse_ini_file() has been disabled for security reasons in <b>/home/xxxxx/wiki/lib/exe/css.php</b> on line <b>41</b><br />
<br />
<b>Warning</b>: Invalid argument supplied for foreach() in <b>/home/xxxxx/wiki/lib/exe/css.php</b> on line <b>42</b><br />
<br />
<b>Warning</b>: readfile() has been disabled for security reasons in <b>/home/xxxx/wiki/lib/exe/css.php</b> on line <b>72</b><br />
js.php fails with warnings:
<b>Warning</b>: readfile() has been disabled for security reasons in <b>/home/xxxxx/wiki/lib/exe/js.php</b> on line <b>60</b><br />
I've tried to grep for those two functions:
parse_ini_file() seems to be used only in ./lib/exe/css.php;
readfile() seems to be used in: ./lib/exe/css.php ./lib/exe/js.php ./inc/feedcreator.class.php
2006-03-09andi
Though both functions could be easily replaced by pure PHP functions I can not try to work around any crippled PHP installation out there. If you pay your hoster for full PHP support ask him to give what you pay for. If you use a free hoster you can do one of the following things:
1) replace those functions yourself
2) run the old release
3) lokk fo a better hoster
2006-03-09andi
BTW. that those functions are not avialable is not because of enabled safe_mode restrictions but because your hoster disabled those functions explicitly.
2006-03-12Andrea
You are right, it was not really related to safe mode.
I solved the problem with my hoster.