7 results found
-
UI Change to Distinguish Prod from Preprod and Int
I've been burned a few times by publishing content on the wrong environment, e.g. publishing a change in a test page on Integration only to learn I was actually on Production. Woops!
And it's not just me. I know of times our clients have done this, and other members of our team.
Can I suggest some sort of UI indicator (other than just the URL) to indicate which environment you're on?
- Maybe you could output the name of the environment in the header?
- Maybe you could you update the 'Publish Changes' button to read 'Publish Changes to {ENVIRONMENT}'?
5 votes -
Media Publishing Confusion
Media Publishing Confusion: Contributors often forget to publish or submit new/updated media (e.g., PDFs, images) for review, as the system does not prompt them, resulting in drafts being left unapproved.
3 votes -
Versioning Limitations: Updates to blocks (even within a page) do not trigger version updates or review requirements for the parent pgge, ma
Page‑level updates are not reflected in version history:
When a block on a page is updated, the page‑level version history does not show the recent change. Instead, version history is tracked only at the block level, not for the page as a whole. As a result, it can appear that a page has not been updated even when changes have been made.For example the Child Health Policy Accelerator | SickKids page was updated couple of days ago, but the last update details are showing of October 2025.
3 votes -
Reviewers lack visibility into where blocks and media objects are used across the site, leading to time-consuming searc
Reviewers lack visibility into where blocks and media objects are used across the site, unless someone published the landing page/parent block where the block is supposed to be placed. This lead to time-consuming searches and uncertainty during approval.
3 votes -
Difficulty locating the "Automatic published media on upload" setting in CMS 12
Location of Settings in CMS 12: Difficulty locating the "Automatic published media on upload" setting in CMS 12, which affects workflow and publishing behavior.
2 votes -
Irritating double load when clicking menu in OPE mode
Our editors often use the sites menu in the OPE mode to switch pages and the menu is built so it uses the editmode link in OPE mode and the normal link in view mode to accomodate this.
When clicking a menu item in episerver 11, the page is loaded more or less at once, but in episerver 12 the page is first loaded in view mode and then reloaded in edit mode. This happens with all the links in the menu.
The editors find this very irritating. We haven't been able to figure out why that happens.
I tried…
1 vote -
Remove the Paste formating options while being able to choose if it should keep or remove default formating by default
When not using 'power paste' options from TinyMCE, and you copy formatted information from a Microsoft Word document, you get the "Paste formatting options" popup that asks if you want to Remove or Keep the format (view screenshot). Currently, it is possible to remove this popup by using the confirmation ".RemovePlugin("epi-paste");", but the default and only option when the popup is gone is to keep formatting.
This request is to give an option to change the default value when removing it, between "Keep formatting" and "Remove formatting", and not forcing into always keeping formatting.
Thank you,
1 vote
- Don't see your idea?