- First commit to issue fork.
- @sjpeters79 opened merge request.
- 🇨🇦Canada sjpeters79
Added a patch that will invalidate the cache tags for the replaced file thus invoking drupal to purge the required files cache and the cache url for the file.
We should be able integrate with the Purge → module to automatically invalidate external cache entries for the replaced file after it has been replaced. While the cache tag for the file entity will already be invalidated by the purge module, it won't do anything, because external caches do not have the cache tags associated with static assets. This is because Drupal, the backend that would add the cache tags to the response, does not serve the static assets. The web server (Apache/Nginx) does.
So, we should be able to purge based on URL instead of cache tag.
This won't purge file assets stored in the browser. We cannot do anything about that, but instruct site owners to lower the cache lifetime.
Active
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Added a patch that will invalidate the cache tags for the replaced file thus invoking drupal to purge the required files cache and the cache url for the file.