Notification Banners

Theme component
41

Okay, just tested one thing. Dismissed the test banner, changed the start and end date, saved it and reloaded the page. No banner.

So once gone for a user, gone for good?

1 Like
42

Ah! That’s a very good point actually @Roi, and the short answer is yes.

Each banner is assigned an ID based on the index number, and the plugin-outlet name. Then, the ID of the closed banners are stored to browser’s local storage.

Screenshot 2025-11-04 at 3.50.59 PM
Screenshot 2025-11-04 at 3.50.59 PM2000×600 66.8 KB

So, if a banner is closed, even if its configuration’s changes it will remain hidden.

I see that can be a problem; I’ll think of a better way to handle this. – Suggestions are welcome : )

1 Like
43

The versatile-banner uses a cookie name setting, which admins can change to make the banner visible again for users who dismissed it.

1 Like
44

Thanks for the pointer @Moin, renaming the cookie to invalidate the saved cookies looks like a very practical solution.

In Notification Banners the banners can be moved up and down to change the sorting order, or change the outlets. That can potentially keep a new banner hidden if there was a banner in the same place and dismissed previously.

Seems I need to change how the IDs defined, and then perhaps adapt the cookie method. :thinking:

45

Then cookies seem to be a better way than the ids, especially when the ids change when you change the sorting order. :eyes:

In my eyes it would be useful to generate a new (cookie) id every time the banner is changed.

About cycles: If it was Christmas already I would wish for a cycle which can be done in weekdays (one or more) and day of month (one or more). And maybe for both something like “every x”, so that I could choose e.g. “every second Monday and Friday” or "every 1st and 16th of every third month).

46

Actually, I was able to solve this issue with a hybrid solution.

A new Banner config version setting which will apply to all banners; and new individual Banner ID values.

The real IDs for each banner are constructed using both of the values. This method should provide a better flexibility IMHO:

  • An individual banner visibility can be reset by updating its Banner ID without affecting the other banners’ visibility.
  • If multiple banners’, or all banners’ visibility needs to be reset, then the Banner config version can be updated.

I will deploy this change soon.

Notification Banners settings
Notification Banners settings800×1700 104 KB

An individual banner configuration
An individual banner configuration800×1520 112 KB

update: The v1.4.0 is now out.

Introduced a unique[1], required Banner ID field for each notification banner and updated related settings, migration logic, and tests to support this change. Additionally, added a Banner config version setting to help reset banner visibility for users when important changes occur. These improvements ensures that banner dismissal tracking to be more robust and future-proof.

  1. The uniqueness is up to the user. Unfortunately the theme object settings don’t allow requiring unique values. However, the tab label now uses the ID value to make them more visible. ↩︎

47

Wow great! Thank you! I will test and give you feedback. :slight_smile:

1 Like
48

Works as said! Great. Thank you again! :slight_smile:

1 Like