15 results found
-
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.
8 votes -
Optimizely CMS 13 should run on .NET 11.
Optimizely CMS 13 should support running on .NET 11.
Today, CMS 13 officially supports .NET 10, but attempting to run it on .NET 11 currently fails because of a breaking runtime change that results in a System.MissingMethodException.
I have documented the current issue, including a workaround, here:
https://www.gulla.net/en/blog/upgrading-optimizely-cms-13-from-dotnet10-to-dotnet11/The request is not necessarily to make .NET 11 the recommended production runtime, but to make CMS 13 compatible with it where this can be done without affecting .NET 10 support.
1 vote -
Make unshared blocks shared and vice versa
When working in CMS13 it would be great to have the ability to make standard blocks shared for better governance of content and similarly the reverse; to take shared blocks and localise them (essentially using the shared block as a template and branching it off to allow customisation). We'd require the ability to easily track these content blocks over time.
1 vote -
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 -
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 -
Preview capabilities for Projects (CMS13)
Right now there's no capability to preview all the content in a project prior to publish. It would be great if this can be considered for CMS13.
1 vote -
Cannot create custom folder-type instances inside shared blocks from the CMS UI
In Optimizely SaaS CMS there is no way to create an instance of a custom folder content type (a content type based on the folder / _folder base type) inside a shared block through the CMS UI. The New Folder action creates only the built-in system folder type and offers no picker to choose a custom folder type. Separately, the New Folder action is currently not working at all in this context. As a result, custom folder instances can only be created via the Content Management REST API or Opal.
Steps to reproduce:
- Define a content type based on the…
2 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 -
Preview in Visual Builder in CMS 13
In CMS 13 (with page type configuration), it is great that editors can easily see and build the content that they are working on in Visual Builder, clicking on properties to be able to edit them inline and immediately see the changes to the page. However, it is still important for editors to be able to preview a page before publishing it so that they can for example test links and see the content in its entirety before publishing.
When working with Visual Builder the Preview button is currently "hidden" beneath the Compare button so that editors need to click…
1 vote -
Allow setting Title to tinyMCE video element (WCAG A level requirement)
Content creator currently cannot set title to tinyMCE video element which means it breaks the WCAG A level requirement: https://www.w3.org/WAI/WCAG21/Understanding/non-text-content.html
tinyMCE can be overridden to allow custom attributes including title but it would need content creator to understand application code in order to apply the value
1 vote -
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 -
Irritating double load when clicking menu in OPE mode
Our editors often use the sites menu in the OPE mode to switch pages and the menu is built so it uses the editmode link in OPE mode and the normal link in view mode to accomodate this.
When clicking a menu item in episerver 11, the page is loaded more or less at once, but in episerver 12 the page is first loaded in view mode and then reloaded in edit mode. This happens with all the links in the menu.
The editors find this very irritating. We haven't been able to figure out why that happens.
I tried…
1 vote -
Remove the Paste formating options while being able to choose if it should keep or remove default formating by default
When not using 'power paste' options from TinyMCE, and you copy formatted information from a Microsoft Word document, you get the "Paste formatting options" popup that asks if you want to Remove or Keep the format (view screenshot). Currently, it is possible to remove this popup by using the confirmation ".RemovePlugin("epi-paste");", but the default and only option when the popup is gone is to keep formatting.
This request is to give an option to change the default value when removing it, between "Keep formatting" and "Remove formatting", and not forcing into always keeping formatting.
Thank you,
1 vote
- Don't see your idea?