Bug #91169
open
Replace file does not invalidate page cache
Added by Anonymous over 4 years ago.
Updated about 1 year ago.
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.
- Related to Bug #63976: Replacing an image in File > Filelist does not trigger recreation of thumbnail added
- Related to Bug #68008: Processed image versions are not deleted when image file is replaced added
- Related to Feature #94478: Clear pages caches on referenced file replace added
- Related to Bug #95759: Clearing cache of pages where file is linked if file was replaced added
- Status changed from New to Under Review
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.
Also available in: Atom
PDF