Bug #89180

Remove sys_file_metadata width and height from excludefields

Added by Christian Futterlieb 28 days ago. Updated 25 days ago.

Status:
In Progress
Priority:
Should have
Assignee:
-
Category:
File Abstraction Layer (FAL)
Target version:
-
Start date:
2019-09-16
Due date:
% Done:

0%

TYPO3 Version:
8
PHP Version:
7.2
Tags:
Complexity:
easy
Is Regression:
Yes
Sprint Focus:

Description

The fields sys_file_metadata.width and sys_file_metadata.height are marked as readOnly. But they are excludeField too.

Even though this is not a logical combination at all, it wouldn't hurt much so far. Until now, when a user tried to translate a sys_file_metadata record and the width and height (which she did not have access to) fields are then set to zero (which then effectively disabled the crop config for the translation of the record to be rendered).

I'd suggest to just remove the 'exclude' => true from those two fields from sysext core and filemetadata. The height/width are managed internally anyway (for example when a user uploads an image the width/height are set correctly even though the user has no access according to the excludeFields). The visibility of the cols should be left to the typedef.


Related issues

Related to TYPO3 Core - Bug #81964: No crop information given in localized FAL version If translated meta data is provided Closed 2017-07-25

History

#1 Updated by Christian Futterlieb 28 days ago

I just saw: this is resolved by #81964, but for master only. Is there any chance we could get this for v8 and v9 too?

#2 Updated by Christian Futterlieb 28 days ago

  • Related to Bug #81964: No crop information given in localized FAL version If translated meta data is provided added

#3 Updated by Georg Ringer 25 days ago

  • Status changed from New to In Progress

will check if a backport will be done.

Also available in: Atom PDF