We have moved to GitHub Issues
Created by Douglas Robar 14 May 2014, 11:01:41 Updated by Shannon Deminick 26 Jun 2017, 07:13:12
Back office caching is too aggressive, especially when packages are installed.
For example nearly a quarter of students had this problem on the last class:
Opening in another browser or using the dev tools in Chrome to not cache when the dev tools are displayed clears the cache and the links work.
But users aren't going to know to do this. Nor will they want to do it even if they know. Instead, they'll think Contour or Umbraco is just badly and frustratingly obviously broken.
Indeed, caching of the back office is too aggressive generally. I'd rather have a slightly slower UI that doesn't exhibit this problem, it would give Umbraco a better impression to both new and existing users than the way it currently behaves some times. "Performance" is a feature to add later. "Broken" is the perceived problem at the moment. Better to be slow-ish than break quickly in this case I think.
I too have similar issues with the caching being too aggressive in the backoffice.
For example: in the "Settings" section, I'll edit a template file and save it, navigate to a partial view file (but do nothing), and then navigate to that original template again by clicking it in the list and it will show me the template as it was BEFORE I saved my changes I made in the beginning (that were supposedly saved). If I edit the template, save it, and then fully reload the "Settings" page (think CTRL-SHIFT-R in Chrome), then the previous version problem doesn't exist. It's caching the first version loaded, and using that cache even after I save the file.
Closing issue due to inactivity - see blog post for details https://umbraco.com/blog/issue-tracker-cleanup/
Backwards Compatible: True
Affected versions: 7.0.4, 7.1.1
Due in version: