80 results found
-
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.
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.
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.
1 vote -
Add Export Button to CMS Built-in Reports
CMS has several built-in reports under the Reports tab (Simple Addresses, Expired Pages, Link Status, etc.) that display useful content data, but none of them offer an export option. Users can view the data on screen, but have no way to download it, only copy paste it.
Adding a CSV export button to these reports would be helpful. The data is already being generated and rendered. The Simple Addresses report is a common pain point, as customers regularly need to audit simple addresses across their site and currently have to resort to Graph queries or custom API calls to extract…
1 vote -
'view on website' should open in a new tab
'View on website' should open in a new brower tab.
1 vote -
Opti SaaS allowing periods in the url
When using Opti SaaS to create a new page that includes a period, the resulting URL segment also contains the period. For example, if you create a page titled "Online on Oct. 4," the URL segment generated will be "online-on-oct.-4," which may render the page inaccessible. It is recommended that the SaaS product automatically remove periods from the URL segment when creating pages.
3 votesThe current url segment generation is based on the RFC 3986 where punctuation is a valid character to include in a URI, see section 2.3 in ietf.org/rfc/rfc3986.txt.
Could you elaborate on the problems you're seeing with these characters in URL's, as reality doesn't always have to align with theory when it comes to these things!
-
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?
1 vote -
Monitoring & Alerting
Monitoring & Alerting
Optimizely to enable monitoring and alerting capabilities:
I. Monitoring
Development of a dashboard for API monitoring, providing visibility into:
⦁ API availability
⦁ API failures
⦁ Traffic trends
⦁ Infra utilizationII. Alerts (Email & Mobile)
Enable proactive alerts to RAKBANK stakeholders for:
⦁ Any API failure
⦁ No traffic detected
⦁ High CPU utilization
⦁ Hardware‑related issuesIII. Alerts should be delivered via:
⦁ Email
⦁ Mobile notifications1 vote -
Localised Alt Text Support with CMS/DAM Integration
There is no option to add Alt Text in multiple languages to assets when using the DAM Asset Picker within the CMS.
With the European Accessibility Act (EAA) taking effect in June it is imperative that we are able to maintain the level of accessibility (via localised alt text) that we had prior to using the DAM integration.
10 votesGood news - this idea is now being explored by our product and design teams. We’re researching potential solutions and scoping out what an implementation might look like.
-
Optimizely DAM picker in TinyMCE
Today, it’s not possible to insert an image or video from Optimizely DAM directly into the TinyMCE rich text editor (unless using a third-party component).
For customers migrating from the built-in CMS media library to Optimizely DAM, native support for this would be expected.
This applies to both SaaS CMS and CMS 13.
2 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.
2 votes -
Saas CMS LongString TextArea
Adding an optional toggle to allow Longstring properties to display as Text areas for CMS editors would be useful.
14 votesThank you for your suggestion! We have this on the roadmap, however not limited to LongString properties. As the regular string supports up to 255 chars it applies to this type as well.
-
property-level permissions
Ability to set permissions either at the property level or the tab/property group level.
Example scenario: you have SEO fields on a page/experience type that only people in an "SEO Manager" role should be able to modify, while other roles can modify the rest of the page properties/content.
1 vote -
Restrict Content and Content types via API keys to a group or site
As a CMS admin, I want to provide access to my development team/delivery apis to a site or sites and content types with the right level of access. (Read, Edit, delete, Create)
This would enable teams to work in an isolated manner that.
One thought is to be able to assign a Content type to a Site or Sites.
1 voteThis effort will be taken up as part of an API framework that will be added to our REST API's. We are expected to pick up the development later in 2026.
-
Setting expiration and scheduled publish date
The idea is to place the expiration date and scheduled publish date together. So a content integrator can see at glance what dates have been set on the page and on the dashboard. The current counting down the expiration date can be kept, perhaps next to the end date itself.
2 votesThanks for reaching out! I will look into this with design!
-
Desktop/Tablet/mobile feature for preview is not available for standard page in visual builder
For content managers and editors, it is essential to have the ability to preview pages across multiple device types. Currently, this functionality is limited to Experience Types only.
This is a significant gap, as standard pages are also being created and previewed within the Visual Builder. Enabling multi-device preview for these pages would greatly enhance the content editing and validation experience for editors and managers.
1 vote -
Boosting to be be applied directly to a nested field like HeroBlock.Heading in the where clause.
I'm a developer, currently using optimzely CMS SaaS. My client would like to take advantage of boosting for specifc fields in a where clause of our GraphiQL search queries. I have learned however that in Optimizely Graph, boosting can be applied only directly to fields that belong to the top level content type, such as Title, MetaDescription, or _fulltext. These properties are directly available in the GraphQL schema for the content type, which is why boosting works as expected when applied to them.
Properties that belong to blocks placed inside a Content Area, such as the Heading property in a…
1 voteWe’re currently gathering additional feedback on this idea. 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!
-
Date/time element for forms
The current supported form types for SaaS CMS do not support a date/time element. This is a common element for dates, DOB etc
Reference
https://docs.developers.optimizely.com/content-management-system/v1.0.0-CMS-SaaS/docs/form-elements2 votesWe’re currently gathering additional feedback on this idea. 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!
-
User experience improvement for Export Data
There is an Export property setting option that appears at the bottom of a screen ONLY when one or more Content Type options are selected. It is otherwise unexposed, and perhaps in the wrong place. I have a suggestion.
TL:DR The problem arises when you select the Content Types section on the Export Data window, which presents a long list of content types. (See attached screenshots.)The user might select a few content types from the top or Select All and click Export and never see that the Export property setting option "magically" appeared off-screen below three other sections (Export tabs,…
2 votes -
Support Geo Seach on Content Types
I work on a tourism website where many of our content types are tied to a Geographic location. We would like the ability to 'Geo Search' the graph but I understand this is not possible using content types (i.e. PageData, BlockData etc). I am to understand this is only possible using custom types.
1 - Can the Geo Search capability be extended to support content types (pages and blocks etc)?
2 - In the meantime, to avoid confusion, can the documentation (https://docs.developers.optimizely.com/platform-optimizely/docs/geo-search) be updated to reflect that this is only possible on custom types?4 votesThanks for sharing this idea. Our product and design teams are looking into it now. We’re exploring possible solutions and figuring out what implementation could involve. We are also actively currently updating our documentation. We’ll keep you posted here as things progress.
- Don't see your idea?