http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692014-08-11T20:55:37ZTYPO3 ForgeTYPO3 Core - Task #60898: On physically moving a file through the FAL API, the cache of affected pages is not clearedhttp://forge.typo3.org/issues/60898?journal_id=2269582014-08-11T20:55:37ZGerrit Code Review
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Under Review</i></li></ul><p>Patch set 1 for branch <strong>master</strong> of project <strong>Packages/TYPO3.CMS</strong> has been pushed to the review server.<br />It is available at <a class="external" href="http://review.typo3.org/32098">http://review.typo3.org/32098</a></p> TYPO3 Core - Task #60898: On physically moving a file through the FAL API, the cache of affected pages is not clearedhttp://forge.typo3.org/issues/60898?journal_id=2455222015-01-18T21:07:04ZIngo Schmitt
<ul><li><strong>Category</strong> changed from <i>Frontend</i> to <i>File Abstraction Layer (FAL)</i></li><li><strong>Sprint Focus</strong> set to <i>On Location Sprint</i></li></ul> TYPO3 Core - Task #60898: On physically moving a file through the FAL API, the cache of affected pages is not clearedhttp://forge.typo3.org/issues/60898?journal_id=2477222015-01-30T18:24:59ZPhilipp Gampephilipp.gampe@typo3.org
<ul></ul><p>The cache must not be cleared automatically, because the file might be used on many pages, even with "insert record" and "show contents of this page", etc. This would be a huge complexity and can potentially kill the server, both for clearing all those caches and for regenerating the caches later on.</p>
<p>Instead, the caching framework should ask the caching framework to clear all cache with the tag sys_file_<uid>:<br /><pre>
/** @var CacheManager $cacheManager */
$cacheManager = $this->getCacheManager();
$cacheManager->flushCachesInGroupByTag('pages', 'sys_file_' . $uid);
</pre></p>
<p>See \TYPO3\CMS\Core\DataHandling\DataHandler::processClearCacheQueue() [bottom of the function].</p>
<p>The integrator/developer of the site need to make sure to tag all pages that should be cleared automatically. This way he has full control over the performance impact.</p> TYPO3 Core - Task #60898: On physically moving a file through the FAL API, the cache of affected pages is not clearedhttp://forge.typo3.org/issues/60898?journal_id=2477242015-01-30T18:25:34ZPhilipp Gampephilipp.gampe@typo3.org
<ul><li><strong>Complexity</strong> set to <i>easy</i></li></ul> TYPO3 Core - Task #60898: On physically moving a file through the FAL API, the cache of affected pages is not clearedhttp://forge.typo3.org/issues/60898?journal_id=2477262015-01-30T18:28:10ZLorenz Ulrich
<ul></ul><p>Comment from Helmut Hummel in Gerrit:</p>
<pre>
The proposed CacheService works very low level, which is likely to cause troubles when changing internals.
It also works kind of "backwards" by looking at the usages of files in the moment they are changed/moved
Instead I would propose to correctly set cache tags "file_usage_<idOfFile>" for the page once the page is rendered and e.g. publicUrl is called for a file.
When doing so, we can just call ->flushByTag("file_usage_<idOfFile>") when a file is changed
</pre> TYPO3 Core - Task #60898: On physically moving a file through the FAL API, the cache of affected pages is not clearedhttp://forge.typo3.org/issues/60898?journal_id=2481692015-02-01T10:11:28ZMathias Schreibermathias.schreiber@typo3.com
<ul><li><strong>Sprint Focus</strong> deleted (<del><i>On Location Sprint</i></del>)</li></ul> TYPO3 Core - Task #60898: On physically moving a file through the FAL API, the cache of affected pages is not clearedhttp://forge.typo3.org/issues/60898?journal_id=2481702015-02-01T10:14:12ZMathias Schreibermathias.schreiber@typo3.com
<ul></ul><p>Results of the discussion at the FAL sprint:<br />Before we can handle this in a meaningful way the Content Elements need to properly tag the page cache.</p>
<p>If this functionality is in place, we can then clear by tags.</p> TYPO3 Core - Task #60898: On physically moving a file through the FAL API, the cache of affected pages is not clearedhttp://forge.typo3.org/issues/60898?journal_id=2481712015-02-01T10:14:44ZMathias Schreibermathias.schreiber@typo3.com
<ul><li><strong>Status</strong> changed from <i>Under Review</i> to <i>Accepted</i></li></ul> TYPO3 Core - Task #60898: On physically moving a file through the FAL API, the cache of affected pages is not clearedhttp://forge.typo3.org/issues/60898?journal_id=2596162015-05-23T17:11:33ZJigal van Hemertjigal.van.hemert@typo3.org
<ul><li><strong>Priority</strong> changed from <i>Should have</i> to <i>Must have</i></li></ul><p>The same effect can be seen by:</p>
<p>- overwriting a file in the Filelist module<br />- overwriting a file with other methods and running the Scheduler task to update the FAL index</p>
<p>With the pre-FAL behaviour we could explain to editors that placing an image on a page creates a copy of the original image. With FAL this was over and the advantages were clear. Editors wouldn't understand that they would have to manually track down where an image is used and clear caches (an image used in a record would even be more complicated, because it might be necessary to clear the caches of the pages where the record is used).</p> TYPO3 Core - Task #60898: On physically moving a file through the FAL API, the cache of affected pages is not clearedhttp://forge.typo3.org/issues/60898?journal_id=3023402016-04-19T07:38:09ZDMK E-BUSINESS GmbHdev@dmk-ebusiness.de
<ul></ul><p>Hi,</p>
<p>we got the same problem, hoping for a solution. The bug is accepted but there seems to be no progress since almost one year.</p>
<p>Can a fix still be expected?</p> TYPO3 Core - Task #60898: On physically moving a file through the FAL API, the cache of affected pages is not clearedhttp://forge.typo3.org/issues/60898?journal_id=3962512019-03-07T12:07:46ZSusanne Moogsusanne.moog@typo3.org
<ul><li><strong>Tracker</strong> changed from <i>Bug</i> to <i>Task</i></li><li><strong>Status</strong> changed from <i>Accepted</i> to <i>On Hold</i></li></ul><p>As stated before this can only be fixed after sensible tagging of Content Elements has been introduced.</p> TYPO3 Core - Task #60898: On physically moving a file through the FAL API, the cache of affected pages is not clearedhttp://forge.typo3.org/issues/60898?journal_id=4203532020-03-24T18:50:30ZSusanne Moogsusanne.moog@typo3.org
<ul><li><strong>Status</strong> changed from <i>On Hold</i> to <i>Closed</i></li></ul><p>For completenes sake: TYPO3 does not clear caches automatically and will only do so when and if proper caching for all kinds of content is implemented. As that is a long way of and this ticket is a task, I'm going to close this now as the whole topic probably needs an own initiative. (Also because the requirements for different projects might differ a lot, see comments above about insert records for example).</p>
<p>For those needing a more immediate solution to that problem, please take a look at <a class="external" href="https://extensions.typo3.org/extension/cacheopt">https://extensions.typo3.org/extension/cacheopt</a> which provides the requested feature via hooks as far as I can see.</p>