You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the new Client UI, we have a number of dynamic elements that will need to be refreshed as events happen within dotCMS (but outside of the single client). We need to make sure we have the server side framework to make this happen. The closest analog of what we have in code are our Cache Invalidations. And like the cache invalidations, they will need to be cluster aware
For example:
When user A changes or updates a file in the file browser, user B using the file browser should see the new files or file changes without a browser refresh
When you "login as", the system is refreshing the menu, but we need refresh the host selector too, this because you can see all the host that you don't have permissions as limited user.
When a user adds, deletes or re-permissions a host - client users' host selectors needs to be refreshed. And not just the user who made the change, every user.
When a new portlet or tab is added or removed, people's sidebars will need to be refreshed.
When you login as, we need to refresh the username and profile pic to the person who is being logged in as
Implement the points above using the new Events infrastructure.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had activity within the past 90 days. It will be closed in 30 days no further activity occurs. Thank you.
In the new Client UI, we have a number of dynamic elements that will need to be refreshed as events happen within dotCMS (but outside of the single client). We need to make sure we have the server side framework to make this happen. The closest analog of what we have in code are our Cache Invalidations. And like the cache invalidations, they will need to be cluster aware
For example:
Implement the points above using the new Events infrastructure.
The text was updated successfully, but these errors were encountered: