206 results found
-
When there are errors on the servicebus we don't log it. It would help if we logged errors for troubleshooting purposes.
When there are issues with the servicebus it is not possible to see what went wrong many times. You can go to the servicebus and look at the graph and see that there are "server errors" and "user errors" and "throttled messages"but there is no way to see the details of the server errors or the user errors.
Some times we can see a log entry in the CMS logs but not always and I guess it depends on the type of error.
If we had more information it would help when troubleshooting customers having problems with the servicebus.12 votes -
Failover alerts
We need to receive alerts when a site goes into failover. The failover CMS should show a warning that its disabled during failover (instead of error message).
9 votes -
Warning of a duplicate asset when saving from a task to the DAM
Upon uploading to a task there is no indication on whether or not content is a duplicate of what exists in the DAM. If it can not be indicated upon import, then can a warning implemented when attempting to save a duplicate to the DAM?
6 votes -
Allow disabling warmup for integration and preproduction
Integration and preproduction environments are sometimes protected by IP-whitelists and in those cases the warmup step always fails with status code 401. The warmup system waits for about 15 minutes until these requests time out. This increases delivery times to these environments specially when CI/CD is set up.
Ex:
2026-03-10 12:40:24 Information Starting to warm up the targets slots...
2026-03-10 12:40:25 Information Preparing target slot for Go Live (<masked>/slot) (warming up the slot)
2026-03-10 12:52:21 Warning Timed out waiting for all instances for webapp <masked> and slot "slot" to become ready!
2026-03-10 12:52:21 Information Validating deployment ID uniqueness between slots…7 votes -
Quick Edit for Images
Currently, in the PaaS CMS, with Blocks, there is a Quick Edit option on the context menu when you click on a block in a content area. The opens a modal that allows the author to edit the block right there, and even publish, without having to load a whole new page in the CMS. This is nice because it allows for much quicker editing.
We sometimes have cases where a project wants to store a lot of information with each image. More than just a title and copyright. They would like to be able to use Quick Edit on…
8 votes -
UI Change to Distinguish Prod from Preprod and Int
I've been burned a few times by publishing content on the wrong environment, e.g. publishing a change in a test page on Integration only to learn I was actually on Production. Woops!
And it's not just me. I know of times our clients have done this, and other members of our team.
Can I suggest some sort of UI indicator (other than just the URL) to indicate which environment you're on?
- Maybe you could output the name of the environment in the header?
- Maybe you could you update the 'Publish Changes' button to read 'Publish Changes to {ENVIRONMENT}'?
5 votes -
Add page or block deletion to approval workflow
My role: Expert Service Application Engineer.
We’re working on adding a deletion workflow similar to the existing approval workflow.
Outcome: We need the ability to configure an approval process not only for publishing content, but also for deleting it.8 votes -
Customer Feedback: Improve CMS UI visibility for Optimizely Graph synchronization status
I am a Technical Support Engineer submitting this feedback on behalf of a customer. The customer is using Optimizely CMS and relies on Optimizely Graph to synchronize content between the CMS and the search index.
Currently, the CMS shows synchronization status only under the Options menu. The text labels such as "Not changed since last publish" or "Synchronize with Optimizely Graph" are not visually prominent. Editors cannot quickly determine whether a page is already synchronized, out of sync, or requires re-synchronization. This makes it difficult for editors to know the current state of content without navigating menus.
The customer suggests…
3 votesWe’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!
-
Support Newer .NET WebApplicationBuilder
I would like to use the newer WebApplicationBuilder / IHostApplicationBuilder introduced in .NET 6 to initialize the CMS instead of the .NET Core 3 method of using IHostBuilder, because .NET Aspire does not support IHostBuilder. The ConfigureCmsDefaults method does not support WebApplicationBuilder, and even though the following code will compile, the CMS is not usable:
var builder = WebApplication.CreateBuilder(args);
builder.Host.ConfigureCmsDefaults();4 votes -
HSTS on the root domain
We are experiencing some redirection issues we have no control over as they are done in the root domain.
http://oldsite.com redirects to https://www.oldsite.com then finally to https://www.newsite.com
The redirection should be as follows:
http://oldsite.com -> https://oldsite.com -> https://www.newsite.com
Please update Optimzely’s configuration to do these redirects properly
30 votes -
Regenerate Content Graph keys and secrets through Paas portal
Clients should have the ability to regenerate Content Graph keys and secrets in the self-service Paas portal.
6 votesGood news - this idea is now being explored by our product and design teams. We’re researching potential solutions and scoping out what an implementation might look like. We’ll share updates here as our thinking evolves.
-
Implement SRI attributes for injected JavaScript & Styles
The Optimizely PAAS CMS platform has multiple touchpoints where scripts are injected into the frontend UI. Examples include Optimizely Forms, Content Recommendations, Search & Navigation etc.
When these scripts are injected into the UI, they are not added with a Sub-resource Integrity attribute. An SRI check allows us to instruct the browser that it should not load a tampered version of a JS or CSS file and can protect users from man in the middle attacks. You can read more about SRI here: https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
This is a commonly reported issue in penetration tests and clients are becoming increasingly more security…
10 votesThanks for raising this - just to let you know this is now in our backlog. While we can’t share an exact release date yet, this means it’s planned for consideration in the future. Thanks for helping us prioritize this work.
-
Site-specific Wastebaskets for multisite
As of now all sites share the same Wastebasket in a multisite. We need site-specific wastbaskets so that only the editors with access to a site (and wastebasket) can go to the site-specific wastebasket and delete content. Closing in to almost 100 sites with extreme amounts of data, our wastebasket is not possible to navigate - even for admins.
3 votes -
Media Publishing Confusion
Media Publishing Confusion: Contributors often forget to publish or submit new/updated media (e.g., PDFs, images) for review, as the system does not prompt them, resulting in drafts being left unapproved.
2 votes -
Versioning Limitations: Updates to blocks (even within a page) do not trigger version updates or review requirements for the parent pgge, ma
Page‑level updates are not reflected in version history:
When a block on a page is updated, the page‑level version history does not show the recent change. Instead, version history is tracked only at the block level, not for the page as a whole. As a result, it can appear that a page has not been updated even when changes have been made.For example the Child Health Policy Accelerator | SickKids page was updated couple of days ago, but the last update details are showing of October 2025.
2 votes -
Reviewers lack visibility into where blocks and media objects are used across the site, leading to time-consuming searc
Reviewers lack visibility into where blocks and media objects are used across the site, unless someone published the landing page/parent block where the block is supposed to be placed. This lead to time-consuming searches and uncertainty during approval.
2 votes -
Access restricted for Specific user with expert import
We need to configure roles in Optimizely to grant specific users permission to use the Import and Export functionality.
Access must be restricted based on the users’ assigned business units. For example, if a user is assigned access only to Asteco, they should be able to perform import and export activities strictly within the business units (e.g., Asteco and Pactive) aligned with their permissions.
Users must not have visibility of or access to any other projects beyond their assigned business units.
3 votes -
Disable Allowed Content Types Description in CMS 12 Edit View
In CMS 12 Episerver Edit interface we noticed a new feature: above all ContentArea fields, a description appears listing allowed content types (Refer attachment).We’d like to have this removed. It seems to add more confusion than clarity for our editors. We already enforce allowed content types using the [AllowedTypes] attribute in code, so displaying the full list in the UI—especially including unrelated options like Episerver Forms elements—is unnecessary and distracting.
This description wasn’t present in CMS 11, and we would prefer to maintain that cleaner editor experience.9 votes -
App Insights alerts
Self-serve creation of alerts in App Insights based on specific thresholds exceeding a limit will help be proactive in responding to potential performance issues or other problems
10 votes -
Ability to smoke-test more than 1 site during smooth deploy (slot domains)
Ability to smoke-test more than 1 site during smooth deploy (slot domains)
As a CMS developer and QA specialist we want to be able to smoke-test multiple sites so that we can detect potential issues on all our sites during deployment with DXP Cloud Platform to our multi-site CMS platform.
When we deploy to PREP/PROD we get a temporary SLOT to run our smoke-tests against. For example:
https://projectidprep-slot.dxcloud.episerver.net/
https://projectidprod-slot.dxcloud.episerver.net/
These are the default URL provided by Optimizely and are configured on the first website. We would like to be able to smoke-test multiple sites on the SLOT instance.
We could…
5 votes
- Don't see your idea?