245 results found
-
Image Version updates from the DAM should automatically be reflected on webpages when you are using Renditions
An updated "Version" of an image from the CMP/DAM is automatically reflected on a published webpage; however, if you are pulling in a "Rendition" of the image from the DAM, the updated Version is not shown. For Renditions, you have to use the Asset Picker and select the image again and then republish the webpage to see the change (new image version.
Our content authors make heavy use of Renditions and would like image version updates from the DAM to be automatically reflected on webpages, just like with original images.11 votes -
Easier cleanup of unused blocks
Maintaining the number of blocks is important to editors. When using Powershell module you can get a list of blocks that are not in use so editors can maintain content on the site.
The problem is that blocks that are located in "For This Page" folders does not contain the page information in the breadcrumb (see attachment. This means that it's hard to find the folder containing this block if you want to delete the block. Extending the breadcrumb to include the owner (page of the folder "For This Page" would help the editors to know the location.11 votes -
Convert blocks
As a developer/administrator, I want to be able to convert blocks like I can convert pages so that I can merge blocks resulting in a cleanup of content and less work for our content editors.
This isn't a new feature request and has been popular on the old forum; see: https://world.optimizely.com/forum/legacy-forums/Feature-requests/Thread-Container/2014/9/Convert-Blocks/. (https://world.optimizely.com/forum/legacy-forums/Feature-requests/Thread-Container/2014/9/Convert-Blocks/
In May 2020, Tomas Hensrud Gulla did a blog post on how he took the existing Convert Pages and made his own Convert Blocks variant with relatively little effort. See https://www.gulla.net/en/blog/convert-episerver-blocks/. (https://www.gulla.net/en/blog/convert-episerver-blocks/11 votes -
As an editor, I'd like navigate to page associated to "For this Page" asset folder
When editing a content object located in "For this X" asset folder I would like to find/navigate to the X content.
This can be solved by adding a link in the "For this X" breadcrumb.11 votes -
App Insights alerts
Self-serve creation of alerts in App Insights based on specific thresholds exceeding a limit will help be proactive in responding to potential performance issues or other problems
11 votes -
Search functionality to help finding needed content type
When there is several page and block types in use it would be easier to have search field so you could find correct content type effectively.
11 votes -
Set a default time zone for date/time editing
Currently in the CMS, time/date pickers are associated to the editors local time. This is problematic, because we have editors all over the US. Entering in time/date information incorrectly will lead to our event registration announcements displaying the wrong time.
For example, our servers are set to Central Standard Time, so we display date/times, we need to assume they were entered in as that time zone as well, or the time will be off.
Ideally we should be able to force the date/time picker to use the same time zone as the server.10 votes -
Make Language Manager smarter - extend translate API with IContent and Property
The Translate Interface in language manager add-on (EPiServer.Labs.LanguageManager, to make translations smarter, It would be benificial to add IContent and propertyName. With that, we can get Custom Property Attributes, or other properties to understand better the context.
Change from
TranslateTextResult Translate(
string inputText,
string fromLang,
string toLang;
to
TranslateTextResult Translate(
string inputText,
CultureInfo fromLang,
CultureInfo toLang,
IContent currentContent, //or similar ContentReference
string propertyName
;
With this, we could make the translations smarter by knowing the context of the block or page. We could also read any custom attribute on the property if any.10 votesWhile we do not plan to pursue it at this time, we’re going to revisit this idea for consideration in the future. Please continue to provide feedback or additional information, and thank you for helping us build a case for pursuing this idea in future.
-
Increase help text visibility
As a Digital Marketing Manager, I've observed that CMS editors often neglect help texts. To enhance visibility and address this issue, I believe implementing an option to display these help texts immediately would significantly improve the situation.
10 votes -
Add customizable reporting framework to CMS 12
As a developer I want to create custom reports (like in CMS pre-v12. Then I want them listed on the Reports tab so users (with proper access rights can be viewed or downloaded.
10 votes -
Implement SRI attributes for injected JavaScript & Styles
The Optimizely PAAS CMS platform has multiple touchpoints where scripts are injected into the frontend UI. Examples include Optimizely Forms, Content Recommendations, Search & Navigation etc.
When these scripts are injected into the UI, they are not added with a Sub-resource Integrity attribute. An SRI check allows us to instruct the browser that it should not load a tampered version of a JS or CSS file and can protect users from man in the middle attacks. You can read more about SRI here: https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
This is a commonly reported issue in penetration tests and clients are becoming increasingly more security…
10 votesThanks for raising this - just to let you know this is now in our backlog. While we can’t share an exact release date yet, this means it’s planned for consideration in the future. Thanks for helping us prioritize this work.
-
CMS13 - EpiServer.Forms.Samples
We upgraded to CMS13 recently, and found that the package EpiServer.Forms.Samples is not upgraded yet. Since we use recaptcha this is blocking all our forms.
Can EpiServer.Forms.Samples be upgraded to support cms13?
9 votes -
Color palette change (Plae Green is not good)
My team who use the PIM product brought the new color palette change to my attention. The color is abrasive and makes spending time in the application unpleasant. What were useful color cues on the product page have become monochromatic scales that are easily lost on a design that doesn't seem to have been vetted for usability in any way. I suspect the color design doesn't meet WCAG in any way.
While the branding is strong, we are already captured customers, and usability is our key concern. Please offer a way to revert or select an alternate color scheme.
9 votes -
Dashboard for Enterprise Headless CMS
Enterprise CMS Headless architecture: Customer Dashboard for usage and platform health.
• Greater visibility and proactive reporting on their environment usage and performance. Specifically a dashboard (or reporting capability) that shows: • Usage/consumption metrics • Traffic patterns • Response times • Proactive monitoring data to help identify issues (e.g., 404 errors) before they become support tickets • The ability for customer teams to independently access this data, rather than having to request it from OptimizelyHaving this available standard vs. a custom build. This will help Enterprise customers shift from reactive issue handling → proactive management of their Optimizely environment
9 votes -
API support for environment copy-back lifecycle and post-copy script execution
As a development team managing multiple lower environments, we want API/PowerShell endpoints to orchestrate the full copy-back workflow, including a mechanism to run registered post-copy maintenance scripts, so that I can automate environment refresh end-to-end without manual PaaS Portal interaction.
Currently, the copy-back workflow requires manual steps in the PaaS Portal (stop environment, copy databases/blobs from Production, start environment). After the copy, teams must anonymise PII from the copied databases to comply with GDPR before the environment can be used. This anonymisation step cannot be triggered or orchestrated through the platform.
We would like the EpiCloud module or REST API…
9 votes -
As an editor, I'd like to see where my content blocks are used in the Catalog.
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 -
Insert an image into rich text editor from DAM
When the DAM Asset Picker is installed to the CMS, content authors should have the ability to "insert image" into a rich text field from the DAM, in addition to inserting from the CMS media library or uploading a new image.
9 votes -
Disable Allowed Content Types Description in CMS 12 Edit View
In CMS 12 Episerver Edit interface we noticed a new feature: above all ContentArea fields, a description appears listing allowed content types (Refer attachment).We’d like to have this removed. It seems to add more confusion than clarity for our editors. We already enforce allowed content types using the [AllowedTypes] attribute in code, so displaying the full list in the UI—especially including unrelated options like Episerver Forms elements—is unnecessary and distracting.
This description wasn’t present in CMS 11, and we would prefer to maintain that cleaner editor experience.9 votes -
Alerting for suspicious bot traffic spikes
Customers never get alerted to suspicious traffic spikes unless they impact site speed or uptime.
Ability to establish alerting for suspicious attacks, even if they are addressed by cloudflare before they impact site performance.9 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.
8 votes
- Don't see your idea?