Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Force updates of UI elements #9968

Closed
5 tasks
wezell opened this issue Oct 13, 2016 · 1 comment
Closed
5 tasks

Force updates of UI elements #9968

wezell opened this issue Oct 13, 2016 · 1 comment
Assignees
Labels

Comments

@wezell
Copy link
Contributor

wezell commented Oct 13, 2016

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.

@wezell wezell modified the milestones: Cody Current, Cody Next Oct 13, 2016
@jgambarios jgambarios changed the title Create a way to force an update of UI elements Force updates of UI elements Oct 31, 2016
@jgambarios jgambarios modified the milestones: Cody Next, Cody Current Oct 31, 2016
@jcastro-dotcms jcastro-dotcms self-assigned this Nov 2, 2016
@wezell wezell removed this from the Cody Next milestone Nov 7, 2016
@stale
Copy link

stale bot commented Sep 28, 2019

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.

@stale stale bot added the wontfix label Sep 28, 2019
@stale stale bot closed this as completed Oct 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants