Bug #27195
closed
1-2-3 Wizard fails with AdoDB/DBAL errors
Added by Steffen Gebert over 13 years ago.
Updated almost 13 years ago.
Description
Occurs on MacOS with 4-5 and master. PHP pdo extension is loaded (but that's default IIRC).
Files
Now I can't reproduce anymore after a few webserver restarts. It occurred since a few weeks, when I tried to install the IP.
- Status changed from New to Rejected
- Status changed from Rejected to New
If used with Chrome Browser, Installer writes the following line at the end of localconf.php and show the "ADONewConnection: Unable to load database driver '':" error in the frontend:
$TYPO3_CONF_VARS['EXTCONF']['dbal']['handlerCfg'] = array('_DEFAULT' => array('type' => 'adodb','config' => array('driver' => '',)));;
Using Firefox, the installer does not write the above line. If the above line is deleted from localconf.php, neither Firefox or Chrome show errors.
Wow, thanks for this great observation! This really explains this weird Heisenbug to me - I always use Firefox for Debugging, thus the bug always disappeared, once I tried to investigate ;-)
Never thought that this could be browser-dependent. If you find the reason, please update! Could take a few days, until I find some time.
- Category set to Install Tool
- Priority changed from Should have to Must have
- Target version set to 4.6.0-beta1
Hartmut, have you tried this with 4.6 or 4.6? This one is really incredible!! Again, I can't reproduce now, after fixing #28324.
Well, I spent some hours on this, but was still not able to figure out, why it occurs in Chrome, but not in Firefox. The whole thing is very weird, with the Install Tool's redirects and sending contradictory data in $_GET
and $_POST
.
- I was able to reproduce it in Firefox, too, following this procedure:
- Go through the wizard, until you have to select Introduction Package or Blank Package
- Click on (1) to go back to the first step
- Hit the Continue button.
- Somehow, the
tx_dbal_installtool::executeWriteLocalconf()
is called for a second time in Chrome (after the HTTP redirect?), but as this time $instObj->INSTALL['localconf.php']['typo_db_driver']
is NULL
, after passing the case
. it writes the wrong information without an driver
to @localconf.php.
Stack trace:
tx_dbal_installtool::executeWriteLocalconf(array, 4, tx_install)
/opt/local/apache2/vhosts/master/typo3_src/typo3/sysext/install/mod/class.tx_install.php:
03774: foreach ($GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['ext/install/mod/class.tx_install.php']['writeLocalconf'] as $classData) {
03775: $hookObject = t3lib_div::getUserObj($classData);
03776: $hookObject->executeWriteLocalconf($lines, $this->step, $this);
03777: }
03778: }
3 tx_install::setupGeneral()
/opt/local/apache2/vhosts/master/typo3_src/typo3/sysext/install/mod/class.tx_install.php:
00480: // Setting stuff...
00481: $this->check_mail();
00482: $this->setupGeneral();
00483: $this->generateConfigForm();
00484: if (count($this->messages)) {
2 tx_install::init()
/opt/local/apache2/vhosts/master/typo3_src/typo3/init.php:
00342: $install_check = t3lib_div::makeInstance('tx_install');
00343: $install_check->allowUpdateLocalConf = 1;
00344: $install_check->init();
00345: exit;
00346: }
1 require("/opt/local/apache2/vhosts/master/typo3_src/typo3/init.php")
/opt/local/apache2/vhosts/master/typo3_src/typo3/install/index.php:
00138: // Defining this variable and setting it non-false will invoke the install-screen called from init.php
00139: define('TYPO3_enterInstallScript', '1');
00140: require ('../init.php');
00141:
00142: ?>
Just wondering, could it be related to the browser maybe prefetching the next page or so and by that causing a "half" request (triggering an action it should not)?
- Target version changed from 4.6.0-beta1 to 4.6.0-beta2
Is somebody else able to reproduce this?
- Target version changed from 4.6.0-beta2 to 4.6.0-beta3
- Target version changed from 4.6.0-beta3 to 4.6.0-RC1
Steffen Gebert wrote:
Is somebody else able to reproduce this?
Hi,
i´ve just tried to reproduce this on Macbook with MAMP Pro v 1.9 and Chrome (just made a fresh install), using introduction package TYPO3 4.6beta3.
All went fine... could not reproduce the error. All 4 steps ok.
After that I went to Database Analyzer and made a compare... again: everything ok.
Maybe this helps.
Regards
Ralf
(t3quetsche, merzilla)
- Priority changed from Must have to Should have
- Target version deleted (
4.6.0-RC1)
Thanks for testing, Ralf! So I'm setting the priority down, as long as it's really only me. Nevertheless, I still can reproduce.
Steffen Gebert wrote:
Thanks for testing, Ralf! So I'm setting the priority down, as long as it's really only me. Nevertheless, I still can reproduce.
You´re welcome! :)
- Status changed from New to Rejected
Not reproducible anymore.. :-)
Also available in: Atom
PDF