TYPO3 Core

Thanks for your interest.

Do you mean the TYPO3 extension DBAL? No, I downloaded the sources and the dummy package from typo3.org/downloads. I am using MySQL:

> mysql --version
mysql  Ver 14.14 Distrib 5.5.34, for debian-linux-gnu (x86_64) using readline 6.2

kind regarts

The extension DBAL is already included in the TYPO3 sources you downloaded. What Markus wants to know is: In the TYPO3 Backend, go to the Extension Manager and check the list of extensions. Is DBAL installed or is it not?

I had the same problem and since the install tool step fail (db connection cannot establish), we don't have the backend to check.

But checking the generated LocalConfiguration.php, it seems that DBAL is still activated.

        'EXT' => array(
                'extListArray' => array(
                        .......,
                        .......,
                        'adodb',
                        'dbal',
                ),
        ),
        'EXTCONF' => array(
                'dbal' => array(
                        'handlerCfg' => array(
                                '_DEFAULT' => array(
                                        'config' => array(
                                                'driver' => NULL,
                                                0 => '',
                                        ),
                                        'type' => 'adodb',
                                ),
                        ),
                ),
        ),

Deactivate dbal from there, everything is working fine. So it's the problem from Install Tool that didn't remove dbal properly.

Just experienced this on 6.1.8-dev with latest dummy package.
Installed sources as per usual, went to URL to begin installation, got jumped to step 1 in URL (Was not given chance to enter database details).

Found this ticket, removed dbal from LocalConfiguration, altered URL to step 0 and proceeded with installation.

Fell down at step 2, added the socket, port and username./host information to the LocalConfiguration.php and managed to convince the installer to continue.

We had a lot of the issues reported here when installing on the latest Ubuntu releases (with whatever MySQL/MariaDB that comes with). Installations on Debian Wheezy did not have any issues.

Additional information: https://github.com/Ecodev/bootstrap_package/issues/57

For the "dbal redirect loop" I created a new issue: #55252

The point "dbal blocks Database settings" seams to be solved, when the redirect works correctly, but I will let this issue open at the moment.