230 results found
-
Immutable Backups
Immutable Backups are increasingly becoming cybersecurity and resilience best practice.
Currently CMS PaaS data is not covered by immutable backups. To further protect us against ransomware attacks and accidental or malicious data tampering having this as a standard or at least optional feature would be highly desirable, providing a reliable last line of defense for fast and trustworthy recovery after a cyber incident or operational failure.
Any update on timeline for its availability would be very much appreciated.17 votes -
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.14 votes -
API support for environment copy-back lifecycle and post-copy script execution
As a development team managing multiple lower environments, we want API/PowerShell endpoints to orchestrate the full copy-back workflow, including a mechanism to run registered post-copy maintenance scripts, so that I can automate environment refresh end-to-end without manual PaaS Portal interaction.
Currently, the copy-back workflow requires manual steps in the PaaS Portal (stop environment, copy databases/blobs from Production, start environment). After the copy, teams must anonymise PII from the copied databases to comply with GDPR before the environment can be used. This anonymisation step cannot be triggered or orchestrated through the platform.
We would like the EpiCloud module or REST API…
7 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 -
Difficulty locating the "Automatic published media on upload" setting in CMS 12
Location of Settings in CMS 12: Difficulty locating the "Automatic published media on upload" setting in CMS 12, which affects workflow and publishing behavior.
6 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.
6 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.
6 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.
6 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 -
select content
As a content editor,
I want to search for existing blocks within the “Select Content” shortcut window, so that I can quickly find and reuse the required content without manually browsing through multiple options.Background / Problem Statement:
Currently, when creating a new block in Optimizely CMS, users are presented with two options:
Create a new block
Select contentWhen selecting “Select Content”, a shortcut window opens displaying available blocks. However, this window lacks a search functionality, making it difficult and time-consuming to locate specific content, especially when the number of blocks is large.
Navigation Path:
Main Content → Select…
4 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 -
Dynamic Scaling in DXP - improve performance and reduce costs
The default hardware SKU for Optimizely is P1V3. P1V3 only has 2 cores and P2V3 has 4 cores. Because the number of cores available to the system dictates the number of default threads the system attempt to regulate, it would be best to deviate away from our current default hardware SKU, P1V3 to P2V3, instead. However, doing so would increase costs which we do not want to do necessarily. This is a proposal to decrease costs while simultaneously increasing hardware resources during peak hours.
The idea is to increase a customer's lower environment hardware to P2V3 during "working hours" (to…
1 vote -
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 -
IQI Report - App Insights as the Source of Truth
There are multiple similar functions happening that are similar within Optimizely. They all need to be utilizing the same data a the singular source of truth. They are:
Incident Management, primary data is App Insights.
Deep diagnostics done by Problem Management, primary data is App Insights
App Insights Dashboard
IQI Health Check reporting, primary information (aside from pingdom's availability info which for legal reasons) is Cloud Flare for health information.
The inconsistency of source data causes issues because we cannot make a consistent presentation of the information when the source being utilized is entirely different.
It also adds possibility of…
1 vote -
Editor Content Health Dashboard : A personalized, self-service governance view for every content editor in the CMS
As a content editor, I want to see a personalized dashboard when I log in to the CMS that shows me only the content I own that needs attention, so that I can find and fix issues myself, without waiting for someone else to tell me about them.
This dashboard replaces the generic default view in the CMS for all content editors. It does not replace any existing admin tools or reports. The intent is to move content governance from a reactive, admin-led activity into a proactive, editor-led habit. The dashboard is the trigger for that behavioural shift. This is…
2 votes
- Don't see your idea?