Caching issues for Client Extension for Doors Next Generation
I am developing a client extension/widget for Doors Next Generation (DNG) version 7.1. I have noticed that the browser will often cache the widget and not display the updated widget unless I manually go to the xml file defining the entry point for the widget and do a hard refresh for it in the browser, and repeat the same process in the browser for each html file for the widget . Simply refreshing the widget via the dropdown menu for the widget in DNG does not always work regarding getting the widget to update, and even manually removing and adding the widget back does not always work. Has anyone else encountered this issue? Was wondering if there was a solution to this outside of the manual hard refresh method.
One answer
Unfortunately this is mostly a browser issue - I've had the same problem with both DNG and EWM client extensions, and it's particularly annoying when you're developing because of the frequent changes to things.
I found I could go into the developer tools for the browser and delete the specific cached files, and that was my way around it. Would be great if you could set some sort of no cache list in the broswer