Skip to content
Custom code for Message stack and Swiftmailer to create messages about new/changed nodes and comments and email them to subscribers.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
src/Commands Omit user 1 and anonymous users from actions, add patch for broken me… Jan 15, 2020
composer.json Add drush command install of install hook to finish configuration bec… Jan 1, 2020 Update README Dec 30, 2019

Custom Message Implementation

Custom code for Message stack and Swiftmailer to create messages about new/changed nodes and comments and email them to subscribers.

The following modules are used:

Using this code

The logic used for subscribing users to content and sending them emails includes the following. See message_integration.module and the message templates for more details.

  • All active users will automatically be subscribed to all new content. They can later unsubscribe if they want.
  • When a node is first published, the code will render the message view mode of the node in an HTML email and send it to the subscriber list.
  • When a new revision is created in a published node, the code will use Diff module to just display what changed and send the diff in an HTML email to the subscriber list.
  • When new comments are added, the code will notify the users subscribed to the node. The email will display the compact view mode of the content and the default view mode of the new comment an HTML email.
  • Admin users will be notified by email when new users register, using a custom mailing list instead of the usual subscription model.

To install on a new site:

This code is too opinionated to use as a normal contributed module. But you you can fork it, adjust it to your own needs, and use it elsewhere.

To use this on your own site, fork this code, then add the forked repository to your site's composer.json.

    "repositories": {
        "drupal": {
            "type": "composer",
            "url": ""
        "forked-repo/message_integration": {
            "type": "vcs",
            "url": "",
            "no-api": true

  • Make sure all the required code (with patches) is available by running composer require forked-repo/message_integration.
  • Enable this module, which will install all the other required modules: drush en message_integration
  • Lots of tweaky little steps can't be done until after everything is installed. Do them by running drush message_integration:configure after enabling the modules.
  • Edit the display mode for each content type to position the subscription flag where you want it on the default view mode of your content nodes, then enable the message view mode to control the display that will be rendered in messages.
  • Subscribe to some content.
  • Create/edit content and add comments to it.
  • Run cron to trigger queued messages and emails.
  • Navigate to admin/content/messages to see the generated messages.
  • Navigate to admin/structure/message to edit and change message templates.

Review the code in message_implementation.module to see what hooks are being used to generate messages. You can alter them as needed. You'll also want to edit the list of libraries used to generate HTML email to add your own theme libraries.

You can’t perform that action at this time.