Bug #101724
closedPHP Warning: Undefined array key in in /.../cms-recordlist/Classes/Browser/FileBrowser.php line 158
0%
Description
Undefined array key warnings in the filebrowser.
Tue, 22 Aug 2023 10:09:57 +0200 [WARNING] request="00c26218332ab" component="TYPO3.CMS.Core.Error.ErrorHandler": Core: Error handler (BE): PHP Warning: Undefined array key 1 in /var/www/html/vendor/typo3/cms-recordlist/Classes/Browser/FileBrowser.php line 158 Tue, 22 Aug 2023 10:09:57 +0200 [WARNING] request="00c26218332ab" component="TYPO3.CMS.Core.Error.ErrorHandler": Core: Error handler (BE): PHP Warning: Undefined array key 2 in /var/www/html/vendor/typo3/cms-recordlist/Classes/Browser/FileBrowser.php line 158 Tue, 22 Aug 2023 10:09:57 +0200 [WARNING] request="00c26218332ab" component="TYPO3.CMS.Core.Error.ErrorHandler": Core: Error handler (BE): PHP Warning: Undefined array key 4 in /var/www/html/vendor/typo3/cms-recordlist/Classes/Browser/FileBrowser.php line 158
Updated by Christian Kuhn about 1 year ago
- Status changed from New to Needs Feedback
Thanks!
Looking at the code, the line in question should probably be sanitized better.
Still, do you have any information on how to reproduce?
It looks as if this should not happen in general by default, and I guess the fix depends on what is actually going wrong here.
Updated by Patrick Lenk about 1 year ago
It seems that these warnings occur in rare cases when an editor wants to add an image or link to a core content element. but i can't add any steps to reproduce this.
The default upload folder is accessible and configured in sitepackage user ts config like:
options { defaultUploadFolder = 1:/uploads/editor/ }
Updated by David Bruchmann 12 months ago
Might it be related to this?
https://forge.typo3.org/issues/96529
Updated by Patrick Lenk 12 months ago
David Bruchmann wrote in #note-3:
Might it be related to this?
https://forge.typo3.org/issues/96529
no
Updated by Georg Ringer 4 months ago
- Status changed from Needs Feedback to Closed
Hey Patrick,
I failed to reproduce this as well and closing the issue to cleanup forge a bit.
If this is still valid for you in v12/v13 and you can reproduce it, please either contact me on slack or create a new issue and reference that one.