Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Status Future consideration
Categories Editing
Created by Guest
Created on Feb 25, 2020

Users would benefit from the ability to refresh their current view in the content tree without refreshing the browser.

Though we use sockets to provide some real-time communication, the content tree doesn't always reflect the most recent changes - particularly in folders in the asset pane or sub-items in the page tree.


To test, open two separate browsers and enter edit mode. Create a child folder in browser A and the changes aren't automatically reflected in browser B.


Options to resolve might include:

  1. Doing more with the sockets to have the changes occurring in one browser pushed into all other connected browsers
  2. Adding a simple refresh button to the context menu for folder-style objects in the asset panel or all pages in the page tree to refresh child items manually

Sample code for option #2 can be found here: