New customization package = force browser cache refresh
Primo VE's browser cache is much too strong.
After the upload of a new customization package I have to check the changes in a new private window and tell my colleagues to test in a new private window.
Recently I got sent a fresh screenshot by a patron which showed a styling element that we have changed several months ago.
We can't ask our patrons to use Primo VE in a private browser window if they want to see the up to date version.
=> When uploading an adapted customization package, there should be a forced refresh of the cache in the browsers, either automatically or at least as an option that can be checked.
[By the way, having to choose between 'Primo VE' and 'User interface' to be able to post this makes no sense.]
Manu Schwendener
shared this idea
Hello All,
This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 30 votes.
This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.
We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Primo.
Best regards,
Primo Product Team
-
Working fine now in Firefox and Chrome on Mac: no refresh necessary to show updated text on start page.
Please close to free the votes.
-
It seems to me that this has gotten much better by now.
'Reload' still not enough, but shift+reload is now working.
Please close the idea to release the votes.
-
Thank you, Stacey.
-
Stacey van Groll
commented
Hi Manu - it should just be 'User interface' category, as this is not specific to VE model but for Primo as a product.