Bug #70375
closed
Story #69617: FormEngine bugs
PHP Warning: Illegal offset type in isset or empty in .../typo3/sysext/backend/Classes/Form/InlineRelatedRecordResolver.php line 233
100%
Description
Hi,
using TYPO3 7.5.0 with powermail 2.11.2 leads to an error in backend, while editing localized Form records (with related Page records via IRRE):
It seems that there are problems with IRRE "appearance" settings in TCA.
Disabling "showPossibleLocalizationRecords" and "showRemovedLocalizationRecords" in EXT:powermail/Configuration/TCA/tx_powermail_domain_model_forms.php prevents the warning:
...
'pages' => array(
'exclude' => 0,
'label' => 'LLL:EXT:powermail/Resources/Private/Langu
'config' => array(
'type' => 'inline',
'foreign_table' => 'tx_powermail_domain_model_pag
'foreign_table_where' =>
'AND tx_powermail_domain_model_pages.deleted
and tx_powermail_domain_model_pages.sys_langu
'foreign_field' => 'forms',
'foreign_sortby' => 'sorting',
'maxitems' => 10,
'appearance' => array(
'collapseAll' => 1,
'expandSingle' => 1,
'useSortable' => 1,
'newRecordLinkAddTitle' => 1,
'levelLinksPosition' => 'top',
'showSynchronizationLink' => 0,
'showAllLocalizationLink' => 1,
//'showPossibleLocalizationRecords' => 1,
//'showRemovedLocalizationRecords' => 1,
),
...
Is there something wrong with my TCA?
Updated by Wouter Wolters over 8 years ago
- Status changed from New to Needs Feedback
Still the case with 7.6 or master?
Updated by Felix Nagel over 8 years ago
I had this issue too. It was caused by a wrong SQL mode. There should be a warning in the install tool (at least in 7.x versions).
Try following SQL command and try if the error still occurs:
SET @@global.sql_mode=''
Updated by
Updated by Christian Kuhn almost 8 years ago
- Status changed from Needs Feedback to Closed
Closing this issue:
The class InlineRelatedRecordResolver doesn't exist anymore in 7.6 / master, neither does the method getLocalizationDifferences() where this warning triggered in 7.5.0. This area was heavily refactored betwenn 7.5 and 7.6, the issue is probably solved.
The comment by Felix Nagel doesn't seem to be related to this issue, at least I don't see any relation between the "transOrigPointerField" in inline relations and the sql mode that is set.
In case a similar warning is still reproducible in current 7.6, please open a new issue. On reporting, it would be great to see the full backtrace as well as the involved tca and maybe data sets to trigger such an issue.