26 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.6 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 -
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 -
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…
3 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 -
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 -
IP Address restriction in Cloudflare
It would be great if we could configure an IP Address whitelist in Cloudflare so that we only allow a specific set of source IP Addresses to be allowed to access our DXP instances. This will allow us to block public access to non-production environments
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 -
Visual Builder: When changing style settings or property values in the outline panel, the left preview panel always refreshes
CMS SaaS: I have just converted my project from using @remkoj/optimizely-cms-nextjs to @optimizely/cms-sdk, but the live preview sync for style settings and property value updates is not as smooth as with @remkoj/optimizely-cms-nextjs.
Previously, my project worked very smoothly in Visual Builder mode. It only updated the element I changed and did not refresh the entire iframe.
However, after switching to @optimizely/cms-sdk, whenever I update anything, it always refreshes the preview iframe, resulting in a very poor user experience.
Is this expected behavior, or am I missing something?CMS 13: We’re seeing the same full iframe refresh issue on Optimizely CMS…
1 vote -
Add .NET Counter publication to App Insights on Startup
There are a whole suite of .NET counters available to use to publish to App Insights. This is a low-lift modification that enables us to gain many insights, directly inside of App Insights Metrics, we can utilize to diagnose issues on customers.
This enables us to do performance investigations that otherwise require manual intervention (such as downloading .ETL files and opening them in PerfView or capturing dump files and analyzing them).
We can skip these manual steps and jump write to "close to root causes" by publishing this information. There is little cost and no significant performance degradation associated with…
1 vote -
Assess binding settings to resolve resets
We need to evaluate whether setting the suggested Microsoft setting is worthwhile to resolve resets. As part of that effort, we would have to evaluate the risks of doing so.
1 vote -
Identify and Aid Customers with Production Live-Locks
There's the concept of a "dead" lock and a "live" lock. A live-lock is essentially a race condition within a production environment. It causes stair stepping of CPU usually until the server crashes.
This often happens when a developer accidentally uses a non-thread safe object in a multi-threaded manner.
The object (for example a HashSet) being used needs to be identified and a thread safe type needs to be replaced so that the live-lock goes away and the CPU goes back to normal.
1 vote -
Improve “Select All” behaviour for lazy loaded export
We’ve received reports from our users regarding confusion when exporting form submissions.
Currently, when users click the header “select all” checkbox, the label shows:
“All 25 posts are selected.”Because only 25 submissions are initially loaded, the checkbox correctly selects only these items. However, users often interpret this label as indicating that all existing submissions (e.g., all 69) have been selected - even though the remaining items have not yet been loaded via lazy loading. This misunderstanding has led to incorrect or incomplete exports.
To reduce user confusion and better reflect what is selected, we would like to request an…
2 votes -
Visible in menu should be available in Graph
In CMS 13 the VisibleInMenu PageData property is not indexed.
1 vote -
Expose categories in Graph
Categories are part of CMS 13 but they're not supported by Graph yet. We use them for filtering content.
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…
1 vote
- Don't see your idea?