Hello! I'm not entirely sure if this fits in feedback or suggestions, because it's a little bit of both. Since it's a suggestion on an existing feature, I thought I should put it here in the feedback category.

On the legacy site, when I have events/notifications, they appear in the sidebar by category and I can dismiss either individual notifications or an entire category of notifications without leaving the page I'm currently on. This makes it really easy to scan what's happened since I last logged on and what tasks I should complete. For instance, things like shop sales, forum replies or tags or new posts, pets finishing training, comments from other users, gifts received, shop buffs received or wearing off, achievements received, etc.

I would really like to also have that on Kumos. Currently, I do get events in the sidebar, but:

• I can only see three at a time on the sidebar. Then it says how many more I have, but I have to navigate to another page to view them.
• I can only individually dismiss the ones displayed on the sidebar, and if I want to dismiss all of them at once OR dismiss additional "view more" notifications individually, I have to navigate to another page to do so.
• Notifications aren't broken into categories and are only displayed as one list - compouding with the previous bullet point, I also can't dismiss a group of notifications by category while leaving another category up, unless I individually sort through and dismiss individual notifications.
• Any notifications I dismiss on the legacy site do not get dismissed from the Kumos sidebar. The sidebar still displays the events and how many I have, but when I navigate to the view all events page, the number of notifications shows even though my events inbox says "There are no events to display." I have to then click "Delete All" for them to disappear from the Kumos sidebar.

Beyond just nostalgia for old-school-style web pages, I have really avoided using Kumos largely because the notifications are so frustrating. I would really love to see the way notifications are categorized, displayed, and dismissed reflect how they do on the legacy site (and would love if dismissing on the legacy site also transferred to Kumos or vice versa).

Thank you for reading this feedback/suggestion, and thank you for all the work you're doing on Kumos!

Amazing! So fast, too!! Thank you so much. I'll see how it works as my events pop up the next few days. :-)

Hi , I have an update! The sidebar does show category now, but the events overall are not displaying correctly on Kumos.

On Legacy, my notifications are currently:

• 1 "Shop Purchases" event to tell me item(s) were bought from my shop
• 9 "Training Center" events, 8 for autotraining complete and 1 for an alert I set to notify me when another pet was done with regular non-auto training
• In total, 10 events in 2 categories.

When I check on Kumos, the sidebar shows:

• No shop purchase event
• 8 "Training Center" events (2 previews, "+6 more" note) ((The Training Center event previews shown are for the autotraining complete, so I think likely it's the additional alert I set for non-auto training that's missing.))
• And a bottom link for "View All Events (8 unread)"

When I click the view all events link, it takes me to the Event History page that displays:

• Total Events: 8
• Unread Events: 8
• On This Page: 0
• And reads "No events to display."

I haven't dismissed any notifications on the legacy site, so they should be showing on Kumos. It seems likely it was also doing this incorrectly before you pushed the update, but I didn't catch it because I was dismissing notifications on legacy first and then not seeing that reflected on Kumos, rather than also trying the other way around.

Which then led me to a maybe separate but maybe related issue on the Event History page - When I click "Refresh," I get a pop-up for a Livewire Internal Servor Error. At the top of the pop-up, the text reads:

• "LivewireExceptionsMethodNotFoundException
• vendor/livewire/livewire/src/Mechanisms/HandleComponents/HandleComponents.php:488
• Unable to call component method. Public method [loadEvents] not found on component"

There is also a button to copy the coding of the error, and I can provide the code if you need. I don't know if it's coding specific to me getting the error or something that pops up the same if you replicate the error on your account.

I know you said syncing dismissed notifications to legacy is a deeper task that you'll have on your to do list, but I thought this is useful information for when you get there!

That is super helpful 🙏 Will target them tomorrow, thank you!