33 results found

1. 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:

   1. Define a content type based on the folder (_folder) base type and push it to the CMS.
   2. Open a shared block and go to the Assets panel.
   3. Try to create a folder using New Folder.

   Expected: The UI lets you create a folder of the custom folder type (e.g. a type picker), and the New Folder action works.

   Actual: New Folder offers only the built-in system folder type — no way to select a custom folder type — and the New Folder option does not work in this context.

   Impact: Editors can't self-serve folder organisation when custom folder types are involved — every folder creation needs a developer or an API call, which doesn't scale for content teams.

   Request:

   1. Fix the non-functioning New Folder action in the shared-block Assets panel.
   2. Allow creating custom folder-type instances from the UI (a folder-type picker on New Folder), consistent with how other content types are selected.

   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:

   1. Define a content type based on the… more
   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Editing (Content)  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Search Management

   Add support to see actual graphlql queries in Search Management/Performance view. Now it shows only names of the queries.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Graph  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Allow copying the original value for Non-CultureSpecific fields inside Culture Specific list properties during auto-translate operation

   For some blocks we use list properties and define them as Culture Specific. And if there is a non-culture specific field inside the list item block type, the value is not copied or translated due to the implementation in EpiServer code.

   For this case we need to find a way to copy the original value from the master language branch while translating the content. Please add a feature to customize this behavior.

   Thanks.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Translations  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Support keeping the original values for technical fields during auto-translate

   We have a culture specific string field in one block type which is decorated by custom "AutoSuggestSelection" attribute. The attribute allows us to select predefined list of icon types. The problem we face is that the field is a technical field which should not be translated. Even possible it should be copied from the master language. But translation provider automatically translates the field value if it is string and culture specific.

   Please add an option for skipping/copying technical fields during auto-translate operation

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Translations  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Official guidance for HTTP QUERY method support in Optimizely DXP

   Summary

   The HTTP QUERY method (RFC 10008) provides a standardized way to perform safe, idempotent query operations while allowing a request body, addressing a long-standing limitation of GET.

   https://www.rfc-editor.org/info/rfc10008/

   https://tykok.medium.com/the-new-http-method-query-d1dc3efc35c4

   While ASP.NET Core applications can implement support for QUERY, developers deploying to Optimizely DXP also depend on the surrounding platform and infrastructure.

   Request

   Could Optimizely publish official guidance regarding support for the HTTP QUERY method in DXP?

   Specifically, it would be helpful to clarify:

   • Is QUERY currently supported throughout the DXP infrastructure?
   • If not, which components prevent support (Cloudflare, WAF, load balancers, Azure App Service, proxies, etc.)?
   • Are there any security considerations specific to QUERY that developers should be aware of?
   • Will QUERY be treated similarly to GET regarding safe/idempotent semantics where applicable?
   • Is support on the product roadmap, or is it considered out of scope?
   • If there is no current support, what is the recommended approach for developers who would otherwise benefit from QUERY?

   Why this matters

   Many APIs expose complex search and filtering operations that naturally fit a safe, idempotent request but exceed the practical limitations of GET query strings.

   The QUERY method provides a standards-based solution to this problem. As more frameworks begin supporting it, developers will naturally want to know whether Optimizely DXP fully supports the method before adopting it.

   Even if official support is not yet planned, having clear documentation describing the current state and any platform limitations would help developers make informed architectural decisions.

   Thank you for considering publishing official guidance.

   Summary

   The HTTP QUERY method (RFC 10008) provides a standardized way to perform safe, idempotent query operations while allowing a request body, addressing a long-standing limitation of GET.

   https://www.rfc-editor.org/info/rfc10008/

   https://tykok.medium.com/the-new-http-method-query-d1dc3efc35c4

   While ASP.NET Core applications can implement support for QUERY, developers deploying to Optimizely DXP also depend on the surrounding platform and infrastructure.

   Request

   Could Optimizely publish official guidance regarding support for the HTTP QUERY method in DXP?

   Specifically, it would be helpful to clarify:

   • Is QUERY currently supported throughout the DXP infrastructure?
   • If not, which components prevent support (Cloudflare, WAF, load balancers, Azure App Service, proxies, etc.)?
   • Are there any… more
   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  1 comment  ·  DXP, Hosting & Infrastructure  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. 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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Editing (Content)  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Computed fields in Contracts

   Role: Developer working with Optimizely CMS 13 and Optimizely Graph.

   Problem:
   I am implementing search across multiple content types (pages, media etc.) using Optimizely Graph.
   A common requirement is to expose consistent search fields across different content types, for example SearchTitle and SearchDescription, while allowing each content type to derive those values from its own properties and fallback logic.

   The current limitation is that computed fields cannot be exposed through Contracts. While computed fields can be defined on concrete content types and avoid storing redundant search data, they cannot be used to create a unified schema across multiple content types.

   For search scenarios, fields such as SearchTitle and SearchDescription are really search projections rather than editor-managed content. To expose these fields through a Contract today, they must be persisted in the content model, even though they are derived projections rather than actual content.

   Desired outcome:
   Ideally, it should be possible to create a unified search schema backed by computed fields, without having to persist derived values in the content model.
   This would allow developers to expose consistent search fields across pages, media and other content types while keeping the content model free from search-specific properties and publish-time population logic.

   Role: Developer working with Optimizely CMS 13 and Optimizely Graph.

   Problem:
   I am implementing search across multiple content types (pages, media etc.) using Optimizely Graph.
   A common requirement is to expose consistent search fields across different content types, for example SearchTitle and SearchDescription, while allowing each content type to derive those values from its own properties and fallback logic.

   The current limitation is that computed fields cannot be exposed through Contracts. While computed fields can be defined on concrete content types and avoid storing redundant search data, they cannot be used to create a unified schema across multiple content types.

   … more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Graph  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. DXP support for apex domain

   Currently DXP only supports complete hostnames containing both the subdomain and apex domain e.g. www.mywebsite.com.

   We would like to request support for configuring the apex (root) domain (e.g. mywebsite.com) as the primary domain within DXP.

   Traffic can then be redirected from www.mywebsite.com to mywebsite.com.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. 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.

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Add CSP nonce to EPiServer.GoogleAnalytics

    Ability of add CSP nonce value to EPiServer.GoogleAnalytics scripts

    https://nuget.optimizely.com/packages/EPiServer.GoogleAnalytics/

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Security & Compliance  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. 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 to expose:

    1. Stop/start an environment without triggering a code deployment
    2. Copy database and blobs from one environment to another
    3. A webhook or callback when the copy operation completes (so we know when to start the anonymisation or "post-copy scripts")
    4. The ability to register and execute approved SQL scripts as a post-copy step (e.g. PII anonymisation, index rebuilds, configuration updates for non-production)
    5. A completion report confirming which scripts ran successfully, for GDPR compliance audit evidence

    Option 4 could take the form of a "post-copy scripts" folder in the project repository that the platform executes automatically after a copy completes, or a managed script execution endpoint that accepts pre-registered/approved scripts.

    This would allow teams to build compliant, scheduled, hands-off environment refresh pipelines without needing direct database access, which most hosted customers do not have.

    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… more

    8 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. 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 13. Does Optimizely have any plan or timeline to improve the synchronization logic for smoother partial updates instead of full preview reloads?

    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… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Editing (Content)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. ease see the below request about deploying ‘Google Tag Gateway’ in Cloudflare which is not currently supported in DXP

    We want to be able to deploy ‘Google Tag Gateway’ in Cloudflare which is not currently supported in DXP. This gets the Google tags to appear as first-party. The tag setup in GTM is otherwise the same and it should still obey the OneTrust cookie consent.

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Integration / APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. 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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. 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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. 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 a single story that covers the concept and requirements. If the team needs to break it into smaller stories per dashboard section for sprint planning, that is a valid approach, but the sections should be built as one coherent interface, not as separate standalone tools.

    The problem we are solving
    Today, the CMS shows every editor the same generic dashboard. It is not personalized, it does not show issues specific to that editor's content, and it gives no signal about whether the content they own is healthy or broken. The result is that content problems, broken links, outdated pages, unused media, unpublished drafts, go unnoticed for months or even years, until an admin, a customer complaint, or a site audit surfaces them. By that point the damage is already done.
    With over 100 editors across our sites, we cannot rely on a central team or a CMS administrator to track and chase every editor about their content. That model does not scale. Governance needs to become a personal responsibility and for that to happen, editors need to be able to see their own issues at a glance the moment they log in.

    Who this is for
    This dashboard is for every person who creates, edits, or publishes content in the CMS. That includes marketing editors, regional content managers, product page owners, and campaign managers. It is not a tool for administrators - it is a tool that makes every individual editor their own first line of quality control.

    What the editor needs to see
    When an editor logs in, their dashboard should surface the content they personally created or own. (as per editor access rights applicable)

    Broken and 404 pages
    1. Pages I created that are currently returning a 404 error or are broken
    2. Pages that have an incorrect redirect set up
    3. Any pages I own that have no live URL and no redirect in place
    4. Direct links to each page so I can go in and fix it immediately

    Outdated content
    1. Pages I own that have not been reviewed or updated in a defined period of time
    2. A clear signal of how long it has been since the last update
    3. The ability to mark a page as reviewed without making edits, if the content is still current

    Unused images and media
    1. Images and files I uploaded that are not currently used on any page
    2. The file name, upload date, and file size so I can make an informed decision
    3. A way to archive or delete unused files directly from the dashboard

    Unpublished drafts
    1. Pages I have started but never published
    2. The last date I saved the draft, so I can identify ones that have been forgotten
    3. A direct link to open the draft and either publish it or discard it

    Expiring and review-due content
    1. Pages where a review date or expiry date is approaching in the next 30 days
    2. Pages where no review date has been set at all, flagged as a governance gap
    3. The ability to extend a review date or set one if it is missing

    Rule-Based Automation Layer (if possible)
    Defined rules such as:
    1. Draft older than 90 days → archive or notify owner
    2. Redirect chains > 2 hops → auto-flag for cleanup
    3. 404 URLs with traffic → auto-suggest redirect
    4. Orphan pages (no inbound links) → flag or archive

    What the editor does not need to see
    The dashboard should not show content owned by other editors (exception for admins, site managers & super users). It should not show global site statistics. It should not require the editor to filter, search, or configure anything to get to their personal view. When they log in, their issues are the first thing they see.

    Why this is a single solution, not multiple tools
    We considered building separate reports for each of these issues. We decided against it. Separate reports mean editors have to remember to check multiple places. Most will not. A single dashboard that loads at login means the information finds the editor, the editor does not have to go looking for it. This also means one build, one place to maintain, and one consistent experience for all 100+ editors regardless of which site or market they work in.

    Attached are vizualisation ideas- not anything we have as of today.

    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… more

    •  

    •  

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Reports  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. 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 content

    When 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 Content button →Select content → Shortcut window opens displaying available blocks

    Reason for change

    The current “Select Content” shortcut window in Optimizely CMS does not provide a search capability, which creates significant usability and efficiency challenges for content editors.

    Inefficient Content Discovery:
    Editors must manually scroll through a long list of blocks, which is time-consuming and error-prone, especially as the content repository grows.

    Poor User Experience:
    Lack of search increases friction in the content creation workflow, leading to frustration and reduced productivity.

    Reduced Content Reusability:
    Difficulty in locating existing blocks discourages reuse, resulting in duplicate content creation and inconsistency across pages.

    Scalability Limitation:
    As more blocks are added over time, the current approach does not scale and will further degrade usability.

    Business value
    Reduces time spent searching for reusable blocks
    Improves content editor efficiency and workflow
    Encourages reuse of existing content (supports consistency and governance)
    Enhances overall CMS usability

    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 content

    When 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… more

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  1 comment  ·  Editing (Content)  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. 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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Configure Salesforce MA Connector to Omit Certain Object Types

    The Salesforce Marketing Connector tries to fetch fields for Account, Campaign, Contact, Lead and Case.
    When one or more of these are not enabled in SF, this leads to a flood of logs/errors from the 'Fetch Data From Marketing Connectors' job.
    Can you please expose a configuration that allows us to specify which object types should be fetched?

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Integration / APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Improve the visibility of image thumbnails in the Media Panel.

    Our content editors rely on thumbnails in the Media Panel to identify images. However, the current view makes this difficult, as the thumbnails are too small. While it is possible to open each image to view it in full size, this process is inconvenient and time-consuming. Providing larger thumbnails would make image identification much easier and more efficient.

    Suggestion: Provide an option to enlarge thumbnails for better visibility.

    •  

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Media / Asset Management  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating