Task #64196

Make it possible to re index files from storage 0

Added by Frans Saris over 6 years ago. Updated about 6 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
File Abstraction Layer (FAL)
Target version:
Start date:
2015-01-08
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Sprint Focus:
Remote Sprint

Description

Currently all files outside of the available storages that are handled by the FAL api are indexed under pseudo storage 0. For example images in the uploads folder but also resources found in extension folders.

Problem with this is that for images the dimensions etc are stored in db and these do not get updated if a certain file gets replaced by another.

It should be possible to reindex these files just like other storages. With the side note that only files that are already are indexed should be re indexed and not that the whole typo3conf folder should get indexed.

For every updated indexed all linked processed files should be removed so a new processed file is created on next hit.


Related issues

Related to TYPO3 Core - Bug #66340: Processed files for storage 0 do not get updated when the original file changesClosed2015-04-09

Actions
Related to TYPO3 Core - Bug #50392: Specifying size in ImageViewHelper does nothingClosed2013-07-24

Actions
#1

Updated by Philipp Gampe over 6 years ago

We will need an own scheduler task for this.

#2

Updated by Tymoteusz Motylewski over 6 years ago

  • Parent task set to #65815
#3

Updated by Xavier Perseguers over 6 years ago

  • Parent task deleted (#65815)
#4

Updated by Benni Mack over 6 years ago

  • Target version changed from 7.1 (Cleanup) to 7.4 (Backend)
#5

Updated by Pierrick Caillon over 6 years ago

  • Status changed from New to In Progress
  • Assignee set to Pierrick Caillon
#6

Updated by Pierrick Caillon over 6 years ago

Frans Saris wrote:

For every updated indexed all linked processed files should be removed so a new processed file is created on next hit.

I am worrying about cache in this case. If we remove the file but do not clear the cache after replacing the file and running the task, a new client will not see the image because the page content is from cache with the no more existing file path. I don't think we should explicitly remove files from this task as it is not done on other storages.

#7

Updated by Gerrit Code Review over 6 years ago

  • Status changed from In Progress to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40316

#8

Updated by Gerrit Code Review over 6 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40316

#9

Updated by Gerrit Code Review over 6 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40316

#10

Updated by Gerrit Code Review over 6 years ago

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40316

#11

Updated by Helmut Hummel over 6 years ago

  • Status changed from Under Review to Needs Feedback

Do we really, really want this?

Honestly I wished we could get rid of the fallback storage. Making indexing work again here works in a different direction

#12

Updated by Pierrick Caillon over 6 years ago

  • Assignee deleted (Pierrick Caillon)
#13

Updated by Susanne Moog about 6 years ago

  • Sprint Focus changed from On Location Sprint to Remote Sprint
#14

Updated by Susanne Moog about 6 years ago

  • Target version changed from 7.4 (Backend) to 7.5
#15

Updated by Benni Mack about 6 years ago

  • Status changed from Needs Feedback to Rejected

should be done in a TER extension

Also available in: Atom PDF