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.

ADD FEEDBACK

Editing

Showing 78 of 1746

Improve possibilities to group larger quantities of items under the same node without affecting the URL segment

I want to be able to group content in "buckets" without affecting the URL. Container pages have been used, but this is not ideal since they add a URL segment and we want to try and avoid to remove this by tweaking into some central parts of routin...
about 4 years ago in Content Management / Editing 0 Future consideration

Cludgy solution for finding content references (moving to trash)

If I want to find internal pages that link to a page, I usually click Move to Trash to get a list of internal references, and then Cancel. Grzegorz Wiecheć has made a nicer solution to this issue: https://gregwiechec.com/2015/06/displaying-related...
about 4 years ago in Content Management / Editing 0 Future consideration

Content referencing list does not show full path

When viewing the content referencing list for a content item the full path to the item is not visible. This makes it hard to see at a glance where the content is being used
over 4 years ago in Content Management / Editing 0 Future consideration

Allow container pages that don't generate a URL segment

Some functionality cascades down the page tree, like approvals or permissions. Sometimes you want to group pages together so you can apply values and functionality to branches of pages, but these necessarily affects the URL, since any page generat...
over 4 years ago in Content Management / Editing 0 Future consideration

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 ent...
over 4 years ago in Content Management / Editing 0 Future consideration

Title missing on images in the Text editing fields

The mouse-over titles are missing in images added in the Text editing fields. This is a normal feature on all CMS:s so it's strange that I can't see it. This would help me make more accessible web content.
over 4 years ago in Content Management / Editing 1 Future consideration

Side panel improvements

One side panel collapses, one is still open. I want to be able to show sites in browsers on different screens. Active panel opens all sceen, others collapses and move to top.
almost 5 years ago in Content Management / Editing 0 Future consideration

Blocks in context of pages

I want blocks to behave as if they were part of the page, rather than separate entities. Primarily on the approval step.
over 5 years ago in Content Management / Editing 0 Planned