Project

General

Profile

Actions

Bug #40669

closed

FAL files get reindexed in storage null when used with tt_content

Added by Steffen Ritter over 11 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Must have
Category:
File Abstraction Layer (FAL)
Target version:
Start date:
2012-09-06
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.0
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Related issues 4 (0 open4 closed)

Related to TYPO3 Core - Bug #39904: Unresized image not displayed in FE after move in filelistClosedSteffen Ritter2012-08-17

Actions
Related to TYPO3 Core - Bug #48998: FAL files get reindexed in storage null when used with tt_contentClosed2012-09-06

Actions
Has duplicate TYPO3 Core - Bug #41783: every image used in frontend gets indexed in storage 0 againClosedSteffen Ritter2012-10-09

Actions
Blocked by TYPO3 Core - Bug #43059: File processing is brokenClosedAndreas Wolf2012-11-17

Actions
Actions #1

Updated by Andreas Wolf over 11 years ago

From the description of #41783:

The FrontendContentAdapterService currently just hands over file-names. CSS Styled Content makes file objects out of them again - as only path' are given there, storage 0 is assumed. All images get reindexed in storage 0, and the uid of this file then is used within the processedfile as reference

Actions #2

Updated by Gerrit Code Review over 11 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15439

Actions #3

Updated by Gerrit Code Review over 11 years ago

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15439

Actions #4

Updated by Gerrit Code Review over 11 years ago

Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15439

Actions #5

Updated by Steffen Ritter over 11 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #6

Updated by Klaus Hinum almost 11 years ago

This is happening (again?) with Typo3 6.1.1
perhaps a regression of the fix of this issue?
http://forge.typo3.org/issues/47211

Actions #7

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF