There must be a simple solution to this but I haven't been able to find one…
After using "Upload File" to replace an existing file, one of our editors noticed that the link to this pdf was "broken" when they viewed the page on the live site (OK in preview). The updated file was using a new name, so the webpath had changed but the frontend was displaying the path to the old version. Obviously this was a caching issue and I cleared the page manually.
I have a trigger to clear the cache when a page's contents are updated but how do I ensure that links to files are automatically updated when someone replaces an existing file?
On v3.18.9.
Thanks
[quote]There must be a simple solution to this but I haven't been able to find one…
After using "Upload File" to replace an existing file, one of our editors noticed that the link to this pdf was "broken" when they viewed the page on the live site (OK in preview). The updated file was using a new name, so the webpath had changed but the frontend was displaying the path to the old version. Obviously this was a caching issue and I cleared the page manually.
I have a trigger to clear the cache when a page's contents are updated but how do I ensure that links to files are automatically updated when someone replaces an existing file?
On v3.18.9.
Thanks[/quote]
From experience, the most efficient way it to ALWAY use the same filename when replacing the file. Then, you never have to worry about Matrix caching, because the user will just grab the new version of the file since it uses the same name as the file it replaced.
Thanks Nic.