Bug #97659
openImport/Export Uppon Import Preview: ERROR: One of the inputs were not an array!
0%
Description
After I Import any kind of data and hit the preview button I always get an error in the result column:
ERROR: One of the inputs were not an array!
The Import seems to work without issue however
Files
Updated by Sebastian Gärtner over 1 year ago
Lina Wolf wrote:
After I Import any kind of data and hit the preview button I always get an error in the result column:
[...]
The Import seems to work without issue however
I have the same issue.
Updated by Christian Drost over 1 year ago
I get the same error while importing any usergroup.
TYPO3: 11.5.19
PHP: 8.1
Updated by Tobias Schmidt over 1 year ago
I'm trying to import data from TYPO3 9.5 to 11.5 and I see the same error message in preview window. The actual import doesn't work and stops with the following error message:
503 Oops, an error occurred! Argument 1 passed to TYPO3\CMS\Impexp\Import::getReferenceDefaultValue() must be of the type array, null given, called in [...]/sysext/impexp/Classes/Import.php on line 1042
Updated by Loek Hilgersom 12 months ago
The 'ERROR: One of the inputs were not an array!' occurs when you attempt to import something - both preview and real import - and you have:
- Update records = false
- Do not show differences in records = false
The import module then tries to show differences, but there are no differences to be shown since your import will create new records. The error disappears when you check 'Do not show differences in records'. It looks like you can ignore this error (although it is definately confusing).
Updated by Benni Mack 10 months ago
- Status changed from New to Needs Feedback
I cannot reproduce the issue. Can you tell me what kind of things are you exporting? Or maybe have an example t3d file?
Updated by Christian Welzel 6 months ago
Same Error here.
Export on 8.7.17, import on 11.5.30/PHP 7.4.20.
Example file is attached.
Updated by Christian Welzel 6 months ago
Note: The exported page does not exist yet in the new installation.
In this case $databaseRecord is null and the error message gets triggered.