-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PHP Warning: array_replace_recursive(): Expected parameter 1 to be an array #24
Comments
The same with TYPO3 11.5.33 and PHP 8.0, any hints for that? |
The Position is related to slug generation, but the variable at that point should not be null.. I wonder how that happens at all. can you provide an xls or csv that triggers this error? |
Yes, this is my file (no personal Data, so it's fine for me to provide ist ;) |
Ok, that is fairly simple. What type of record are you trying to import? |
I try to import the xlsx file into the tx_cartbooks_domain_model_book table, but I don't know, if I understand, what you mean... |
yes thats what i meant.. I'll check it out later |
Ok. I need more information. I tested this with a vanilla installation of this extension with EXT:cart_books, and I did not have any problems importing your dataset. xls-import uses the DataHandler to write the new records to the database, and of course it will run all registered hooks in that case, and apply configured actions from the TCA where applicable (like slug generation for example).
|
|
@taunusweb @Philscode1 |
Just as a general advice - for these kind of errors/exceptions, it is always good to enable the debug mode and than provide the complete stack trace. This allows a extension maintainer/contributer to see the call chain and have some map at hand how it may come to this error in a TYPO3 core class. |
TYPO3 11.5.25
PHP 7.4
I got the error:
PHP Warning: array_replace_recursive(): Expected parameter 1 to be an array, null given in /var/www/html/public/typo3/sysext/core/Classes/DataHandling/DataHandler.php line 1779
The text was updated successfully, but these errors were encountered: