PHPackages                             montikids/module-message-popup - 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. [Queues & Workers](/categories/queues)
4. /
5. montikids/module-message-popup

ActiveMagento2-component[Queues & Workers](/categories/queues)

montikids/module-message-popup
==============================

Magento 2 popup messages module

1.0.0(3y ago)314MITPHPPHP >=7.2

Since Aug 13Pushed 3y ago2 watchersCompare

[ Source](https://github.com/montikids/module-message-popup)[ Packagist](https://packagist.org/packages/montikids/module-message-popup)[ Docs](https://github.com/montikids/module-message-popup)[ RSS](/packages/montikids-module-message-popup/feed)WikiDiscussions master Synced today

READMEChangelog (1)DependenciesVersions (2)Used By (0)

About the module
================

[](#about-the-module)

The module allows us to use popups to display notification messages. It works for both: frontend and admin areas.

It also is quite flexible. For instance, you can use it only for displaying error messages for admins and keep all the other notifications displaying in the standard way. Furthermore, you don't have to replace standard notifications at all, just use it for custom-defined messages in places you need it.

Main features
=============

[](#main-features)

- Adding a custom popup notification is the frontend area with a single line of code, the same way you do it for the standard Magento notifications
- Adding a custom popup notification is the admin area with a single line of code, the same way you do it for the standard Magento notifications
- Displaying popup notifications on success/error AJAX responses in the admin area (for custom AJAX grids and forms)
- Allowing using certain HTML tags in the notification text: `div`, `span`, `b`, `strong`, `i`, `em`, `u`, `a`, `br`
- `OPTIONAL` Replacing all the standard notifications in the frontend area
    - Success notifications (turn it on/off at any moment)
    - Error notifications (turn it on/off at any moment)
    - Warning notifications (turn it on/off at any moment)
    - Notice notifications (turn it on/off at any moment)
- `OPTIONAL` Replacing all the standard notifications in the admin area
    - Success notifications (turn it on/off at any moment)
    - Error notifications (turn it on/off at any moment)
    - Warning notifications (turn it on/off at any moment)
    - Notice notifications (turn it on/off at any moment)
- Popups adapted for mobile devises

How does it look like
=====================

[](#how-does-it-look-like)

Admin area
----------

[](#admin-area)

### Success notification

[](#success-notification)

[![Admin success popup](docs/img/sample/notification-admin-success.png)](docs/img/sample/notification-admin-success.png)

### Error notification

[](#error-notification)

[![Admin error popup](docs/img/sample/notification-admin-error.png)](docs/img/sample/notification-admin-error.png)

### Warning notification

[](#warning-notification)

[![Admin warning popup](docs/img/sample/notification-admin-warning.png)](docs/img/sample/notification-admin-warning.png)

Frontend area
-------------

[](#frontend-area)

### Success notification

[](#success-notification-1)

[![Frontend success popup](docs/img/sample/notification-frontend-success.png)](docs/img/sample/notification-frontend-success.png)

### Notice notification

[](#notice-notification)

[![Frontend notice popup](docs/img/sample/notification-frontend-notice.png)](docs/img/sample/notification-frontend-notice.png)

### Warning notification

[](#warning-notification-1)

[![Frontend warning popup](docs/img/sample/notification-frontend-warning.png)](docs/img/sample/notification-frontend-warning.png)

### Error notification

[](#error-notification-1)

[![Frontend error popup](docs/img/sample/notification-frontend-error.png)](docs/img/sample/notification-frontend-error.png)

How to use
==========

[](#how-to-use)

Add a new popup message in any area
-----------------------------------

[](#add-a-new-popup-message-in-any-area)

It's a two-step action.

1. Add the message manager to the constructor of your controller

```
// ...
use Montikids\MessagePopup\Model\Manager\PopupMessageProxy;

// ...
public function __construct(
    // ...
    PopupMessageProxy $messageManager,
) {
    // ...
    $this->messageManager = $messageManager;
}
```

2. Add messages of any type as you do this with the standard Magento's message manager. You can do this because the `PopupMessageProxy` class implements the `\Magento\Framework\Message\ManagerInterface` interface.

```
$this->messageManager->addSuccessMessage(__("You're awesome!"));
```

Display currently existed messages in popups
--------------------------------------------

[](#display-currently-existed-messages-in-popups)

1. Go to the admin settings `Stores -> Configuration -> Montikids -> Message Popup`
2. Make sure you enabled the module itself
3. Make sure you allowed popup notifications in the desired area
4. Enable the replacement mode for the area
5. Select which types of the notifications you want to see in popups
6. Save the configuration
7. Flush the config cache [![Enabling the replacement mode](docs/img/guides/admin-config-replace-mode.png)](docs/img/guides/admin-config-replace-mode.png)

Display popup on AJAX response
------------------------------

[](#display-popup-on-ajax-response)

It's intended to be used with AJAX forms in the admin area, when you display the form in a popup, instead of redirecting to an edit page. You can try to use it with another UI components hat make AJAX calls, but it's not tested yet.

1. Go to the admin settings `Stores -> Configuration -> Montikids -> Message Popup`

```

        false
        Your fieldset name
        fieldset

                success

                mk_message

                type

                label

                text

                true

                true

```

You don't have to specify each option, only the ones you want to override. Potentially, nn case you're okay with the default values, is can be as simple as that:

```

        false
        Your fieldset name
        fieldset

```

An example of the possible structure of your AJAX response JSON body:

```
{
    "success": true,
    "mk_message": {
        "type": "success",
        "text": "Person data updated successfully",
        "label": null
    }
}
```

Local developing
================

[](#local-developing)

The is only one of several options, but I think it's the simplest one.

The main approach is to clone the repository inside a separate folder and tell composer to use this folder as source of the package.

If you don't like it, feel free using other approaches, like git submodules, Modman, or direct cloning inside the `app/code` folder.

Go to the root of your Magento installation and create a new folder inside your Magento project:

```
mkdir -p app/packages/montikids
```

Go inside:

```
cd app/packages/montikids
```

Clone the package repository:

```
git clone git@github.com:montikids/module-message-popup.git
```

Go back to the root of your project:

```
cd -
```

Tell composer to load the package from the local path:

```
composer config repositories.montikids/module-message-popup path app/packages/montikids/module-message-popup
```

Install the package as usual:

```
composer require montikids/module-message-popup
```

As a result, you get symlinked your `app/packages/montikids/module-message-popup` folder to the `vendor/montikids/module-message-popup`.

The main difference between this and just placing the repository into `app/code` that you can always make sure your `composer.json` is correct and the module is compatible with your project.

If you have already installed the module via composer, remove the folder first:

```
rm -rf vendor/montikids/module-message-popup
```

###  Health Score

22

—

LowBetter than 21% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity9

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity42

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

Unknown

Total

1

Last Release

1419d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/493f43bb02cfc7de6b145067f8836bfa4c02cf482c81b4484e6a01b48244dd03?d=identicon)[devs@montikids.com](/maintainers/devs@montikids.com)

---

Top Contributors

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

---

Tags

messagenotificationsmodulepopupmagento 2

### Embed Badge

![Health badge](/badges/montikids-module-message-popup/health.svg)

```
[![Health](https://phpackages.com/badges/montikids-module-message-popup/health.svg)](https://phpackages.com/packages/montikids-module-message-popup)
```

###  Alternatives

[php-amqplib/php-amqplib

Formerly videlalvaro/php-amqplib. This library is a pure PHP implementation of the AMQP protocol. It's been tested against RabbitMQ.

4.6k132.3M1.0k](/packages/php-amqplib-php-amqplib)[aws/aws-php-sns-message-validator

Amazon SNS message validation for PHP

22223.4M117](/packages/aws-aws-php-sns-message-validator)[fotografde/cakephp-sms

SMS Plugin for CakePHP

1273.2k](/packages/fotografde-cakephp-sms)

PHPackages © 2026

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