Skip to content

CMS SaaS (Content Management System)



CMS SaaS (Content Management System)

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

6 results found

  1. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Implementation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. for more context I'm syncing my data through a webhook that triggers when published, so i want the webhook to be triggered when that page is deleted or expires.

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Implementation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. In CMS 13 with CMP DAM integration, the DAM Library Picker currently prompts users to manually select a CMP instance when they have access to multiple instances. For users such as partners who frequently work across multiple instances, this creates unnecessary friction and interrupts the workflow.

    The expected behavior is that CMS should automatically open or restrict the picker to a specific CMP instance based on its configuration, eliminating the need for manual selection. The DAM Library Picker already supports targeting specific instances (e.g., via instanceIds), but this capability is not currently utilized or exposed in the CMS integration.https://docs.developers.optimizely.com/content-marketing-platform/docs/library-picker#pass-options-in-url

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Implementation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Customers have the ability to manage CMS product details in Admin Center, including the CMS navigation URL - https://support.optimizely.com/hc/en-us/articles/28866325868301-Manage-product-details

    However, the instance name in the URL is not customizable from this customer facing feature and would require a some engineering effort. Customers have asked to update their instance names similar to their own naming standards.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Implementation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. We need a way of deploying the current content and blobs from our production environment to a lower environment of our choosing in our CMS SaaS instance. We should have the option to completely replace all of the data that is currently in the lower environment as well.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. When a scheduled job is executed on a schedule it is executed on the special Scheduler server instance. When a scheduled job is executed by running it Manually it appears it executes on one of the front end servers. This feedback request is to suggest adding the manually run jobs to the queue or some other mechanism so they are executed on the scheduler instance. Running the scheduled jobs on the frontend web instances exposes the end users to poor performance when CPU and memory is peaked and can cause delays in executing the scheduled job when the server becomes…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?