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.

We are pleased to announce that beginning on Tuesday, March 25th, we are launching a new feedback experience for our customers!

The new experience should transition over seamlessly, but please be aware that short interruptions to our feedback portal may occur on March 25th between 2:30-4:30pm EDT.


All the best, your Optimizely Product Team

Add feedback Subscribe
Product Content Management
Categories Editing
Created by Guest
Created on Jan 19, 2023

RELATED FEEDBACK

Easier cleanup of unused blocks

Maintaining the number of blocks is important to editors. When using Powershell module you can get a list of blocks that are not in use so editors can maintain content on the site.

The problem is that blocks that are located in "For This Page" folders does not contain the page information in the breadcrumb (see attachment). This means that it's hard to find the folder containing this block if you want to delete the block. Extending the breadcrumb to include the owner (page) of the folder "For This Page" would help the editors to know the location.

2023-01-19_09-0...
2023-01-19_09-05-23.png
Open full size
2023-01-19_09-05-23.png
  • Post comment
  • Guest
    Reply
    |     Mar 18, 2025

    As part of a content migration, a number of template pages were created with preset blocks. These have then been copied and had new content added to them. As part of this, they now have thousands of blocks that are not in use across the system. They have wanted to check for all usages of a test image, but this is flagging up so many of these items, but when they navigate to a usage of it, they can find the block, but cannot find the parent so that they can delete the block.

    There is a fundamental flaw here in that the UI does not allow you to delete the content item you're viewing, you have to delete it from the content tree, but when you find content in this way, the breadcrumb does not show you the page that owns the "For this page" folder, so you cannot navigate to the page as a CMS editor in order to delete the content item.

    Our client's only option now appears to be to navigate page by page through the entire content tree and clean up the blocks. Or alternatively we have to write custom code that does this for them. This should just be easier within the interface.