Bug #57565: Creating new sys_file_metadata record for existing sys_file record doesn't set image dimensions - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #57565

closed

Creating new sys_file_metadata record for existing sys_file record doesn't set image dimensions

Added by Bernhard Schmitt about 10 years ago. Updated almost 10 years ago.

Status:

Closed

Priority:

Must have

Assignee:

Category:

File Abstraction Layer (FAL)

Target version:

Start date:

2014-04-02

Due date:

% Done:

Estimated time:

TYPO3 Version:

6.2

PHP Version:

5.4

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

Given the presence of a sys_file record with no related sys_file_reference_record
When I am in the metadata "Edit" dialog in the filelist module
The missing sys_file_metadata record will be autocreated

But: (at least) the fields "width" and "height" are not written, which is quite deadly for the f:image ViewHelper

While this might sound like a special case of database inconsistency, it actually seems to be the default case when upgrading from 6.0 or 6.1
Might be related to #44105 et al.

Files

sys_file_export.sql (2.57 KB) sys_file_export.sql

Bernhard Schmitt, 2014-04-02 17:25

Related issues 2 (0 open — 2 closed)

Actions

Copy link

Updated by Alexander Opitz about 10 years ago

"While this might sound like a special case of database inconsistency, it actually seems to be the default case when upgrading from 6.0 or 6.1"

Did you run the migration wizards? Course this shouldn't be the case if you upgrade from 6.0/6.1.

Updating TYPO3 before 6.0 had an issue, which was solved today with #46020.

The issue behind the auto creation with empty values is #57545. I would like to concentrate me on your upgrade problem in this issue.

Actions

Copy link

Updated by Bernhard Schmitt about 10 years ago

Yep, I ran the migration wizards. One step stated the splitting and creation of FAL stuff, so I didn't skip on that.
Actually, the sys_file_metadata table seemed to be completely populated with records, but they were empty except for the references to sys_file

Actions

Copy link

Updated by Alexander Opitz about 10 years ago

Status changed from New to Accepted

Ok, we will take a look into this. Can you tell me, which TYPO3 version do you tried to update? And maybe some lines from the sys_file table before migration?
If we found an issue there, do you have the possibility to migrate again with fixed code?

Actions

Copy link

Updated by Bernhard Schmitt about 10 years ago

File sys_file_export.sql sys_file_export.sql added

Old version was 6.1.5

File records are attached

Migration can be re-done, no problem.

Actions

Copy link

Updated by Alexander Opitz about 10 years ago

Thanks for help, hopefully I have time tomorrow to take a look. The SQL snippet seams to be correct.

Actions

Copy link

Updated by Alexander Opitz about 10 years ago

Hi Bernhard,

I couldn't reproduce this issue, so I need some more information:

Dump of the SQL Structure of the sys_file before migration.
Dump of the SQL Structure of the sys_file_metadata after migration.

The FileTableSplittingUpdate wizard takes all data from sys_file and inserts them into sys_file_metadata in one SQL Statement. I don't think that there is an error, but maybe the table structure has issues.

One possibility in my mind, did you start the "Database analyzer" before migration?

Actions

Copy link

Updated by Bernhard Schmitt almost 10 years ago

I've tested this again with 6.2.3 including running the complete set of install tool upgrade wizards and scheduler tasks and there seem to be no further problems regarding image dimensions.

Actions

Copy link