#104795TypeError in TypoScriptService::convertPlainArrayToTypoScriptArray - Argument #1 ($plainArray) must be of type array, null given
Description
A TypeError occurs when trying to execute the method TypoScriptService::convertPlainArrayToTypoScriptArray() in TYPO3. The error message indicates that the method expects an argument of type array but is receiving null.
Additionally, it has been observed that media in {settings} no longer exists in Fluid_styled_content/Media/Type/Image.html. This could be related to the issue or cause further complications in the rendering of media content.
Error: TypeError TYPO3\CMS\Core\TypoScript\TypoScriptService::convertPlainArrayToTypoScriptArray(): Argument #1 ($plainArray) must be of type array, null given, called in /var/www/html/www/typo3/sysext/fluid_styled_content/Classes/ViewHelpers/Link/ClickEnla
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Files 2
History 6
-
Garvin Hicking commented and changed status
NewNeeds Feedback 09/02/24, 13:51 -
Jasper Verbunt commented and changed attached Screenshot 2024-09-05 at 09.22.18.png 09/05/24, 07:25
Garvin Hicking wrote in #note-1:
> Thanks for your report. Can you please provide a full stacktrace of where the error occurs, and also how you utilize your FSC chain, do you customize any partials?Thank you for your response. I’ve attached an image with the full stack trace for your reference. Additionally, I can confirm that we have not customized any partials in our setup. If needed, I am also available in the TYPO3 CMS Slack under the name Jelmer Ketelaar. Please let me know if you need any further details or clarification.
-
Garvin Hicking commented 09/05/24, 07:51
Thanks for getting back. I would need the full stacktrace, not an excerpt – so best, a HTML dump of it (see if you need to redact use of passwords or “secrets”).
At best I’d like to keep this in public here, so others can drop in too on the issue :-)
-
Jasper Verbunt commented and changed attached stacktrace.html 09/05/24, 09:57
Garvin Hicking wrote in #note-3:
> Thanks for getting back. I would need the full stacktrace, not an excerpt – so best, a HTML dump of it (see if you need to redact use of passwords or “secrets”).
>
> At best I’d like to keep this in public here, so others can drop in too on the issue :-)Sure thing. I hope this is what you need
-
Jasper Verbunt commented 09/18/24, 15:10
Hi. Have you found anything yet about this issue?
-
Garvin Hicking commented and changed status
Needs FeedbackClosed 09/18/24, 15:54Sorry, I had this on the list for some time, but I had some unplanned time off in the hospital. ;)
I just contacted Jelmer via Slack and went through it. We found at that the TypoScript definition of
lib.contentElement.settings.media.popupwas not existing. There is probably custom TypoScript that overwrites this (because the contents oflib.contentElementhad some custom keys in there).The solution here should be to ensure that the TypoScript definition is set, so that clickEnlarge can operate on these TypoScript settings. So in this case, the error message of receiving an invalid configuration input data array is IMO actually helpful, I’d not change the code to hide this instance, or silently just not use the clickEnlarge.
Hope that helps! Feel free to reply here or on slack, even though I already closed the issue so I don’t forget to. ;-)
Thanks for your report. Can you please provide a full stacktrace of where the error occurs, and also how you utilize your FSC chain, do you customize any partials?