Closed (fixed)
Project:
DANSE Drupal - Audit - Notification - Subscription - Event
Version:
2.2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
4 Jun 2022 at 16:00 UTC
Updated:
30 Mar 2023 at 16:39 UTC
Jump to comment: Most recent
Comments
Comment #2
jurgenhaasGood question, it looks like it was lost and only lives in a customer project. But we can that back easily. What it was is simply a view which shows all unseen notifications for the current user and also prints the number of records in the header of the view. This view can be displayed in a block and that would then be styled with css so that only the number will be displayed and with a mouse over the list of notifications will drop-down.
If anyone wanted to build that a start a merge request in this issue, I'm happy to review and merge it into the module then.
Comment #3
Anonymous (not verified) commentedComment #4
Anonymous (not verified) commentedI am planning on more fully exploring DANSE early in the New Year with a view to overhauling the subscription/notification system on my site.
Does anyone have exports of the ‘missing’ views that they could share here (the notifications block and archive view for the user profile)? This would be really helpful and very much appreciated.
Comment #5
jurgenhaas@Janner I'm working on it.
Comment #6
Anonymous (not verified) commented@jurgenhaas excellent, thank you.
I figure that I've been stalking this module long enough and finally need to determine if I can make it work for my use case. On paper it's a good fit, but having an existing setup that sort of works has had me reluctant to change anything (or, in this case, even explore too deeply the possibility 🤦♂️ ).
Comment #8
jurgenhaasA first version of this is now available in the 2.2.x-dev release and is waiting for feedback.
Here is what is implemented:
For testing this, please update to the latest dev release, flush your cache and then import the config entities from the
config/optionaldirectory. You can do that with drush, e.g. with this command:Comment #9
jurgenhaasLooks like this topic has been asked for by many for a long period of time, for good reasons. It was just missing.
Somehow frustrating though, if a maintainer then gets around to provide the solution for it, nobody cares any more. No review and no feedback, as if it wasn't important in the first place.
Closing the issue, the code just landed in version 2.2.13
Comment #10
gnumatrix commentedBeing a Drupal maintainer seems to be a lonely and thankless job! I kind of wish the issues queues had a more social aspect. You know, like a "thumbs up" option or similar feedback mechanisms to encourage more activity. I realize it would not strictly help with the coding aspects, but might make for a more welcoming and interactive environment.
For example, this is a great development update! I'm sure I was one of the people asking for it some time ago. Needs a +1 button for sure.
Comment #11
jurgenhaasThanks @GNUMatrix this actually not too bad. In fact I really enjoy being a maintainer in the Drupal community.
The social aspects you're referring to with all the aspects you mentioned will be here soon, when issues will be migrated over to GitLab. Talking about a thankless job? Ask the engineers from the Drupal Association who are working hard on that part. Not only is that a gigantic job, there is also resistance from the community - like always when things are changing ;-)
Comment #12
gnumatrix commentedWow, interesting. That's a big change for sure! Change can be exciting though, so looking forward to it.