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.First of all thanks for the useful module!
I've patched the module to serve our needs a bit better and thought the module could use the improvement as well. The Slack change notification is very handy but knowing what has changed can be even more useful. In our case, the client has access to an admin-level account and makes changes that sometimes require our immediate attention (depending on the config changes). This improvement helps with acting on time. I've attached the patch including the changes we made.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | list_config_changes-3128111-6.patch | 6.86 KB | fjgarlin |
| #5 | config_notify_slack_message.png | 48.21 KB | 3li |
| #5 | config_notify_email_message.png | 54.87 KB | 3li |
| #4 | list_config_changes-3128111-4.patch | 6.64 KB | 3li |
| config_notify-change_list_improvement.patch | 1.45 KB | mleprohon |
Comments
Comment #2
fjgarlin CreditAttribution: fjgarlin as a volunteer and commentedThanks for the suggestion/patch. A couple of things/suggestions though.
* The "```" is specific to slack, so that won't probably render nicely on an email. We'd need to find a solution that displays nicely on any service.
* Also, whilst this feature might be useful to the case you're working on, it might not always be needed. For this, I suggest adding a checkbox for "Verbose output" or similar, and when checked, this additional information could be added to the message.
If I find the time I can work on these suggestions soon, but you're also welcome to give them a go.
Best.
Comment #3
fjgarlin CreditAttribution: fjgarlin as a volunteer and commentedComment #4
3liHave taken the original patch and expanded upon it.
Created the patch on 8.x-1.2 but also tested it on 8.x-1.x-dev.
Comment #5
3liExample images of the new notifications.
Comment #6
fjgarlin CreditAttribution: fjgarlin as a volunteer and commentedThanks @elistone.
Uploading patch with same approach you followed, but refactoring a bit the message generation (hopefully simplifying it a bit) and applying coding standards.
Comment #8
fjgarlin CreditAttribution: fjgarlin as a volunteer and commentedThanks Eli.Stone and mleprohon. I've committed the above patch. Thanks for your patches and ideas!
Comment #9
fjgarlin CreditAttribution: fjgarlin as a volunteer and commented