Here is the scenario:
Have two computers (say home and work) working with the same Cloudify user over the same manager
Use both to view a certain page in the manager UI.
Add a widget to the page using computer A - widget is added and can be seen as expected.
open the same page from computer B using the same account - The widget does not appear.
refresh the browser cache on computer B - the widget appears.
The scenario above is not uncommon and I am sure there are similar usecases. That said, the workaround is very easy so if the cost of a fix will mean degraded performance or other impact please let me know before fixing.
Can we add some flags that will avoid caching of the page structure?
Just highlighting that this should be last on our 5.1 list. It is not regarded as a Showstopper.
Are you sure browser refresh with clearing cache is necessary?
I tested a bit different scenario. Instead of two computers, I used my laptop with two different browsers (Firefox and Chrome), in normal mode, not in incognito/private mode. After adding/removing the page or widget I only needed either re-login or page refresh (no need to clear cache) to see the change. I think that is OK and we don’t need real-time (without relogin or page reload) change visibility. I used two different stage instances - local (127.0.0.1:4000) and RS (10.x.x.x). The behavior was the same in both cases.
You used two, physically separated machines. It’s a bit harder for me to have such configuration, so before I move on, I’ll wait with for confirmation from you that it (necessity to clear cache) is really the case here.
I tried it the same way as you did - add the widget in one browser, and refresh the view on a second browser on the same computer and shared your results - it was enough to either logout-login or to hit simple refresh (no cache flush) to get the new widget. so this worked well.
I wasn't sure if this is version related, so tested with 5.0.5 and had similar results.
Seeing that on separate computers I saw this issue more than once, perhaps this is related to some caching done by the webserver, hence on the same computer, the info is updated?
let’s look at it together and try to reproduce it
Works as is