Bulk list view action creates many notifications in backend, is it right?

[PeterKvayt]

I have noticed that when we use bulk actions with list view, e.g. publish, it does not trigger one publish notification. Instead it triggers published notification per selected content.

So can we call it a bulk operation in terms of backend implementation?

I think it will be great to implement these bulk actions in way where bulk publish list view action will trigger only one publish notification with many IContent entities instead of one publish notification per selected entity.

[iOvergaard]

I have noticed that when we use bulk actions with list view, e.g. publish, it does not trigger one publish notification. Instead it triggers published notification per selected content.

So can we call it a bulk operation in terms of backend implementation?

I think it will be great to implement these bulk actions in way where bulk publish list view action will trigger only one publish notification with many IContent entities instead of one publish notification per selected entity.

Hello 👋
This should be remedied in 15.3 already. The RC will be available Thursday next week.

[PeterKvayt]

Wow, great news!
I am looking forward to it!

[PeterKvayt]

@iOvergaard

I have tried this fix in 15.3.0-rc2. I have created a notification handler on unpublish and have configured a breakpoint in it. I have created a list view with items in the content tree. I have applied bulk unpublish and on each item, my breakpoint has been hit. Is it a bulk behavior?
I thought on bulk list action I willl get only one notification in notification handler with all entities instead of notification per entity.

I know, that you kinda frontend dev (sorry if I am wrong), but if we have one UI notification, why do we still get many notifications in backed?

Could you please notify someone who is responsible for it?

[iOvergaard]

Hi, this sounds like a bug. I have created it on the tracker at #18675, and we'll look into it.