You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When replacing an existing asset file via the control panel, the old version of the file is still shown when clicking the "View" link, until the page is manually refreshed. It seems like the browser is caching the original file, and the new version doesn't appear right away.
Steps to reproduce
Go to Assets in the control panel
Click on a file
Go to Settings → Replace file
Upload a new version of the file
Expected behavior
The newly uploaded file should be visible immediately.
Actual behavior
The old file is still shown unless the page is manually refreshed.
Suggestion:
Could the page auto-refresh, or the asset link be busted (e.g. with a query string or timestamp) to ensure the latest version loads?
Craft CMS version
5.6.16
PHP version
No response
Operating system and version
No response
Database type and version
No response
Image driver and version
No response
Installed plugins and versions
The text was updated successfully, but these errors were encountered:
What happened?
Description
When replacing an existing asset file via the control panel, the old version of the file is still shown when clicking the "View" link, until the page is manually refreshed. It seems like the browser is caching the original file, and the new version doesn't appear right away.
Steps to reproduce
Expected behavior
The newly uploaded file should be visible immediately.
Actual behavior
The old file is still shown unless the page is manually refreshed.
Suggestion:
Could the page auto-refresh, or the asset link be busted (e.g. with a query string or timestamp) to ensure the latest version loads?
Craft CMS version
5.6.16
PHP version
No response
Operating system and version
No response
Database type and version
No response
Image driver and version
No response
Installed plugins and versions
The text was updated successfully, but these errors were encountered: