Bug #43471
closed
dbal used on clean install using mysql
Added by Stefan Neufeind almost 12 years ago.
Updated about 11 years ago.
Description
Minimal install from source + dummy with TYPO3 6.0 and using 1-2-3-installer.
DBAL was automatically activated. Could it be that's in the defaults now? Or activated during installation and not disabled again although mysql (native) is used?
This should not cause problems (well, it caused me to find #43470) but is not really useful performancewise.
Dbal is enabled during installation process (123 mode) and automatically disabled if the installation process is finished and a MySQL database is used. If you step out the 123 mode you have to take care about uninstall adodb and dbal on your own.
- Status changed from New to Needs Feedback
- Category set to Install Tool
Stefan, I could not reproduce that either.
Neither the Intro Package nor the Dummy package kept the DBAL activated after going through all the steps.
Actually step 1 activates dbal. Step 2 (in the URL "?TYPO3_INSTALL[type]=config&mode=123&step=3") will deactivate it again after you have chosen MySQL as a driver.
Please follow the steps again, note the corresponding URLs (step=x) and check LocalConfiguration.php after each step so that we can see what is happening in your installation.
Which of these PHP modules do you have loaded?
Hmm, I've tried various ways but also can't make it happen again. Weird.
I can confirm that upon step=3 in the URL (123 says it's actually step 2) dbal was disabled because mysql was chosen.
Of the above mentioned modules only pdo is installed.
I'd suggest, unfortunately, we close this as "unable to reproduce".
I've experienced the same thing again, now on Windows on a clean Xampp test-installation. However I'm still unsure how to make it reproducable though :-(
Did it happen again with 6.1?
For 6.2 the installer was rewritten.
Can't really tell. Haven't done many 6.1-installs lately. Sorry :-)
- Status changed from Needs Feedback to Closed
So I close this issue for now.
Stefan you can reopen this issue, if you get into this issue again. :-)
Yes, apparently, it happens with TYPO3 6.1
I moved a TYPO3 installation from a local Debian Wheezy to a Strato server. Now I can't access some pages of the install tool. DB information is correct.
For example:
http://test.mydomain.com/typo3/install/index.php?TYPO3_INSTALL[type]=config
Error Message:
TYPO3 Fatal Error: The current username, password or host was not accepted when the connection to the database was attempted to be established!
Details:
PHP Version 5.5.1
MySQL Client API version 5.0.91
mysqli Client API library version 5.0.91
Edit: made one mistake. The DB password was wrong ;) however, the system's behaviour is still puzzling, because why does the part of the install tool, where I can reset the password, throw an error when I select it in order to change the password?
Anyways, thanks.
Could it be you're experiencing a problem with DBAL and MySQL (not MySQLi)? See #50752 ... DBAL needs some mysqli-related changes. Please comment over in that forge-ticket if the fix might help you.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by