27 results found

1. Option to do a shallow copy when duplicating (copy/paste) a page

   Currently when copying a page all nested items have copies created as well, including: 1) child pages but also any 2) shared blocks within the page content. I would like options to skip the "deep copy" that happens for child pages and shared blocks whenever a copy/paste is done. The shared blocks is especially a problem. Since copying a page creates separate duplicates of the shared blocks, it requires manual work to go in and delete the duplicated shared blocks and re-insert the reference to the original. This feels pretty antithetical to the point of shared blocks: keeping a single instance across many pages to make changes at scale easier.

   Choosing to skip copying child pages would be a nice extra, but especially being able to leave the references of shared blocks as is instead of duplicating them would be a really big improvement to our workflow.

   Currently when copying a page all nested items have copies created as well, including: 1) child pages but also any 2) shared blocks within the page content. I would like options to skip the "deep copy" that happens for child pages and shared blocks whenever a copy/paste is done. The shared blocks is especially a problem. Since copying a page creates separate duplicates of the shared blocks, it requires manual work to go in and delete the duplicated shared blocks and re-insert the reference to the original. This feels pretty antithetical to the point of shared blocks: keeping a single… 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  ·  1 comment  ·  Editing Content and Visual Builder  ·  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. Inline blocks should honor the "unique value per language" (shared property) setting

   Inline blocks should honor the "unique value per language" (shared property) setting

   Properties on inline blocks are always stored per language version, regardless of how the property is configured on the content type. A property marked as not unique per language — i.e. intended to be shared across all languages — behaves as language-specific when the block is inline, so editors get divergent values in each language with no warning.

   Reproduction:
   1. Create a content type with two properties: one marked as unique value per language, and one marked as not unique per language (shared).
   2. Create a page with two language versions.
   3. Add a block of that content type inline inside a content area on the page.
   4. In the first language version, set values for both properties.
   5. Switch to the second language version and change the shared property's value.
   6. Return to the first language version and inspect that property.

   The shared property holds a different value in each language version, while the same content type used as a shared block from the block tree respects the setting correctly — the divergence only occurs when the block is inline

   Expected:
   Inline block properties should respect the language-uniqueness configured on the content type. A shared property should resolve to one value across every language version of the owning page.

   Why it matters:
   Shared properties are how editors keep non-translatable data consistent — identifiers, product codes, tracking keys, brand labels, configuration toggles. On multilingual sites, inline blocks silently break that guarantee: values drift as each language is edited, and there's nothing in the UI signaling that the setting doesn't apply here. Teams either avoid inline blocks entirely on multilingual sites — losing their main advantage of not cluttering the block tree — or manually reconcile values across every language.

   Inline blocks should honor the "unique value per language" (shared property) setting

   Properties on inline blocks are always stored per language version, regardless of how the property is configured on the content type. A property marked as not unique per language — i.e. intended to be shared across all languages — behaves as language-specific when the block is inline, so editors get divergent values in each language with no warning.

   Reproduction:
   1. Create a content type with two properties: one marked as unique value per language, and one marked as not unique per language (shared).
   2. Create a page with… more

   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  ·  Editing Content and Visual Builder  ·  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. Add Find/Replace Feature

   Create a feature to allow find/replace functionality so I can easily find words and phrases and, if necessary, replace them with a new word or phrase. This is standard in many CMS.

   5 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 and Visual Builder  ·  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. Allowable Section Types in an Experience Type

   Can we have allowable section types in an Experience Type?

   In a large implementation, we can have several components/blocks enabled as 'Sections' so that they can be directly added to the Experience page.

   The GraphQL query for an Experience becomes very big as we specify more blocks as 'sections' Can we add a feature where a developer can define 'allowable' sections on an experience, so that the graphQL query that is formed contains only a limited allowable types?

   7 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 and Visual Builder  ·  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. Support relocating components across fields without recreating them

   We need the ability to move an existing component from one content field to another (e.g. from one column to a different column that allows the same component types), not just duplicate it in place. Currently there's no way to relocate a component across fields — the only option is to delete it and fully recreate it from scratch in the destination, re-entering text, re-uploading/re-linking images, and reconfiguring settings each time. This makes routine page reorganization slow and error-prone, especially for content-heavy components like Rich Text blocks or Link Columns.

   •  

   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  ·  Editing Content and Visual Builder  ·  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. CMS Authoring UI Improvement: Multiselect Choice Field

   We have Multiselect Choice Field with 50+ items. These are rendered in authoring UI as a long list of checkboxes, which takes up a lot of space.

   We would like to see improvements to authoring UI where we show Multiselect Choice fields as a Dropdown CheckedList box. Would be great if we can have search feature in the list, and also Clear All functionality to reset previous selections.

   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  ·  Editing Content and Visual Builder  ·  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. Optimizely DAM picker in TinyMCE

   Today, it’s not possible to insert an image or video from Optimizely DAM directly into the TinyMCE rich text editor (unless using a third-party component).

   For customers migrating from the built-in CMS media library to Optimizely DAM, native support for this would be expected.

   This applies to both SaaS CMS and CMS 13.

   10 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

   1 comment  ·  Editing Content and Visual Builder  ·  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
   Research & Design  ·  AdminTom Bramley (Senior Product Manager, Optimizely) responded

   Good news - this idea is now being explored by our product and design team. We’re scoping out the functionality and we’ll share updates here as our thinking evolves.

8. Allow Component Copying/Cloning/Duplicating

   Currently, copying/cloning is only available at the page level, but admins would benefit from being able to clone/make a copy at the component level, too, within a given page.

   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  ·  Editing Content and Visual Builder  ·  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. 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
   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  ·  Editing Content and Visual Builder  ·  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. convert a page into an experience.

    Client has requirement to convert convert a page into an experience in CMS SAAS.

    11 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

    0 comments  ·  Editing Content and Visual Builder  ·  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
    Gathering Feedback  ·  AdminHåkan Edling (Senior Product Manager, Optimizely) responded

    Thank you for reaching out. Can you give more concrete examples of the data loss you're describing.

11. In-line blocks in a content area with "Unique value per language" setting turned on can't be translated

    Currently, you can't edit inline-blocks within a content area outside of the master language. Meaning if you want to translate anything it's not possible unless you make it a shared block.

    This makes it very difficult for content editors to understand but also maintain all of this as you'll be unnecessarily working with tons of shared blocks just to support the language/translation functionality.

    The content area should be locked which is correct (no reordering) but the in-line blocks inside of it should still be translated.

    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  ·  Editing Content and Visual Builder  ·  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. Image Renditions in CMS

    Image renditions need to be accessible in the CMS via the DAM picker. This way, the author can choose the different renditions of an image they want to add to the page/view.

    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 and Visual Builder  ·  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. Conditional Content Tagging

    Hello!

    We have teams which we are migrating over to Optimizely SaaS who have a need for conditional content tagging. What I mean by that is when a category is selected on a block, it shows specific fields that are unique to that category. A category could have 0 unique fields or multiple unique fields.

    This is important to help prevent our content model or blocks from getting "messy". The only way around this, that we've found, would be to either list out all available fields, which would be confusing to content authors, or have a unique block per category, which requires managing a large number of potential extra blocks (instead of max 1 per team, it could be 5,10 depending on category count).

    If I am wrong regarding current available solutions or you need any more information on our use case, please let me know. Otherwise, we hope this could be implemented in the future.

    Thanks!

    Hello!

    We have teams which we are migrating over to Optimizely SaaS who have a need for conditional content tagging. What I mean by that is when a category is selected on a block, it shows specific fields that are unique to that category. A category could have 0 unique fields or multiple unique fields.

    This is important to help prevent our content model or blocks from getting "messy". The only way around this, that we've found, would be to either list out all available fields, which would be confusing to content authors, or have a unique block per category,… 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

    Future Consideration  ·  0 comments  ·  Editing Content and Visual Builder  ·  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. Include component name in validation error message

    Currently, when we try to publish and some required properties are missing from an experience or a component from the experience outline, we only see a simple validation message that the property is missing. The problem is that we might have that property on many components and we can't tell from the validation message alone which is the component that causes the problem, so we have to manually find it.

    It would be great to also include the component name in the validation message.

    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 and Visual Builder  ·  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. CMS Headless Preview Endpoint Selection

    Editors cannot choose which head (localhost/dev/qa) to preview a page in - only one endpoint is available and tightly coupled.

    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 and Visual Builder  ·  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. Shareable external preview links for unpublished (draft) content

    Problem
    In Optimizely CMS (SaaS) there is currently no way for content editors to generate a long-lived, shareable preview link for unpublished/draft content that external stakeholders can open without a CMS / Opti ID account.
    Current limitations:

    The official preview token expires in only 5–10 minutes.
    The only official recommendation is to give stakeholders limited CMS access so they can open the page in Visual Builder themselves.
    This creates friction for external reviews (clients, legal, marketing stakeholders, executives, agencies, etc.) and forces customers to either:
    Maintain a separate staging environment, or
    Build custom workarounds.

    This was a solved problem on classic CMS (via the External Review / Advanced Reviews functionality) but is missing in SaaS.
    Proposed Solution
    Allow content editors to generate secure, shareable preview links directly from Visual Builder (or a dedicated gadget) with the following capabilities:

    Link shows the exact current draft version of the page
    No CMS / Opti ID login required for the recipient
    Configurable expiration (e.g. 24 hours, 48 hours, 7 days)
    Optional PIN / password protection
    Ability for the editor to revoke the link at any time
    Works on the production environment (no need for a separate staging site)
    Preferably supports visitor groups / personalization if used on the page

    Business Value

    Significantly improves the content review & approval process
    Removes the need for external stakeholders to have CMS accounts
    Reduces reliance on separate staging environments just for preview purposes
    Aligns SaaS with capabilities that many customers already had (or expected) from previous Optimizely versions
    Very common request across agencies and enterprise customers

    Additional context
    Several customers and partners (including us) have already confirmed with Optimizely Solution Architects that this is currently not possible natively. A clean, first-party solution would be highly valued.

    Problem
    In Optimizely CMS (SaaS) there is currently no way for content editors to generate a long-lived, shareable preview link for unpublished/draft content that external stakeholders can open without a CMS / Opti ID account.
    Current limitations:

    The official preview token expires in only 5–10 minutes.
    The only official recommendation is to give stakeholders limited CMS access so they can open the page in Visual Builder themselves.
    This creates friction for external reviews (clients, legal, marketing stakeholders, executives, agencies, etc.) and forces customers to either:
    Maintain a separate staging environment, or
    Build custom workarounds.

    This was a solved problem on… 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

    Future Consideration  ·  0 comments  ·  Editing Content and Visual Builder  ·  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. TinyMCE editor toolbar configuration

    I'm a software developer. I would like to be able to configure the toolbar of the TinyMCE xhtml editor in Optimizely CMS SaaS so it matches the exact wishes of my client. Currently we only have 3 options: minimal, standard and extended. It would be convenient if we could configure the toolbar ourselves. I'm think of an option to insert code snippets, but also simple thinks like support for H2 to H5 but not H1. Basically, I would like to be able to configure everything that TinyMCE allows to be configured out-of-the-box.

    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  ·  Editing Content and Visual Builder  ·  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. Saas CMS LongString TextArea

    Adding an optional toggle to allow Longstring properties to display as Text areas for CMS editors would be useful.

    22 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

    3 comments  ·  Editing Content and Visual Builder  ·  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
    Committed  ·  AdminHåkan Edling (Senior Product Manager, Optimizely) responded

    Thank you for your suggestion! We have this on the roadmap, however not limited to LongString properties. As the regular string supports up to 255 chars it applies to this type as well.

19. Retain outline structure on all translations when making changes in Experience

    When I have multiple languages of my site and I want to retain the outline of my Experience of all languages this is currently not synced. When I move sections around I have to manually do this for every language.

    We would like an option to keep the outline in sync for all languages, and only adjust the translations

    Currently Experiences are not an option for sites that use multiple languages but are managed by a single team that wants the same structure. They are better off using Pages

    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

    Gathering Feedback  ·  0 comments  ·  Editing Content and Visual Builder  ·  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. On-Page Editing not available when using the JS SDK

    On-Page Editing (https://docs.developers.optimizely.com/content-management-system/v1.0.0-CMS-SaaS/docs/live-preview-with-react?_gl=1*ye51gc*_gcl_au*MjUyOTYwNjQ4LjE3NzMxNTUxMzcuMTg0NzgxNDg3NS4xNzc2NzgxMjQ4LjE3NzY3ODE0MDU.*_ga*MTMzMjkyMTY1My4xNzczMTU1MTM3*_ga_C7SLJ6HMJ5*czE3NzY3ODEzMDAkbzE1JGcwJHQxNzc2NzgxNDM2JGo2MCRsMCRoODIzOTg0Njc1#use-preview-utilities-for-on-page-editing) is not currently available in the JS SDK (https://github.com/episerver/content-js-sdk/issues/270#issuecomment-4236777609).

    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 and Visual Builder  ·  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