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

All feedback

Showing 1601 of 1601

Automated product data enrichment

As a client, I want enriched metadata and descriptions of my products to be automatically created, to save me doing it manually, to improve search results and to entice visitors to purchase products.
over 3 years ago in Data Science / Merchandiser Experience 0 Future consideration

Public API for accessing automatically created related queries

As a developer I would like a way to retrieve and potentially delete or modify the automatically created related queries(a feature of search and navigation). In some cases the "Did you Mean" feature will give bad results, so companies need a way t...
over 3 years ago in Search & Navigation 2 Planned

Search within a geographical location

As a developer I want to be able to search within an area. For examle "Find all dealers within 100 miles from this location". Something like this: var result = SearchClient.Instance.Search<DealerProduct>() .Filter(x => x.DealerLocation.Wi...
over 3 years ago in Search & Navigation 1 Future consideration

Add an option to DXC for a NodeJS server in addition to an Episerver instance

I want to have a NodeJS server running on Azure, alongside my Episerver instance. To start, this would be a simple, naked NodeJS instance. I could do whatever I like with this. It would be deployable apart from the Episerver instance -- I could pu...
over 3 years ago in Content Management / APIs / Technical 1 Investigating

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

Corporate license

As a Company I want to have a possibility to manage one license/package for many websites so that administration is less time consuming
over 3 years ago in Content Management 1

A more competitive price for the CMS license

As a customer I want to be able to pay a price to use the product that is reasonable and competitive compared to similar products so that I can choose Episerver CMS as platform instead of alternatives like Umbraco or Wordpress. Money I spend on li...
over 3 years ago in Content Management 2 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

Automatic summarization for content

As a client, I want summaries of my articles automatically created, so that I can entice readers to sign up or purchase.
over 3 years ago in Data Science / Editor Experience 0

Epi DXP support for Cloudflare Workers and Apps

As a digital marketing manager responsible for organic search traffic, I would like Epi DXP to support Cloudflare Workers and Apps so that I can use the Ranksense App to make content adjustments at scale for SEO meta, schema and HTML data in a no...
over 3 years ago in DXP Cloud Platform 1 Future consideration