123 results found
-
Support Content Variations in Export/Import
We would like support for Content Variations to be included when using the Export/Import feature
2 votes -
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"…
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.
1 vote -
add a full URL read-only field in experience settings
In the Settings tab of the Experience properties panel, we currently only see the "Name in URL" for the individual page. It would be very helpful to also have a read-only field showing the full page URL, including all parent pages in the hierarchy.
This would make it much easier to quickly verify a page's complete URL path without having to navigate up through each parent page individually.
1 vote -
PA on a Page with a Content Area / nested Content Areas
For Preview functionality scrolling logic and OPE in the visual preview only works on property fields in Pages and the entire Content Area, but not on its in-line/shared items.
Using Pages with Content Areas containing nested blocks remains a core part of our implementation and workflow. Not supporting scrolling logic for these in-line items makes On-Page Editing practically unusable for our editors.
Please update the visual preview so that scrolling logic and focus behavior work properly on in-line and shared items inside Content Areas.
This is a critical issue for teams who rely on Content Area architectures and need a…
1 vote -
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
1 vote -
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 -
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.
1 vote -
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 -
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.
1 vote -
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.
3 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.
3 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.
1 vote -
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.
1 vote -
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 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 -
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
- Don't see your idea?