Skip to content

CMS PaaS (Content Management System)

CMS PaaS (Content Management System)

Categories

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

244 results found

  1. Currently, if we author a block within the catalog but then go to make edits to that block we often see "this block isn't used anywhere" but that is false. It would be helpful to know all the placements within the catalog.

    9 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)
  2. Currently, the Link Status report shows broken links that are present on expired pages. I would prefer it if broken links on expired content could be excluded from the report.
    This could be configurable.
    Jira ticket (https://jira.sso.episerver.net/browse/CMS-24033

    12 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)
  3. As an admin I want to be able to export a report from the reports system So that I can distribute required updates to the broader author group. The outcome is the ability to complete an export of any report within the reports system

    27 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)
  4. Some functionality cascades down the page tree, like approvals or permissions. Sometimes you want to group pages together so you can apply values and functionality to branches of pages, but these necessarily affects the URL, since any page generates a new URL segment.
    "Container" pages can't be accessed directly, but they still generate a URL segment, so they can't be transparently used for grouping content.
    It would be helpful to allow a type of container page that doesn't generate a URL segment. When ancestors are collected to form a URL for a descendant page, this type of page could simply…

    3 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)
1 2 … 9 10 11 13 Next →
  • Don't see your idea?