#91169Replace file does not invalidate page cache
Description
An editor uploads an image in filelist. The editor references the image in a “textpic” CE on a page 1. The editor visits the frontend of page 1 and the page gets cached.
If an Editor replaces the image via “replace” functionality in filelist:
- processed files are removed. which is correct
- but page cache with references to the image is not invalidated
result:
textpic on page 1 shows no image anymore (as processed files were deleted and webserver says 404).
expected behaviour:
invalidate caches (e.g. pages) where file-references to fal-files are made.
Reviews 1
Related issues 4
- Bug #63976Replacing an image in File > Filelist does not trigger recreation of thumbnail
- Bug #68008Processed image versions are not deleted when image file is replaced
- Feature #94478Clear pages caches on referenced file replace
- Bug #95759Clearing cache of pages where file is linked if file was replaced
History 1118
-
Anonymous changed Related to #63976 <span data-processor="relativetime" data-value="2020-04-22T11:36:13+00:00" > 04/22/20, 11:36 </span>
-
Anonymous changed Related to #68008 <span data-processor="relativetime" data-value="2020-04-27T12:55:07+00:00" > 04/27/20, 12:55 </span>
-
Anonymous commented <span data-processor="relativetime" data-value="2020-06-24T09:17:13+00:00" > 06/24/20, 09:17 </span>
Josef Glatz wrote:
> Just some reference:
>
> @Ingo: Daniel Siepmann has dealt with such scenario in his article https://daniel-siepmann.de/posts/2019/typo3-content-caching.html if I can remember… There you find exactly good examples for your problem.That’s right.
But this is still an issue for all FSC CEs.
-
Riccardo De Contardi changed category <span data-processor="relativetime" data-value="2021-08-08T09:00:54+00:00" > 08/08/21, 09:00 </span>
-
Benni Mack changed Related to #94478 <span data-processor="relativetime" data-value="2021-11-05T12:33:59+00:00" > 11/05/21, 12:33 </span>
-
Benni Mack changed Related to #95759 <span data-processor="relativetime" data-value="2021-11-05T12:35:26+00:00" > 11/05/21, 12:35 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 74442 status
NewUnder Review <span data-processor="relativetime" data-value="2022-04-27T00:03:26+00:00" > 04/27/22, 00:03 </span> -
Gerrit Code Review pushed patch set 2 for main to change 74442 <span data-processor="relativetime" data-value="2022-04-27T00:06:52+00:00" > 04/27/22, 00:06 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 74442 <span data-processor="relativetime" data-value="2022-04-27T00:17:41+00:00" > 04/27/22, 00:17 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 74442 <span data-processor="relativetime" data-value="2022-04-27T00:20:45+00:00" > 04/27/22, 00:20 </span>
-
Christian Toffolo commented <span data-processor="relativetime" data-value="2022-04-27T06:04:49+00:00" > 04/27/22, 06:04 </span>
This extension Cache optimizer (not tested) does this and more. From the manual:
It uses an enhanced tag handling to clear the cache in these use cases: - When a content element is changed the cache of all pages is cleared where this content element is referenced by a shortcut. - When a file or the metadata of a file is changed the cache of all pages is cleared where this file is used in the page properties or in content elements. - When a file is changed the directory is detected and the cache of all pages is cleared where a folder collection references it. - When a record of an Extension is changed the cache of all pages is cleared where a related plugin is used.
IMHO all these cases should be handled by the core, not only the case where a file is replaced.
-
Gerrit Code Review pushed patch set 5 for main to change 74442 <span data-processor="relativetime" data-value="2022-04-30T21:11:08+00:00" > 04/30/22, 21:11 </span>
-
Simon Schaufelberger changed Complexity hard <span data-processor="relativetime" data-value="2022-05-02T21:40:08+00:00" > 05/02/22, 21:40 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 74442 <span data-processor="relativetime" data-value="2023-10-24T11:17:18+00:00" > 10/24/23, 11:17 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 74442 <span data-processor="relativetime" data-value="2023-10-24T11:19:43+00:00" > 10/24/23, 11:19 </span>
-
Simon Schaufelberger commented <span data-processor="relativetime" data-value="2026-03-07T19:27:14+00:00" > 03/07/26, 19:27 </span>
This should be fixed with #102430 or?
-
Benni Mack commented and changed status
Under ReviewClosed <span data-processor="relativetime" data-value="2026-10-23T08:17:40+00:00" > 10/23/26, 08:17 </span>Yes. closing this
Just some reference:
@Ingo: Daniel Siepmann has dealt with such scenario in his article https://daniel-siepmann.de/posts/2019/typo3-content-caching.html if I can remember… There you find exactly good examples for your problem.