254 results found
-
Allow upload destination selection for upload element in Optimizely Forms
There should be an option to specify the destination folder directly in the Optimizely Forms upload element. Currently, I can’t manage access rights for uploaded files stored under contentassets. Saving them to a folder under globalassets would let me set the appropriate permissions for the files separated from the Form/Upload element.
8 votes -
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.22 votes -
Add Ability to Star or Favorite a Page
Our design team would like the ability to star or favorite select pages for their own personal view within the CMS. This could manifest in several places in several ways, but the goal is to be able to access specific pages more easily without having to rely on the (at times glitchy or tedious) search function.
Perhaps in Dashboard, you could add more than "workflow status" - but also add "recently worked on" or "recently viewed" or "starred/favorites". Or simply in Edit mode in the page tree pane off to the left, allow for the ability to sort/filter the pages…
17 votesThanks for sharing this recommendation. This is something we have discussed and would like to pursue in future. In the meantime we will continue to monitor feedback on this topic
-
CMS13 - EpiServer.Forms.Samples
We upgraded to CMS13 recently, and found that the package EpiServer.Forms.Samples is not upgraded yet. Since we use recaptcha this is blocking all our forms.
Can EpiServer.Forms.Samples be upgraded to support cms13?
9 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.22 votes -
CMS 13 Content Manager UI - Ability to identify expired assets
When authors use the CMS 13 Content Manager UI image picker, expired assets are displayed without any visual indication that they are no longer valid.
This allows authors to unknowingly select expired images, resulting in broken images after the page is published.
We would like to see an "Expired" badge or status indicator on asset cards, similar to the indicators shown for expired content in the CMS tree view.
Additionally, a filter option to show or hide expired assets would help authors avoid selecting invalid content.
This is currently a significant usability issue that creates unnecessary rework and frustration for…
7 votesThis 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 progress develops.
-
Color palette change (Plae Green is not good)
My team who use the PIM product brought the new color palette change to my attention. The color is abrasive and makes spending time in the application unpleasant. What were useful color cues on the product page have become monochromatic scales that are easily lost on a design that doesn't seem to have been vetted for usability in any way. I suspect the color design doesn't meet WCAG in any way.
While the branding is strong, we are already captured customers, and usability is our key concern. Please offer a way to revert or select an alternate color scheme.
9 votes -
Synonyms and "Pinned results" admin UI for custom Graph sources
We are indexing custom entities to a custom source in Graph (that is, to a source named something other than "default").
Since the editor UI for synonyms and "Pinned results" defaults to the "default" source behind the scenes (it does not allow you to specify any other source), it is impossible for our customer to use the synonyms or "Pinned results" features within our custom source.
We want a source-dropdown in the synonyms UI and the "Pinned results" UI. See attached image for an example.
5 votes -
Dashboard for Enterprise Headless CMS
Enterprise CMS Headless architecture: Customer Dashboard for usage and platform health.
• Greater visibility and proactive reporting on their environment usage and performance. Specifically a dashboard (or reporting capability) that shows: • Usage/consumption metrics • Traffic patterns • Response times • Proactive monitoring data to help identify issues (e.g., 404 errors) before they become support tickets • The ability for customer teams to independently access this data, rather than having to request it from OptimizelyHaving this available standard vs. a custom build. This will help Enterprise customers shift from reactive issue handling → proactive management of their Optimizely environment
9 votes -
Monitor Health of All Instances in the Load Balancer
Health checks on DXP PaaS sites - as I understand it - go via the load balancer. I understand they make a simple http request using Pingdom.
If my DXP application is running on 5 servers and one of them is having an issue, there is a one-in-five chance that the health check's request will hit that server and flag a degradation.Can the health check strategy be broadened to monitor the health of every instance and trigger an alert when any of them is failing?
3 votes -
Expose categories in Graph
Categories are part of CMS 13 but they're not supported by Graph yet. We use them for filtering content.
8 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!
-
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…
9 votes -
Search Management
Add support to see actual graphlql queries in Search Management/Performance view. Now it shows only names of the queries.
5 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.
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 -
geopoint
I'm a developer trying to solve customer needs for sorting results from graph queries by geolocation. Sorting by geolocation is a vital part of meeting customer expectations and would be greatly appreciated to get solved as we are now performing multiple cursor queries in order to sort by a customers location.
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
- Don't see your idea?