[TYPO3-english] Still problems with lighttpd (now isolated to @is_file function call difference in class.t3lib_tstemplate.php line 1163)
baekgaard at b4net.dk
Tue May 12 17:36:19 CEST 2009
OK -- fixed the problem now.
When files/templates are included by typo3, a relative document path is
used. This is meant to be relative to the root of the typo3 installation.
Thus, when the @is_file function is called, it assumes the current
working directory to be the root of the typo3 installation -- i.e. where
the index.php file resides.
I had my typo3 installation setup with symbolic links, i.e. typo3_src
was a symlink to ../typo3_src-4.2.6 and index.php was symlinked to
Under Apache, when this index.php is called up, the cwd remains the home
of the typo3 installation, say /var/www/mysite.
However, under LigthTPD, the cwd becomes the one of the "real" file,
i.e. /var/www/typo3_src-4.2.6. This is realy bad -- it will cause typo3
FE to cease working, and it will also make it difficult to host multiple
sites even if you fixed it by more symlinking...
So... I removed the symlink and just copied the index.php file
instead... et voila, now all works well as intended!
... just a warning to others that may have problems with this behaviour
of LightTPD vs. Apache. I also reported this as an "issue" (#1983)
Per Baekgaard skrev:
> Dmitry Dulepov skrev:
>> Per Baekgaard wrote:
>>> I don't have the faintest idea on why this happens. The files clearly
>>> exists and can be accessed by the process.
>>> Anyone have any hints on what is going on here?
>> What does your error_log say?
> Sorry -- as I'm sure this is a stupid question -- but I am not aware of
> any error_log. Do I need to enable some extension to make it appear, or
> is this just a setting somewhere in typo3 that I have overlooked?
> I'd surely like to be able to see any errors that may be generated...
> -- Per.
> TYPO3-english mailing list
> TYPO3-english at lists.netfielders.de
More information about the TYPO3-english