Problem/Motivation

Hi,

In the module says:
"Notification widget: DANSE comes with a view which displays a drop-down widget anywhere on the site (configured as a block)"

Is there a documentation how to enable this block?
I see only views, but there is no blocks, the views are all pages. Should the block be created? Should it be ready?

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

jukka792 created an issue. See original summary.

jurgenhaas’s picture

Version: 2.2.5 » 2.2.x-dev
Component: Documentation » Code
Category: Support request » Task

Good 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.

Anonymous’s picture

Anonymous’s picture

I 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.

jurgenhaas’s picture

Assigned: Unassigned » jurgenhaas

@Janner I'm working on it.

Anonymous’s picture

@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 🤦‍♂️ ).

  • jurgenhaas committed 503012f7 on 2.2.x
    Issue #3284137 by jurgenhaas: Notifications widget
    
jurgenhaas’s picture

Assigned: jurgenhaas » Unassigned
Priority: Minor » Normal
Status: Active » Needs review
Related issues: +#3095941: Finalize on-site notification options

A first version of this is now available in the 2.2.x-dev release and is waiting for feedback.

Here is what is implemented:

  • notification icon with a drop down, showing new notifications only
  • a tab in the user profile going to the notification archive
  • an rss feed for each user

For testing this, please update to the latest dev release, flush your cache and then import the config entities from the config/optional directory. You can do that with drush, e.g. with this command:

drush cim --partial --source modules/contrib/danse/config/optional
jurgenhaas’s picture

Status: Needs review » Fixed

Looks 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

gnumatrix’s picture

Being 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.

jurgenhaas’s picture

Thanks @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 ;-)

gnumatrix’s picture

Wow, interesting. That's a big change for sure! Change can be exciting though, so looking forward to it.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.