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

Content Management

Showing 56

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...
11 months ago in Content Management / Editing 2 Future consideration

LanguageManager - Allow deletion of catalog item language branches

For CMS pages and blocks, it is possible to delete a whole language branch using the language manager. However, attempting to do this for catalog items in commerce will give the following error: EPiServer.Labs.LanguageManager.Controllers.LanguageM...
about 1 year ago in Content Management / Multi-language 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...
over 3 years ago in Content Management / Editing 0 Future consideration

Search and replace utility

Our CMS authors need a built-in reporting tool that will list all pages, blocks and documents that contain a specific keyword (In strings, xhtmlStrings or external links). Ideally this would allow replacement of the text with another term in pages...
about 1 year ago in Content Management / Reporting 2 Future consideration

Honeypot

There should be a honeypot field to prevent spam submissions without captcha.
over 2 years ago in Content Management / Forms 0 Future consideration

Archive old projects automatically

Automatically archive projects that have not been used for a certain amount of time.
over 3 years ago in Content Management / Collaboration & Approval 0 Future consideration

Listing Page for Projects

As a user I want to see a page listing for all projects in my CMS, both for me and other users across my business. I want to be able to search for projects as I have a large number.
over 3 years ago in Content Management / Collaboration & Approval 0 Future consideration

Forms should be able to show blocks on-page after a form submission

When configuring a Form in the CMS, the "Display message after form submission" rich text area allows blocks and other content items to be added. However when a Frontend user has submitted the form, the blocks will not render in the rich text area...
about 1 year ago in Content Management / Forms 0 Future consideration

Add CMS login auditing

Add historical logging of CMS user logins, including IP address and date and time.This will allow admins to view and track information about possible login hacking attempts and to mitigate these issues.
over 3 years ago in Content Management / Roles and Security 0 Future consideration

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