Lukas Renggli wrote:
I forgot to
make it clear that the situation is for different login sessions
- i.e. the settings change is made in a designer session, but in a
concurrent guest session, the settings change only appears if I let the
guest session expire, then login again.
Indeed, in other sessions the changes are not reflected immediately.
I don't think I need the refresh command anymore, now that I've noticed
that Logout/Login was reusing the session. Going to a URL without the
_s/_k will create a new session, which will then have a new component
using the new settings.
What was worrying was that I did not have a way for a non-logged-in user
to refresh, except to wait for expiry. Then I noticed that even a these
users had a _s/_k in their URLs.
BTW, I do see the changes immediately, in the session where the changes
are made.