Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
It is often useful to only send notifications for specific bundles.
Proposed resolution
Add bundle support
Remaining tasks
User interface changes
Add a bundle selection checkbox in the UI. If ticked, list the available bundles. If bundles are selected only send mails for entities matching these.
API changes
Pass entity bundle info service into settings form.
Data model changes
New bundles key in configuration. However the code is such that an upgrade path is not required.
Comment | File | Size | Author |
---|---|---|---|
#6 | 3-4-interdiff.txt | 599 bytes | alexpott |
#6 | 2803743.4.patch | 10.38 KB | alexpott |
#3 | 2803743.3.patch | 10.37 KB | alexpott |
| |||
#3 | 2-3-interdiff.txt | 504 bytes | alexpott |
#2 | 2803743.2.patch | 10.67 KB | alexpott |
|
Comments
Comment #2
alexpottHere it is...
Comment #3
alexpottRemoving an unnecessary change...
Comment #6
alexpottWhoops.
Comment #8
milos.kroulik CreditAttribution: milos.kroulik commentedThis seems to be working fine for me. Is this sufficient for RTBC?
Comment #9
milos.kroulik CreditAttribution: milos.kroulik commentedUseful follow up would be ability to set up different behaviours based on bundle.
Comment #10
LpSolit CreditAttribution: LpSolit as a volunteer commentedShouldn't each bundle have its own section (tab)? This way, one could send notifications to different users (and using different mail content) based on the bundle.
Comment #11
kybermanThank you, patch #6 is working correctly with current dev.
As @milos.kroulik and @LpSolit are saying, it would be better to split settings by bundles, so we can set different notification for different bundles.
I can imagine the same structure as we have here: "/admin/structure/types/manage/article/display".
- one main tab for every entity type
- one secondary tab for every bundle
- one vertical tab for every CRUD event