Bug #15823
closed
Pages not shown in FE with DBAL and Oracle
0%
Description
I installed Typo3 4.0RC1 with MySQL, then added adodb and dbal and changed dbal configuration to:
$TYPO3_CONF_VARS['EXTCONF']['dbal']['handlerCfg']=array(
'_DEFAULT'=>array(
'type'=>'adodb',
'config'=>array(
'driver'=>'oci8'
)
),
);
$TYPO3_CONF_VARS['EXTCONF']['dbal']['debugOptions'] = array(
'enabled' => TRUE,
'printErrors' => TRUE,
'EXPLAIN' => 0,
'parseQuery' => 1,
'joinTables' => 1
);
I can create pages and contents, but when I try to look at the web page I get error message: "The requested page does not exist!"
Through debuging I have discovered, that if I change fe_group field in pages and tt_content table form '' to '0', page and content is normally displayed.
(issue imported from #M2866)
Updated by Karsten Dambekalns over 18 years ago
Today I debugged some problem with tt_news and saw the same problem (comparing an integer field to an empty string). I'll have to think about a solution, though...
Updated by Kurt Lochte over 18 years ago
Hello Uroš,
may be you have the same problem described in --> 0002327: DB Field fe_group is empty after migration to beta1+2
Greets
Kurt Lochte
Updated by Uros Kositer over 18 years ago
Hi!
Sorry for late reply.
No, I don't think that this problem is related to bug report 0002327. I have clean instalation.
Today I have installed version 4.0 and the problem is still exists. I can now create pages, but cannot create content anymore. I get "Sorry, you didn't have proper permissions to perform this change." error everytime I try to save content element or change type of content element.
I think this bug is related to blob handling as it was described in some other bug reports.
Greets
Uros
Updated by Karsten Dambekalns over 18 years ago
This is (probably) caused by a where clause that tests for the field being '' or '0' which doesn't work if the field is null (which it is under Oracle in a lot of cases). The fix is to add another " field IS NULL" to the where clause.
I am currently on a project making TYPO3 run (again) on Oracle 10g and hope to have the fixes in version 4.0.1 and/or in TER the next days.