No output *at all* vom s9y anymore
Posted: Fri Oct 23, 2009 12:02 pm
Hi!
Today after I've edited (tried to use a symlink) a template file s9y totally stopped producing ANY output.
Even the administration pages are blank.
It does not produce any errors (server- and php-errorlog only show some warnings about timezone settings) either.
template_c is writable and smarty does produce files here - but appart from an HTML comment they don't contain any content.
I already tried a backup and upgrading to 1.4.1. To no avail.
Tried re-installing 1.4.1 - and the second the installation is over I'm back to blank screens.
Using php 5.3.0 on lighttpd on a rootserver - didn't touch anything on the server though.
*any* ideas?
edit: everything else on that server, including a different s9y installation(!), runs perfectly fine.
edit2: setting the working s9y installation to use the database of the defunct one produces no output, too. So there must be something blown up in the tables. No errors though. any ideas?
edit3: reverting to PHP5.2.11 seems to have solved this issue.. probably a strange PHP 5.3.0 bug.
Thanks, sorry, close.
Today after I've edited (tried to use a symlink) a template file s9y totally stopped producing ANY output.
Even the administration pages are blank.
It does not produce any errors (server- and php-errorlog only show some warnings about timezone settings) either.
template_c is writable and smarty does produce files here - but appart from an HTML comment they don't contain any content.
I already tried a backup and upgrading to 1.4.1. To no avail.
Tried re-installing 1.4.1 - and the second the installation is over I'm back to blank screens.
Using php 5.3.0 on lighttpd on a rootserver - didn't touch anything on the server though.
*any* ideas?
edit: everything else on that server, including a different s9y installation(!), runs perfectly fine.
edit2: setting the working s9y installation to use the database of the defunct one produces no output, too. So there must be something blown up in the tables. No errors though. any ideas?
edit3: reverting to PHP5.2.11 seems to have solved this issue.. probably a strange PHP 5.3.0 bug.
Thanks, sorry, close.