129 results found
-
Database Backup and Point-in-Time Restore for CMS SaaS
Summary
Customers want the ability to create database backups of their CMS SaaS environments on demand, and to restore an environment to a specific point in time from those backups.
Problem
Today, customers have limited control over recovering their SaaS environments after unexpected data changes. Content editors and developers can make mistakes that are difficult to undo: bulk deletions, faulty imports, a bad deployment that corrupts content, or a misconfigured integration overwriting data. When this happens, recovery generally depends on a support request, which adds delay, uncertainty, and risk to the customer's operations. Teams that test migrations, upgrades, or major…
3 votes -
Choose whether to copy child pages, and how many levels, when copying a page
When a page that has child pages is copied, the CMS always copies the entire subtree. There's no way to copy only the parent. Request: when copying a page, let the author choose to copy the parent only, or the parent plus its children. If children are included, let the author choose how many levels deep to copy. We need both: duplicating a single page as a starting point without its subtree, and cloning a section or template tree to a chosen depth to stand up new sites. Related: "Option to do a shallow copy when duplicating (copy/paste) a page"…
3 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 -
Group Content Types
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.
5 votesThank you for your feedback! This is on the roadmap!
-
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 -
Include OCP synced fields in CMS search
Problem
CMS search currently only finds synced assets by title. Users cannot search metadata like description, tags, or other synced external fields.Request
Allow internal CMS search to index and search OCP synced metadata fields.Examples
Description
Tags / Keywords
Categories
Custom external fields
Product IDsExpected Outcome
Users can find synced assets using metadata, not just title.Value
Better asset discovery, faster editor workflow, improved usability.9 votesGood news - this idea is now being explored by our product and design teams. We’re researching potential solutions and scoping out what this might look like. We’ll share updates here as this capability progresses.
-
Visual Builder forms are incomplete when fetched with @optimizely/cms-sdk
Visual Builder forms are incomplete when fetched with @optimizely/cms-sdk
In Optimizely SaaS CMS, Visual Builder forms work in the editor, but the content JS SDK (@optimizely/cms-sdk) does not return everything needed to render them on the site.
When a Form Container is placed on an Experience, the SDK query does not go deep enough to include the fields inside the form (step → row → column → elements). Form Container properties set in CMS — Title, Description, Submit URL — are also missing from the response.
As a result, forms cannot be implemented with the SDK as-is. We had to…
3 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.
3 votes -
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.
3 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 -
Support Content Variations in Export/Import
We would like support for Content Variations to be included when using the Export/Import feature
2 votes -
Add an external media embed option (YouTube, Vimeo, Wistia) to the rich text editor
The rich text editor has no option to embed external media such as YouTube, Vimeo, or Wistia videos. Authors can't place a video inline within body content without developer help or a purpose-built component. Request: add an embed action to the RTE toolbar that accepts a video URL (or oEmbed-compatible link) and renders a responsive player in both the visual editor and on the published page. This is common in higher-ed program content, such as program overviews, faculty introductions, and student testimonials. At a multi-site scale, requiring a custom component for every inline video adds friction for non-technical authors.
2 votes -
Enable selective block/page export across different paths
We are currently struggling using Export Content Items since we can not export specific blocks and pages from different paths into a single package.
As a workaround, we have to create multiple packages for each path and manually clean up the child content after importing.
We would like to request an enhancement to the export content items feature that allows us to cherry-pick specific pages and blocks across multiple paths
2 votes -
Give admins tenant-level control over enabling new platform capabilities
New platform capabilities (for example a new AI feature or a Visual Builder enhancement) are exposed to all authors automatically, so authors may see UI changes with no lead time or training. Request: administrator controls to stage the rollout of new capabilities - enable first in a Dev environment, train authors, pilot with one or a few sites, then roll out to Production when ready.
2 votes -
Automatic per-edit revision history with before-and-after diff
There is no automatic per-edit revision history. The Change Log records that a save or publish occurred, by which user and when, but identifies content only by machine references (ContentGuid, ContentLink, ContentTypeId) and does not show what changed. The Versions gadget requires manually creating version records and is capped at 20, which does not work for frequently edited pages. Request: automatic per-edit versioning with a visual before-and-after diff and no practical version cap. Our current platform provides this natively, including who made each edit, plus a site-level activity view.
2 votes -
Content dependency and impact analysis before publish, change, or delete
Before publishing, changing, or deleting a component, asset, page, or taxonomy term, authors have no way to see what references it. Request: a references or where-used view that lists every page, component, template, and experience that references the selected item, shown before the change is made. This is especially important in large multi-site environments where a single change can have wide downstream impact.
2 votes -
Improve multi-site management and navigation for cross-site editors
Managing multiple sites is not intuitive for users who work across sites. The long list of sites and pages down the left side is difficult to scan and navigate, which slows editors who move between many sites. Request: a more usable multi-site navigation experience (for example search/filter, grouping, or a collapsible site and page tree) so cross-site editors can find content and switch context quickly. This is especially important for large multi-site portfolios.
3 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.
2 votes -
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.
2 votes -
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.
2 votes
- Don't see your idea?