A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Ryan Bare
Ryan Bare  -  CMS
Mar 25, 2019
  3450
(2 votes)

Marking notifications as read automatically

Users often have a large number of unread notifications displayed in their notification icon badge. While opening the window temporarily clears the badge, the number returns on a page reload. This has been discouraging users from utilizing notifications, as they are not using the "Mark all as read" button.

In CMS 11.19.0, all notifications will now automatically be marked as read when the notification window is closed. The notifications will retain their yellow "unread" background until either the notification is clicked, or upon a page reload. This means the "Mark all as read" button and the context menu with the "Mark as read" option are no longer necessary and have been removed. 

Mar 25, 2019

Comments

Please login to comment.
Latest blogs
Building simple Opal tools for product search and content creation

Optimizely Opal tools make it easy for AI agents to call your APIs – in this post we’ll build a small ASP.NET host that exposes two of them: one fo...

Pär Wissmark | Dec 13, 2025 |

CMS Audiences - check all usage

Sometimes you want to check if an Audience from your CMS (former Visitor Group) has been used by which page(and which version of that page) Then yo...

Tuan Anh Hoang | Dec 12, 2025

Data Imports in Optimizely: Part 2 - Query data efficiently

One of the more time consuming parts of an import is looking up data to update. Naively, it is possible to use the PageCriteriaQueryService to quer...

Matt FitzGerald-Chamberlain | Dec 11, 2025 |

Beginner's Guide for Optimizely Backend Developers

Developing with Optimizely (formerly Episerver) requires more than just technical know‑how. It’s about respecting the editor’s perspective, ensurin...

MilosR | Dec 10, 2025