129 results found
-
Sync external content data purge deletes content as well index
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…
13 votesWe’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!
-
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.
10 votes -
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…
10 votes -
Bulk publish content item with all child items
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…10 votesThank you for raising this feature request. This is something we are actively pursuing and is on our roadmap to deliver later in the year.
-
Drag-and-drop reordering for repeatable content structures
Currently, repeatable or ordered content structures within CMS: such as table rows/cells, and content links, rely on manual move up/ move down controls to reposition content one step at a time.
For example, within our Table Block, authors must repeatedly click move up/down to reorder rows or cells, which can become inefficient for larger content structures.
This request is to add native drag and drop reordering functionality for applicable repeatable content structures within the CMS authoring experience.
Desired Behavior:
Authors can drag and reposition items in a single action
Visual drag handles or intuitive reorder controls
Improved efficiency over repeated…13 votes -
REST API support needed for Default Values to get/set default values for Content Types fields
Currently ContentType REST API does not support get/set for ContentType fields.
For example: I have a content type with a TextField, have set default value for it in the CMS. However, there is no way to get/set it via REST API, which makes it impossible to deploy the contenttype with default values to other environments using the CLI
11 votes -
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.
6 votes -
"Seed ID" for building the content URL should be exposed
We are currently migrating a large amount of content from another platform into the SaaS CMS. We are building an automated tool for this that uses the REST API. After the tool runs we are aiming for a "Run Report" that displays the link to the content in the previous platform and the Optimizely CMS for comparison. In order to build the link in Optimizely URL we need, what I will call for this request, the "seed id".
For example: https://app-<tenant>.cms.optimizely.com/ui/cms#context=epi.cms.contentdata:///<seed_id>
Since this is saved somewhere, it would be helpful if this was exposed when you make a request…9 votes -
Retrieve references/usages of local (inline) blocks
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 -
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…6 votes -
'view on website' should open in a new tab
'View on website' should open in a new brower tab.
8 votes -
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.
6 votes -
Converting single use blocks into shared blocks easily
Currently blocks created for a specific page cannot be covered into shared blocks. (Shared blocks can be covered into single use block). Therefore if we want to convert the single use of block into a shared block, we will have to create a shared block from the scratch. This functionality is available in other headless CMSs and I believe it's useful.
17 votes -
Ordering of content in UI
Scenario: An editor creates many news articles and then needs to find them again in the UI.
Challenges
Any content, when added, is ordered in the order it was created, not alphabetically. This makes content difficult to find in the content tree.You can manually reorder content, but this takes time.
In PaaS, you can define how child content is ordered; this isn't available in SaaS, and I feel it would be beneficial to bring this feature back, as we are getting a lot of negative feedback from the clients' editors.
Or, at least in the short term, order the…
3 votes -
Language management on Multiple sites
Scenario: I have a SaaS instance with multiple sites/applications enabled and multiple languages enabled.
Challenge 1
In CMS 12, the admin was able to configure which languages are enabled for the site; this is no longer available and leads to confusion for editors.Editors should be able to edit content and work only in the languages enabled for that site.
Challenge 2
I want to create a new application/site, and the master language is different to the master language of all the other sites.i.e. I want to create a site where the master language is zh-hant, not the default…
3 votes -
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.
5 votes -
Do not pre-apply Files and Images filters in the DAM picker
When selecting an asset from the DAM inside the CMS, the picker pre-filters to 'Files' and 'Images,' and there is no way to disable these default filters. We would prefer no filters applied by default so authors get an unfiltered view of available assets. Request: make the default picker view unfiltered, or make the default filters configurable.
3 votes -
Prevent silent overwrites of concurrent edits with conflict warning and field-level locking
Concurrent edits to the same page can be silently overwritten (last write wins). Both editors work against a single shared draft, so whoever publishes second overwrites the first with no conflict warning and no merge. The 'currently being edited' notice is dismissable and does not prevent this, there is no field-level locking, and comments are page-level rather than field-level. Request: a conflict warning on save or publish when another user has changed the draft, and/or field-level locking to protect in-progress edits.
4 votes -
Filter content by site or partner when selecting content in multi-site instances
When selecting content (for example using Select Content to reference a program), the picker shows content across ALL sites and partners on the platform with no way to filter to a specific site or partner. This creates governance and usability problems for large multi-site portfolios. Request: allow filtering the content picker by site or partner.
5 votes -
Filter the shared-block picker to blocks valid for the current section
The shared-block picker shows every reusable block on the site rather than only the blocks valid for the section or content area being edited. Invalid options appear (some grayed out, some opening to nothing), which makes the picker hard to navigate. Request: filter the picker to show only the blocks allowed in the current context.
4 votes
- Don't see your idea?