Project

General

Profile

Actions

Bug #26142

closed

Media field in pages_language_overlay differs from field in pages table

Added by Mario Rimann over 13 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Miscellaneous
Target version:
Start date:
2011-04-20
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

The field "media" in the pages table is of type "text" while in the table pages_language_overlay it's of type "tinytext". We encountered a problem when adding some files to the media field of a page, and wanting to do the same on the translated page (yes, long file names involved...)

Steps to reproduce:
- create a page
- add some file to the media field, best some with long file names and/or a long path within fileadmin
- save and check in the db > filenames should be stored properly
- create a translation of this page
- add the same files to the media field of the "alternate page language" record
- save -> the filenames get cropped since the DB field is too short to save all of the data

Expected behaviour:
The translated page record should behave like the page itself and store the path/filenames correctly.

Needed changes:
Since the TCA looks the same for the two fields, I assume only the DB schema needs to be adapted.

Since the fix of this bug will include changes to the DB schema, I set the target version to 4.6.0.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #28317: Increase "maxitems" for media in TCA of pagesClosed2011-07-19

Actions
Actions #1

Updated by Mr. Hudson over 13 years ago

Patch set 1 of change I05298e8429384da7af6ffdef78587198532030f0 has been pushed to the review server.
It is available at http://review.typo3.org/2513

Actions #2

Updated by Mario Rimann over 13 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
Actions #3

Updated by Clemens Riccabona about 10 years ago

This has not been fixed in TYPO3 4.5.37. I just stumbled upon this issue in a customers TYPO3 installation.

IMHO it would be save to solve this bug in 4.5.X because it only changes the db from tinytext to text, and I can't imagine any unwished side-effects.

Actions #4

Updated by Ernesto Baschny about 10 years ago

  • Is Regression set to No

Thanks for the feedback Clemens. There are lots of fixes which could make "no harm". but we are now focused on 6.2 and later and only "important fixes" will still be backported to 4.5 (security issues, browser compatibility and maybe some selected others). This issue does not fit in this category. If you are affected, please consider updating your DB manually, as there is no need to change any code to do so. Thanks for understanding and keep up with helping us out!

Actions #5

Updated by Clemens Riccabona about 10 years ago

ok ernesto, i did so in my 4.5 branch of ricbasicsettings. quick 'n dirty. ;)

Actions #6

Updated by Riccardo De Contardi about 7 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF