Bug #28800
closed
DBAL fatal error: No handler found in handler_getFromTableList() for: " tx_powermail_fields INNER JOIN ..."
0%
Description
In the Frontend, when submitting a Powermail form, I get the following error message in a blank page :
DBAL fatal error: No handler found in handler_getFromTableList() for: " tx_powermail_fields INNER JOIN tx_powermail_fieldsets ON ( tx_powermail_fields.fieldset = tx_powermail_fieldsets.uid AND tx_powermail_fieldsets.deleted=0 AND tx_powermail_fieldsets.t3ver_state<=0 AND tx_powermail_fieldsets.pid!=-1 AND tx_powermail_fieldsets.hidden=0 AND tx_powermail_fieldsets.starttime<=1312651020 AND (tx_powermail_fieldsets.endtime=0 OR tx_powermail_fieldsets.endtime>1312651020) ) INNER JOIN tt_content ON ( tx_powermail_fieldsets.tt_content = tt_content.uid AND tt_content = 70 AND tt_content.deleted=0 AND tt_content.t3ver_state<=0 AND tt_content.pid!=-1 AND tt_content.hidden=0 AND tt_content.starttime<=1312651020 AND (tt_content.endtime=0 OR tt_content.endtime>1312651020) AND (tt_content.fe_group='' OR tt_content.fe_group IS NULL OR tt_content.fe_group='0' OR FIND_IN_SET('0',tt_content.fe_group) OR FIND_IN_SET('-2',tt_content.fe_group) OR FIND_IN_SET('1',tt_content.fe_group) OR FIND_IN_SET('2',tt_content.fe_group) OR FIND_IN_SET('3',tt_content.fe_group)) )" (SQL engine parse ERROR: No join field found in parseFromTables()!: near "( tx_powermail_fields.fieldset = tx_powermai")
A search on Google tells me that it's a bug related to DBAL.
Can someone help me on finding a solution?
Updated by Xavier Perseguers over 13 years ago
- Status changed from New to Rejected
- Priority changed from Must have to Could have
Hi. Yes, this is related to DBAL. The question is why you need DBAL while having a MySQL backend.
Anyway, the answer is simple: the JOIN condition (INNER JOIN ... ON (... AND ... AND ...OR FIND_IN_SET()...) is simply too complicated and is not planned to be supported.
If you don't really need DBAL, then you should simply deactivate it, otherwise... well, powermail is thus not supported as it uses too complicated queries!
Updated by Jean ALex over 13 years ago
Xavier Perseguers wrote:
Hi. Yes, this is related to DBAL. The question is why you need DBAL while having a MySQL backend.
Anyway, the answer is simple: the JOIN condition (INNER JOIN ... ON (... AND ... AND ...OR FIND_IN_SET()...) is simply too complicated and is not planned to be supported.
If you don't really need DBAL, then you should simply deactivate it, otherwise... well, powermail is thus not supported as it uses too complicated queries!
You'r right. The problem was DBAL itself. I don't need DBAL, it's an extension come by default with TYPO3. If it's not already done, I suggest to document this case somewhere.
Thanks for your help. It's a wonderful extension by the way!
Updated by Michael Stucki almost 11 years ago
- Project changed from 329 to TYPO3 Core
- Category deleted (
MySQL) - Target version deleted (
1.2.3 (TYPO3 4.5.x))