Skip to content

CMS SaaS (Content Management System)



CMS SaaS (Content Management System)

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

99 results found

  1. 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…
    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. In Optimizely CMS (SaaS), there is currently no built-in way to publish a content item along with all its descendant items (child pages/blocks) in a single action. Editors must publish each item individually, one at a time, through the UI.

    Impact:
    For content trees with many nested pages or blocks (e.g., large campaign launches, section rewrites, or bulk imports), publishing item-by-item is slow and time-consuming, especially as the number of child items grows.

    Suggested solution:
    Add a "Publish with children" (or similar) action in the content tree/edit view that recursively publishes a selected item and all its descendants. Alternatively, expose…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. For shared blocks and other content types, we can already query Optimizely Graph to find every instance of a given type. For example:

    query FindByType {
    _Content(where: { _metadata: { types: { in: ["<ContentTypeName>"] } } }) {
    total
    items {
    _metadata { key displayName types url { default } }
    }
    }
    }

    This works because shared blocks are standalone content items with their own key/ContentLink, so they're indexed and queryable like any other content type.

    Local (inline) blocks don't support this. Since they're stored as embedded property data on the parent content item rather than as standalone content…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. CMS (SaaS) does not currently expose an explicit height/width setting for the rich-text editor. Unlike CMS PaaS (where the editor size can be set in code via the TinyMCE Configuration API), SaaS is configured entirely through the content-type contract, and the only editor setting available for a rich-text property is the toolbar preset.

    As a developer worried with the user experience, I would like to have the ability to set the text area's height, at least.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Forms  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. I manage our website and we just switched over to Optimizely. It is FAR better than our old system! However, editing our website is not intuitive and the button symbols are so rarely intuitive with their functions. Minimally when you hover over a button it should tell you what it's function is, please!

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Content Manager  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. We currently manage our website in English plus 13 additional languages. Currently, the workflow to translate content requires editors to manually open each target language version in the Languages gadget, initiate auto-translate via Opal, and then manually publish each version. This requires a minimum of 13 separate clicks/actions for every single content change.

    We would like a "set-and-forget" automation rule or workflow capability. When a page or block is published in the master language (English):
    1. An automated workflow triggers immediately.
    2. It sends the updated English content to Opal AI's Content Translation engine.
    3. It automatically updates, localizes, and…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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…

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. When we have a CMS instance on the Conservative ring, it does not prevent updates to the associated DAM instance (and Graph schema for that DAM instance), which can cause issues when the CMS graph doesn't get updated at the same time. See support ticket #1910807 for an example.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. for more context I'm syncing my data through a webhook that triggers when published, so i want the webhook to be triggered when that page is deleted or expires.

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Implementation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. While implementation I found out the indexed content post purge not only delete indexed content but the underlying content type schema too. i.e. the elastic storage container. Thus if we again index content if fails to index content. Though it gives success response with journal id, internally the Optimizely graph do not index content and gives exceptions index not found.

    Which led me to opening a ticket with optimizely support explaining them the issue https://support.optimizely.com/hc/en-us/requests/1908585

    The response from opti support team about no index found exception post purge is following:

    Thank you for waiting. I tested with my production CG…

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Graph  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’re currently gathering additional feedback on this feedback and we're exploring a potential fix. 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!

  18. When enabling the "List" option for a "block" property type, adding blocks to an actual instance of my item only shows the name of the block type in the list and it is impossible to differentiate each item without opening them all (see attached screenshot). In the non-SaaS version of the CMS I see there is a way in code to set a nested property as the item header using ListItemHeaderProperty as described here https://docs.developers.optimizely.com/content-management-system/docs/property-value-list

    Please enable the ability to select a nested property as the header in SaaS CMS, either via the API or the UI for defining content…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Content Manager  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. In the PaaS version of the CMS it is possible to group Page and Blocks. This acts as a visual aid for editors allowing them to easily locate the relevant content type when there is a long list.

    This should also be manageable via the management api.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5
  • Don't see your idea?