Bug #53735
closed
Fatal error in FileIdentifierHashUpdate
Added by Alexander Stehlik about 11 years ago.
Updated about 7 years ago.
Category:
File Abstraction Layer (FAL)
Description
When executing the FileIdentifierHashUpdate
I got an PHP error:
Fatal error: Cannot use string offset as an array in /var/www/typo3_src/typo3_src-master/typo3/sysext/install/Classes/Updates/FileIdentifierHashUpdate.php on line 145
I found out that the reason for this error was a deleted record in the sys_file_storage
table where the configuration
field did not contain any data.
This lead to an error in the GeneralUtility::xml2array()
call which returns a string in that case. Using this string as an array will not work.
It needs to be made sure that the FlexForm data in the configuration
field is not empty and / or no parsing error occurs in xml2array()
.
- Category set to Install Tool
- Priority changed from Should have to Must have
- Target version changed from 6.2.0 to next-patchlevel
- Is Regression changed from No to Yes
Two suggestions:
- Skip deleted storages in general?
- The wizard should skip storages with no configuration. But this will lead to the situation that all storages except those with no configuration are migrated and the wizard keeps showing up, since it still detects not migrated storages.
Maybe faulty storages with no configuration should get marked somehow.
Skip deleted storages in general?
Hmm, I would not do that because if the storage is restored after the wizard was run it contains an old configuration.
The wizard should skip storages with no configuration.
What about: set is_online
to false and add a hint to the storage title / description:
Title: <OldTitle> [invalid]
Description:
<OldDescription>
This storage was disabled by the install tool, because it contains an invalid (FlexForm) configuration. To regenerate the configuration, please save it once.
- Category changed from Install Tool to File Abstraction Layer (FAL)
- Status changed from New to Accepted
- Target version changed from next-patchlevel to 6.2.0
- Sprint Focus set to On Location Sprint
- Status changed from Accepted to Resolved
can't reproduce - the file is not there
- Sprint Focus deleted (
On Location Sprint)
- Status changed from Resolved to Closed
Also available in: Atom
PDF