On Mon, 18 Dec 2006 18:36:22 +0100
Christian Welzel <[EMAIL PROTECTED]> wrote:
> Am Montag, 18. Dezember 2006 08:28 schrieb Clayton:
>
> > Thanks for the try, but that link was just fine. I then got a little
> > progress by adding a tslib/ directory under typo3_src-4.0, but
> > alas, just a little progress....
>
> Typo3 4.0 does not need neither tslib nor a link to tslib in the
> src-directory anymore.
>
> > Instead of the "Cannot find tslib/" brick wall, after this my two
> > typo3 instances (with separate /var/www/typo3-...
> > and /etc/typo3-.... and
>
> The current Typo3 packages do not support the creation of two
> different typo3 installations.
> If you got this working its fine, but the packages do not anything to
> respect those settings.
> For further help please provide complete information about your
> installations. (dir-listing, links, etc).
>
> > Is this new version of typo3 looking for localconf.php in some new
> > place?
>
> No, the localconf.php file is searched for
> in /etc/typo3-dummy/localconf.php.
I have been picking and poking at this problem for days now. I still am not
sure exactly what the problem was or what was changed/broken by the software
update, but I have gotten everything working again by deleting all the Debian
packages and downloading the latest 4.0.4 source directly from the typo3
website.
And then deleting all the configuration from the Debian-provided
/etc/typo3-dummy/apache.conf such that the final result looks like this:
<VirtualHost *:80>
ServerName www.ckintl.biz
ServerAlias ckintl ckintl.biz *.ckintl.biz
ServerAdmin [EMAIL PROTECTED]
DocumentRoot /var/www/typo3-ckintl
CustomLog /var/log/apache2/access.log combined
</VirtualHost>
The "alias /typo3 /var/www/typo3-ckintl" (I might not be remembering this
exactly correctly) was causing me all sorts of grief and may have been the
biggest source of problems, namely frontend worked for both my typo3 instances
but I always seemed to end up with one backend pointing at the OTHER site's
backend. In retrospect, if I had to guess what the biggest source of my
difficulties was, it was probably that "alias /typo3 /var/www/typo3-xxxxxx"
line in both versions of apache.conf.
I don't have the stomach right now to go back and try to verify that hypothesis
on my server right now, but if you want I can try on another machine in a
couple weeks when I return from vacation.
Clayton
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
