36 results found
-
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.
8 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…
9 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 -
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 -
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 -
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…
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.
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 -
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.
8 votes -
Add a filter to show only Blueprints on the Add Section screen
When adding a new section to a page, there is no way to filter to only Blueprints; they are comingled with all components. Request: add a filter and keyword search on the Add Section screen so authors can quickly find Blueprints.
2 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.
2 votes -
convert a page into an experience.
Client has requirement to convert convert a page into an experience in CMS SAAS.
11 votesThank you for reaching out. Can you give more concrete examples of the data loss you're describing.
-
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,…
5 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 -
Allow inserting an image inline without navigating to a separate area
Adding an image requires navigating to a separate area, which interrupts the authoring flow. Request: enable inline image insertion directly where the author is working in the editor.
1 vote -
Reduce the number of clicks required to insert a link in the editor
Adding a link currently takes four to five clicks versus about two on our previous platform. For a very common authoring task, this adds up across a site. Request: streamline the link-insertion flow to reduce the number of clicks required.
1 vote -
Add spell check to the rich text editor
The rich text editor has no built-in spell check, and it overrides the browser's native spell check so even the browser no longer flags errors. Request: provide built-in spell check in the rich text editor, or at minimum stop suppressing the browser's native spell check so authors can catch typos.
1 vote -
Add word and character count to the rich text editor
The rich text editor has no word or character count. Request: display a live word and character count in the editor so authors can meet content standards and length limits without copying text into another tool.
1 vote -
Make the admin and authoring UI extensible with init modules, plugins, and custom editor descriptors
The admin and authoring UI is not customizable in SaaS. There is no support for initialization modules, plugins, or custom editor descriptors, which limits how far the authoring and governance experience can be tailored to a client's needs. These extension points exist in PaaS. Request: provide supported extension points so customers and partners can customize the authoring and admin experience in SaaS.
1 vote -
Allow deleting a section or component from the Outline view
A section or component cannot be removed from the page-level Outline view. Removing one requires opening the section/component first and then using its options menu, which adds an extra step. Request: add a remove/delete action directly in the Outline view so authors can remove items in a single step.
1 vote
- Don't see your idea?