32 results found
-
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…
8 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 -
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
8 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.
5 votes -
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 -
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 -
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 -
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 -
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:
- Define a content type based on the…
3 votes -
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 -
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 -
CTAs are not removable when prompting external link or email
When a user:
Configures a CTA to link to an email address (mailto:) or external link
Saves and publishes the item/component
Returns later to edit the same item
…the user is unable to remove the optional CTA/link afterward.
This creates a blocking editing issue where previously configured optional email links become effectively permanent unless overwritten with another value.
2 votes -
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 -
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 -
Need the ability to set the TinyMCE Toolbar height
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 -
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 -
editing our website is not intuitive and the button symbols are so rarely intuitive with their functions
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 -
Automated "Set-and-Forget" Multi-Language Translation and Publishing via Opal AI
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
- Don't see your idea?