Actions
Bug #57495
closed
Metadata db insert fails due to NULL value
Status:
Closed
Priority:
Should have
Assignee:
Category:
File Abstraction Layer (FAL)
Target version:
Start date:
2014-04-01
Due date:
% Done:
100%
Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
no-brainer
Is Regression:
No
Sprint Focus:
Description
The MetaDataRepository::createMetaDataRecord() function checks the TYPO3_MODE to decide the value of the cruser_id field.
When this is executed in the Install Tool Standalone context the TYPO3_MODE is BE, but no BE_USER is available.
So this results in NULL being assigned for the cruser_id field.
A subsequent database insert fails because of the column being defined as NOT NULL.
This leads to the problem that no metadata records are created for migrated files and the subsequent upgrader adds empty metadata records, lacking the width/height information.
Updated by 
Updated by 
Updated by
Actions