Bug #65800
PageRepository::shouldFieldBeOverlaid raises PHP warning - FileReference
Status: | Closed | Start date: | 2015-03-18 | |
---|---|---|---|---|
Priority: | Must have | Due date: | ||
Assigned To: | - | % Done: | 0% |
|
Category: | Frontend | Spent time: | - | |
Target version: | - | |||
TYPO3 Version: | 6.2 | Is Regression: | No | |
PHP Version: | 5.5 | Sprint Focus: | ||
Complexity: |
Description
I have the Error:
Uncaught TYPO3 Exception
#1: PHP Warning: trim() expects parameter 1 to be string, array given in /home/shared_typo3/typo3_source/typo3_src-6.2.11/typo3/sysext/frontend/Classes/Page/PageRepository.php line 1416 (More information)TYPO3\CMS\Core\Error\Exception thrown in file
/home/shared_typo3/typo3_source/typo3_src-6.2.11/typo3/sysext/core/Classes/Error/ErrorHandler.php in line 101.20 TYPO3\CMS\Core\Error\ErrorHandler::handleError(2, "trim() expects parameter 1 to be string, array given", "/home/shared_typo3/typo3_source/typo3_src-6.2.11/t…o3/sysext/frontend/Classes/Page/PageRepository.php", 1416, array)
19 trim(array)/home/shared_typo3/typo3_source/typo3_src-6.2.11/typo3/sysext/frontend/Classes/Page/PageRepository.php:
01414: }
01415:
01416: if ($checkValue === array() || trim($checkValue) === '') {
01417: $shouldFieldBeOverlaid = FALSE;
01418: }
The Array has one FileReference (media) from pages_language_overlay.
array(1 item) 0 => TYPO3\CMS\Core\Resource\FileReferenceprototypeobject propertiesOfFileReference => array(32 items) uidOfFileReference => NULL name => NULL originalFile => TYPO3\CMS\Core\Resource\Fileprototypeobject mergedProperties => array(empty)
If have the Option: $GLOBALS['TCA']['pages_language_overlay']['columns']['media']['l10n_mode'] = 'mergeIfNotBlank';
related to Core #60998
Related issues
History
#1 Updated by Florian Engelke 5 months ago
- File pages_language_overlay_meida.png added
#2 Updated by Markus Klein 5 months ago
- Status changed from New to Closed
- Priority changed from Should have to Must have
Ah I didn't see you created a new ticket.
I'd have preferred that before, but now pushed the patch as followup to the old ticket #60998.
Closing this one therefore.