Bug #56253
closed
Fatal Error at "Installing TYPO3 CMS"
Added by Andreas Fernandez over 10 years ago.
Updated about 6 years ago.
Description
Hello TYPO3 team,
installing TYPO3 with an Oracle database (oci8) fails on certain points. After selecting oci8 and passing the credentials, the install wizard crashes with a fatal error:
PHP Fatal error: Cannot use object of type TYPO3\CMS\Core\Configuration\ConfigurationManager as array in typo3/sysext/install/Classes/Controller/Action/Step/DatabaseConnect.php on line 93
Please see the attached patch file to fix the bug.
Files
- Project changed from 1865 to TYPO3 Core
I don't think the patch is correct.
The patch sets:
$config['_DEFAULT']['config']['driverOptions']['connectSID'] = $postValues['type'] === 'sid' ? TRUE : FALSE;
but $config is neither used below this line nor a reference.
Looking at the rest of the function, I guess something like the following is meant:
$config['_DEFAULT']['config']['driverOptions']['connectSID'] = $postValues['type'] === 'sid' ? TRUE : FALSE;
$configurationManager->setLocalConfigurationValueByPath('EXTCONF/dbal/handlerCfg', $config);
Disclaimer: This is just a guess by reading the code for the first time. I never used dbal or oracle.
Can you test and reproduce this on oracle?
- Category set to Install Tool
I tried your code and didn't notice any changes. So, I guess, it still works ;). I understand your point, but instead writing the new configuration back directly, I put it into $localConfigurationPathValuePairs. This array is written back into the configuration manager at the end of the method. Please see the attached diff.
Instead of pushing patches here, you could push these to the review system. So we can keep track much better...
- Status changed from New to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF