TYPO3 Core

Cannot reproduce the bug. However I can see that DBAL does not deactivate itself automatically anymore.

See bug #16678

Hi Daniel,

Please wait until tomorrow night when I've committed #16444 and #16679. Make sure you use TYPO3 Core trunk, then:

1) Go to typo3/sysext/
2) rename dbal into dbal.ORIG
3) check out DBAL trunk into typo3/sysext:

svn co https://svn.typo3.org/TYPO3v4/Extensions/dbal/trunk dbal

Test again and report here if bug is stil there.

You may of course patch Core yourself with aforementioned bug ids (do not miss the DBAL part with #16679) and thus not wait until tomorrow :-)

Patches were committed, manual patching is not needed anymore

This bug will be closed around Christmas if there is no confirmation that this bug still occurs.

Hi Xavier,

Just checked out the full trunk, cleared the cached files without any success.
Even replaced the DBAL with the one from the trunk to be sure...

Still the same error, tell me if I did anything wrong.
Thanks by the way.

Hi Daniel,

Please mail me screenshots of the whole install process up to the error and the output of

phpinfo();

you may consider attaching them here too, it's up to you.

Thanks. I do not understand how to reproduce but hopefully your additional info will help be tracking down the problem.

After doing a few quick tests on your environment, this sounds like you entered invalid credentials with your DB connection setup and this crashes the install tool.

I wonder why you have DBAL active as you don't see to support it (I mean you seem only to support MySQL anyway). Did you activate it manually?

I changed this bug to make it a feature request for Install Tool that should not crash as dramatically as it does currently when invalid DB parameters are provided.

Just tested current trunk (~ 4.5 RC1) with Oracle and I cannot reproduce this anymore. A nice message is shown meaning invalid credentials do not crash install tool anymore.

Could you confirm please?

Just got the final version of TYPO3 4.5.0. After I gave the correct database parameters, it ended up with the same error message. After I changed following line in the typo3conf/localconf.php from:

$TYPO3_CONF_VARS['EXTCONF']['dbal']['handlerCfg'] = array('_DEFAULT' => array('type' => 'adodb','config' => array('driver' => '',)));;

to (notice the type => native)

$TYPO3_CONF_VARS['EXTCONF']['dbal']['handlerCfg'] = array('_DEFAULT' => array('type' => 'native','config' => array('driver' => '',)));;

it all worked out.

This error occured also in an fresh installation in the TYPO3 4.5.0 final.

I have tried to intall from dummy and source package, downloaded from typo3.org on 29.01.2011.

The dbal bug is an dependency on the adodb extension for php5. Without the extension installed the error occured. When I install the adodb php extension the installation worked perfectly.

But I think that is not a good solution. Because many hosters do not install all the php extensions.

I could be wrong, but it would be interesting to see the database driver "string" while doing install. Maybe its empty in these cases?

If i see the topic and i check the source it has to be this kind of message

ADONewConnection: Unable to load database driver '$db'

$db is missing here, or ?

@Andy - This should also work for mysql i think:

$TYPO3_CONF_VARS['EXTCONF']['dbal']['handlerCfg'] = array (
'_DEFAULT' => array (
'type' => 'adodb',
'config' => array(
'driver' => 'mysql',
)
)
);

I got the same:
- new TYPO3 4.5, install tool, entered correct DB credentials -> always said: incorrect credentials...

when I inserted the missing db-name in the localconf manually, everything worked...

You all seem to use MySQL as database, is it true? Could you confirm that you actually don't want/need to use DBAL? Or are you planning to use DBAL with a MySQL DB?

Hi Xavier
I do use MySQL - since years...
Since I did not notice a note that MySQL is not ok, I should use DBAL... etc - I thought this should works as it did since years...
So, maybe there's a note in the Changelog but as long as the install tool does not say: "hey - MySQL is deprecated use something different" - I do not think about using something different.

And as written above: when entering the db name manually in the localconf everything is working as I am used to it...

OK, thus the problem seems to be that DBAL remained activated at the end of the Install process although you chose a MySQL database and that DBAL is not needed and should in 99% of cases be deactivated when using MySQL.

Just wanted to add:
in the 1-2-3 mode, the install tool works good: you put in the db-username, the password and the host, then it works.
Normally I skip the 1-2-3 mode...

Good to know! Thanks. I won't manage to deal with that for upcoming 4.5.1 but it's on my list!

A similar problem with fresh 4.4.7 installation - if I skip 1-2-3 steps I can't connect to MySQL until I manually remove dbal from extensions in typo3conf/localconf.php

Same problem with updating 4.3 to 4.4.10.

ADONewConnection: Unable to load database driver ''
Fatal error: Call to a member function PConnect() on a non-object in /home/mysite/public_html/typo3/sysext/dbal/class.ux_t3lib_db.php on line 2574

Not sure why the issue marked as duplicated to rejected issue #27195
But the bug still exists in 4.7.1 - if I skip 1-2-3 steps on fresh install and go directly to Install Tool I can't connent to the MySQL DB because of unneeded extensions installed - dbal and adodb, if I remove them from localconf.php manually then all works fine.

As 4.7 will only get security updates and this issue was tested for TYPO3 CMS 6.1 and the installer process was rewritten for TYPO3 CMS 6.2, I'd like to close this issue.

But before, my question, does this issue occur in latest TYPO3 CMS 6.1 release?