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

Content Management

Showing 425 of 1913

Improve user experience for editors when searching for Pages when multi-site

As an editor, when searching in the Pages gadget, results from all sites are shown. Add a label to indicate what site the result is from. It's possible multiple sites have the same named content. i.e. 'Blog' So it would be ideal to see:Blog [Sit...
almost 2 years ago in Content Management / Multi-site 0 Future consideration

Create UI Builder

Creating custom admin interfaces in Optimizely, is not standardized, so nothing looks the same. It is also too time consuming to build. Umbraco has a really nice UI builder. It's both powerful, easy to use, and creates recognizable UIs. Optimizely...
about 1 year ago in Content Management / Editing 0

CMS 12 Admin UI request - sorting & searching Visitor Groups

In CMS 11, Visitor Groups were sorted alphabetically. Now with CMS 12, the list of Visitor Groups are all "mixed up" and it's hard to maintain when you have +100 of them. Please add sort and search to this part of the administration user interface...
almost 2 years ago in Content Management / Content Manager 0 Future consideration

Scroll issue for DateTime propertyon Macbook

Scrolling for this property is too fast on Macbook (testet Edge and Chrome): [ UIHint ( "TimeOnly" )] public virtual DateTime? StartTime { get ; set; } Adjusting scroll in mouse settings doesn't help.
3 months ago in Content Management / Editing 0

Enable selection of datetime format on DateTime block in EPiServer.Forms

The current implementation of the DateTime element (found in the EpiServer.Forms.Samples package) appears to be insufficient. In the DateTimeElementBlock.js file, the logic used to determine the language format relies on the browser's language set...
6 months ago in Content Management / Forms 1

Make "Additional properties" section optional when creating content

Currently non-required properties are listed under a section called "Additional properties" when creating content. This gives users the impression that those properties should be filled out before clicking the "Create" button. This is particularly...
almost 2 years ago in Content Management / Editing 2 Future consideration

Restrict editor access to other microsites

We want to hide the website tree structure to the user who do not have access (even we want to remove the read-only access). For example we have multiple websites as Website A, Website B ... etc. and EditorA, EditorB ... etc. If EditorA has access...
10 months ago in Content Management / Multi-site 0

Multiple content paths in export feature

As an admin in the Optimizely, I would like multiple pages from different content paths to be exported and imported into another Optimizely environment. Currently to export 5 pages from different content paths makes a user to export and import the...
over 1 year ago in Content Management / Content Manager 0

Improvements local inline blocks

This is the drawback right now with local blocks: There is no way to map the inline local blocks between versions or language contexts. Why not add a GUID? There is no way in the UI (Dojo JavaScript API) to determine if the context is within "inli...
3 months ago in Content Management / APIs 0

CMS 12 removed the fallback language in content area UI

In our solution, we have 31 different languages, and thus a lot of language fallbacks both for pages and blocks. In CMS 11, we could easily spot the blocks in a content area that were a fallback, it would be a slightly darker grey and also had the...
about 1 year ago in Content Management / Multi-language 0