PHPackages                             mediadreams/md-notifications - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Mail & Notifications](/categories/mail)
4. /
5. mediadreams/md-notifications

ActiveTypo3-cms-extension[Mail & Notifications](/categories/mail)

mediadreams/md-notifications
============================

Notify frontend users about the creation of new data records. Every data type can be configured easily, for example pages (blog posts) or tx\_news records.

v1.0.4(9mo ago)01911GPL-2.0-or-laterPHP

Since Apr 16Pushed 2mo ago2 watchersCompare

[ Source](https://github.com/cdaecke/md_notifications)[ Packagist](https://packagist.org/packages/mediadreams/md-notifications)[ RSS](/packages/mediadreams-md-notifications/feed)WikiDiscussions master Synced today

READMEChangelog (4)Dependencies (1)Versions (6)Used By (0)

TYPO3 Extension `md_notifications`
==================================

[](#typo3-extension-md_notifications)

This extension adds notifications to configured record types for frontend users. In a list, a frontend user can see, whether or not an item was read by himself. Additional it is possible to show the number of notifications for each record type or for all record types together.

Requirements
------------

[](#requirements)

- TYPO3 v12.4 || v13.4

Screenshots
-----------

[](#screenshots)

[![Screenshot list](./Documentation/Images/list_view.png?raw=true "List view")](./Documentation/Images/list_view.png?raw=true)

Installation
------------

[](#installation)

- Install the extension by using composer (`composer req mediadreams/md-notifications`) or use the extension manager
- Include the static TypoScript of the extension
- Configure the extension (see chapter [Configuration](#configuration))

Configuration
-------------

[](#configuration)

Configuration is done in the sites configuration file. Either add the configuration directly in `config/sites/{site-itentifier}/config.yaml`, or import a YAML file in your site configuration by using this command:

```
imports:
    - { resource: "EXT:my_extension/Configuration/Yaml/MdNotifications.yaml" }

```

Following configuration can be added:

```
md_notifications:
    # The page Id, where the notification records get stored
    # If no `storagePid` is provided, the records will be saved on page Id = 0
    storagePid: 123

    # If this is set, notifications will be saved for users who belong to groupId only.
    feGroup: 3

    # Configure recod types for notifications
    # All record types can be configured. Just add a section for the table name of the record.

    # All pages which have page Id 6 in it's rootline, will get notifications.
    pages:
        - 6

    # All news records which will be saved on a pages within the rootline of page 2 or 16 will receive notofications.
    tx_news_domain_model_news:
        - 2
        - 16

```

Hint:
You can use environment variables in the site configuration like this:

```
storagePid: "%env(md_notifications_storagePid)%"

```

Usage
-----

[](#usage)

As soon as you have installed and activated the extension, it will hook into the saving process of records. Everytime a backend user adds a configured record, the unread info for this record and the configured `feUsers` will be added.

### List plugin

[](#list-plugin)

The extension ships a content element `Notifications`, which shows a list of all notifications for the logged in user. In the `Plugin`-tab you have the following configuration options:

- `Record keys`
    Comma separated list of record keys (table names). Leave empty, if all records shall be shown.
    Example: `pages, tx_news_domain_model_news`
- `Startingpoint`
    The page on which the notification records are stored.

### Notification counter

[](#notification-counter)

This counter will show the number of notifications for a user.

Use following code in your fluid template in order to get number of all notifications:

```

```

Use this to get number of notifications for example for `pages`and `tx_news_domain_model_news` records:

```

```

### Show notification info of record

[](#show-notification-info-of-record)

Use the following code in the fluid template to show, whether the current logged in feUser has read the item.

Example for a `page`-record:

```

```

Example for a `news`-record:

```

```

### Remove notification info

[](#remove-notification-info)

Remove the notification info as soon, as the user has read the item. Use the following code in your fluid template.

Example for a `page`-record:

```

```

Example for a `news`-record:

```

```

### Send reminder emails

[](#send-reminder-emails)

You can send reminder emails about notifications, which are not seen yet. Therefor you will find a scheduler task called `mdNotifications:reminder`.

Setup scheduler task:

- Go to `Scheduler`
- Click `New task`
- Select `Execute console commands` in the `Task`-dropdown
- Select `mdNotifications:reminder` in the dropdown `Schedulable Command`
- Add a value in the field `Frequency`
- Press the `Save` button
- Add value for `storages`. This is a comma separated list of IDs where the notification data is stored.
- Add value for `listPageUid`. This is the Uid of the page, which holds the list of notification items. This page will be linked in the email.
- Add value for `mailSubject`. The is the subject of the email, which will be sent.
- Add optional value `mailTemplate`. With this option, your are able to set a templates for the task. Enter the name of the HTML file, which shall be used for the e-mail.
- Press the Save button again

Hint:
You can setup individual tasks for individual notification types. Therefor add more than one `mdNotifications:reminder`-tasks and configure individually.

#### E-Mail template

[](#e-mail-template)

In order to change the E-Mail template, add the path to your site extension in global configuration in the section `[MAIL][templateRootPaths]`. As soon, as you have added the path to your extension, you can copy the `Notifications.html` template from `Resources/Private/Templates/Email/` to your path and do your modifications.

**Important:** This extension registers its template root path with the array index `2025`. TYPO3 resolves `templateRootPaths` from the highest index to the lowest, so your custom path must be registered with an index **higher than `2025`** to take precedence.

Example in your `ext_localconf.php`:

```
$GLOBALS['TYPO3_CONF_VARS']['MAIL']['templateRootPaths'][2100] = 'EXT:my_sitepackage/Resources/Private/Templates/Email/';
```

Place your customized template at:

```
EXT:my_sitepackage/Resources/Private/Templates/Email/Notifications.html

```

### Remove items

[](#remove-items)

If you wish to remove unread items, which are older than a certain time, you can use the following scheduler task:

- Go to `Scheduler`
- Click `New task`
- Select `Table garbage collection` in the `Task`-dropdown
- Select `tx_mdnotifications_domain_model_notification` from `Table to clean up`-dropdown
- Set a value in field `Delete entries older than given number of days`
- Add a value in the field `Frequency`
- Press the `Save` button

Bugs and Known Issues
---------------------

[](#bugs-and-known-issues)

If you find a bug, it would be nice if you add an issue on [Github](https://github.com/cdaecke/md_notifications/issues).

THANKS
======

[](#thanks)

Thanks a lot to all who make this outstanding TYPO3 project possible!

The TYPO3 project - inspiring people to share!

Credits
-------

[](#credits)

- Extension icon was kindly taken from [Font Awesome](https://fontawesome.com/icons/bell?f=classic&s=solid).

###  Health Score

36

—

LowBetter than 79% of packages

Maintenance72

Regular maintenance activity

Popularity15

Limited adoption so far

Community9

Small or concentrated contributor base

Maturity41

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~37 days

Total

5

Last Release

295d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/c5d77efbf0d5d788c58c6c783c044fc88a8009cdc65dff094a6b8d7de862de94?d=identicon)[mediadreams](/maintainers/mediadreams)

---

Top Contributors

[![cdaecke](https://avatars.githubusercontent.com/u/2102444?v=4)](https://github.com/cdaecke "cdaecke (23 commits)")

---

Tags

notificationsphptypo3typo3-cms-extensiontypo3-extensionnotificationsextensiontypo3

### Embed Badge

![Health badge](/badges/mediadreams-md-notifications/health.svg)

```
[![Health](https://phpackages.com/badges/mediadreams-md-notifications/health.svg)](https://phpackages.com/packages/mediadreams-md-notifications)
```

###  Alternatives

[directmailteam/direct-mail

Advanced Direct Mail/Newsletter mailer system with sophisticated options for personalization of emails including response statistics.

42212.4k2](/packages/directmailteam-direct-mail)[mediaessenz/mail

Powerful newsletter system for TYPO3

1111.2k3](/packages/mediaessenz-mail)[sup7even/mailchimp

Simple MailChimp integration to let users register to a specific list

1532.0k](/packages/sup7even-mailchimp)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)