Skip to content

CMS PaaS (Content Management System)

CMS PaaS (Content Management System)

Categories

JUMP TO ANOTHER FORUM

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

175 results found

  1. The scheduled jobs are executed as tasks by the scheduled job executor (IScheduledJobExecutor. However the Execute method that is required to create and run a custom job does not support return type Task or Task<T> and therefore the async/await syntax cannot be used. When performing expensive procedures such as reading files or executing web requests the thread is kept busy as a result. Also as far as I'm aware if I need to call an async function/method in the job then a workaround has to be used. An example of how others do this can be seen in this forum…

    30 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. As a an editor I would like to translate the contents regarding "Send email after form submission" on the "Settings" tab in order to send e-mails with the correct language to end users, especially with regards to subject and message. This is not currently possible since this list-property is not culture specific.

    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)
  3. Episervers standard behaviour is to convert DateTime between database, application and editors depending on what time zone the application and editors are in. If would be nice if there would be built in properties (or editor hints to enable timezone agnostic date+time or date only selections. There's a blog post how to enable this written by Casper Aasgard (https://fellow.aagaardrasmussen.dk/2016/04/23/get-predictive-time-zones-in-datetime-properties/, but this requires you to add custom editors to the site. However, there's no premade extension for date-selection only.
    This is probably quite easy to add as a standard functionality to the product, which would save a lot of…

    16 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. As an administrator I'd like to be able to publish content bypassing the approval sequence. Can there be a feature added to say which roles a particular approval sequence must follow?

    15 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)
  5. We're using this add-on on Episerver World and it's very good: https://www.david-tec.com/2018/03/visual-compare-option-available-for-episerver-11/
    I think it should be included in the core product so that it is available to everyone.

    13 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 comparing a submitted version of a page to the published version of a page, it would be helpful to have an indication of what content has been added, edited, or deleted. Currently we need to eyeball it to see what the submitter has changed and I'm sure edits are being missed. If we only had to check the places that were changed, it would streamline the process and lower the amount of time spent on each page.

    5 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)
  7. As an editor I would like to be able to remove/move to trash a block or a media content item from the property view in the CMS.
    As it is now you need to have the Block or Media widget open, and if a piece of content is orphaned you don't see it in any list.
    I would like there to be a delete and move option the "Tools" dialog (See attached screenshot.
    A alternative solution would be to have a automated "Orphaned" folder in the block/media view so you can actually select the delete option from there.

    22 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)
  8. We have multiple times seen and gotten feedback from customers that they've accidentally created content in the wrong language when for example English is supposed to be the master language.
    This is usually due to them mainly working in one language and don't switch language branch just to create a page in English.
    We have a few CMS instances where we use fallback language and a navigation with mixed language context. Once a piece of content has been created with a master language other than the intended master language (English it becomes confusing and a frustrating task for editors to…

    26 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)
  9. Content Security Policy (CSP (https://developer.mozilla.org/en-US/docs/Glossary/CSP is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS (https://developer.mozilla.org/en-US/docs/Glossary/XSS and data injection attacks. These attacks are used for everything from data theft to site defacement to distribution of malware.
    Current version of EpiServer Forms is not compatible with Content Security Policy (without 'unsafe-*'.
    This requires us to change EpiServer Form Element to follow directives from our IT-Security apartment.
    Please remove/replace all inline CSS and Javascript required to run EpiServer Forms.
    Documentation:
    https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP
    https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/default-src

    34 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)
  10. As GDPR administrator i would like to know who was viewing, editing data that has been sent via EpiServer Forms. This is why all actions such:
    - display form submissions
    - download form submissions report
    - deleted submitted data
    in Form Submissions panel should be tracked, like for all other types of content.

    6 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)
  11. 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)
  12. 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

    11 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)
  13. As a customer I want to be able to pay a price to use the product that is reasonable and competitive compared to similar products so that I can choose Episerver CMS as platform instead of alternatives like Umbraco or Wordpress.
    Money I spend on license is money that I cannot spend on development of content and features which might make me choose another CMS platform.
    Lowering the license price will result in you selling more licenses and maintaning your position as a leading CMS product company.

    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)
  14. 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

    23 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)
  15. 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 5 6 7 9 Next →
  • Don't see your idea?