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 392

Give warning in Visual Studio if Optimizely nuget package has security vulnerability

I do not get a warning for a vulnerable package from Optimizely like the 4.30 version of Forms. Currently visual studio gives warning if solution contains packages from nuget.org that has a security vulnerability. This is a really nice feature tha...
8 months ago in Content Management / Technical 0

Move render-blocking EpiserverForms JavaScript out of document head

Google PageSpeed Insights reports the WebResource.axd containing the Episerver injected JavaScript in the page head is render-blocking. jQuery here, loaded as a dependency of the Episerver Forms js blocks page rendering by an estimated 300ms dimin...
over 3 years ago in Content Management / Forms 2 Investigating

New cache architecture for the platform

Currently there exists a large number of different caches used in CMS and all its addons, Optimizely codebase primarily uses ISynchronizedObjectInstanceCache (implemented by RemoteCacheSynchronization) but there are a lot of other caching mechanis...
about 1 month ago in Content Management / Technical 0

Support for Managed Identity in EPiServer.Azure

We are hosting Optimizely CMS in Azure for some customers so we are using the EPiServer.Azure nuget package for connection to Azure Storage Account and Azure Service Bus. To do this we have use the SAS key connection string. Are there any plans to...
about 1 year ago in Content Management / Technical 0

Add horizontal scrollbar to page/asset pane and model windows.

As a CMS user, the page pane, asset pane, and page/asset selector modal should display horizontal scroll bars when trying to view deeply nested content items. This will improve navigation and prevent content item names from being cut off.
9 months ago in Content Management / Editing 0

TinyMCE - Paste clean HTML from Word by default

The epi-paste functionality is confusing to our authors. They tend to select "Keep formatting" which keeps all of the Word styles in the HTML. We want clean HTML to be pasted in by default. We would like a way to just set the default behavior to p...
about 1 year ago in Content Management 0 Future consideration

Add validation notifications on property tabs and property labels

When editing a page/block, the property validation feature is great to prevent editors publishing an incomplete or sub-optimal piece of content. However, the validation notification is only shown near the Publish dropdown menu, and the editor then...
over 1 year ago in Content Management / Editing 0

Being able to delete/move to trash orphaned blocks and media

As an editor I would like to be able to remove/move to trash a block or a media content item from the property view in the CMS. As it is now you need to have the Block or Media widget open, and if a piece of content is orphaned you don't see it in...
over 3 years ago in Content Management / Asset Management 1 Investigating

[Feature request] Display forms in 'For This Site' and 'For This Page' sections when creating an EpiServer Forms criteria under Audiences

Dear Team, Currently, when setting up EpiServer Forms criteria in Audiences, we can only select forms listed under the 'For All Sites' section. However, our business also requires the use of forms from the 'For This Site' and 'For This Page' secti...
3 months ago in Content Management / Forms 0

Specify which domain is the editorial domain / Be able to view the website on the editorial domain

On many of our clients websites we have disabled the /Episerver path on the customer facing domain and have a separate subdomain where editors work. This works great, but in a multi site/multi domain context, jumping between sites will lead editor...
about 1 year ago in Content Management / Multi-site 2