8 results found
-
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.
2 votes -
On-Page Editing not available when using the JS SDK
On-Page Editing (https://docs.developers.optimizely.com/content-management-system/v1.0.0-CMS-SaaS/docs/live-preview-with-react?_gl=1*ye51gc*_gcl_au*MjUyOTYwNjQ4LjE3NzMxNTUxMzcuMTg0NzgxNDg3NS4xNzc2NzgxMjQ4LjE3NzY3ODE0MDU.*_ga*MTMzMjkyMTY1My4xNzczMTU1MTM3*_ga_C7SLJ6HMJ5*czE3NzY3ODEzMDAkbzE1JGcwJHQxNzc2NzgxNDM2JGo2MCRsMCRoODIzOTg0Njc1#use-preview-utilities-for-on-page-editing) is not currently available in the JS SDK (https://github.com/episerver/content-js-sdk/issues/270#issuecomment-4236777609).
2 votes -
Undo Button for Visual Builder
There should be an undo button that restores the visual builder page to its state before a new section was added or modified.
2 votes -
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 -
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 -
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
- Don't see your idea?