[TYPO3-core] RFC #16172: Accessing FE in fresh install fails with RuntimeException "No database selected"

[Ernesto Baschny [cron IT]]

Hi,

Lars Peipmann schrieb am 29.10.2010 18:07:

> this is a SVN patch request with a new version.
> 
> Type: Bugfix
> 
> Branches: Trunk
> 
> Bugtracker references:
> http://bugs.typo3.org/view.php?id=16172
> 
> Problem:
> In 0015576 a new Exception-Handler was implemented. In the current trunk
> it will used for the the errors on connecting to the database in the
> Frontend. In the past there was a error message without the php-methode
> "exit". The error-message was shown a part of second and then typo3
> redirected to the install tool in a fresh install. And now there is no
> redirect after the RuntimeException.
> 
> Solution:
> If database host and database is not defined typo3 jumps automatically
> into 1-2-3 Install Tool. Those two values are essential for the database
> connection. If they are not defined, it should be a new typo3 website
> without installation.

I could reproduce that with the dummy package at last. Thanks for your
contribution Lars (back from the code sprint...). :)

What about the solution in the attached patch (v2), which gets rid of
that JavaScript redirect and instead does a direct HTTP redirect? The
Exception is useless, and would hinder the redirect, because it sends a
HTTP 500. Since this is the normal route of installing the product it
doesn't need to be an "Exception" anyway.

Anyway +1 on reading and testing both variants, the last core reviewer
that will commit should choose the one that he likes more.

Cheers,
Ernesto
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 16172_v2.diff
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20110109/baf899ac/attachment.asc>