WordPress Notification plugin

Last update: Apr 25, 2022

Test Develop Stable

Notification

Notification banner

This is the public repository for Notification - the WordPress plugin.

This plugin allow you to send custom notifications about various events in WordPress. It also comes with simple yet powerful API by which you can add literally any trigger action.

By default it supports Email, Webhook and Webhook plain JSON notifications.

Default Triggers

Comment, Pingback, Trackback and Custom Comment Type

This covers all the comment types. Use comment, pingback, trackback, another_comment_type instead of the {comment_type_slug}.

Trigger name Trigger slug
Comment added comment/{comment_type_slug}/added
Comment approved comment/{comment_type_slug}/approved
Comment replied comment/{comment_type_slug}/replied
Comment spammed comment/{comment_type_slug}/spammed
Comment trashed comment/{comment_type_slug}/trashed
Comment unapproved comment/{comment_type_slug}/unapproved
Comment published comment/{comment_type_slug}/published
Media
Trigger name Trigger slug
Media added media/added
Media trashed media/trashed
Media updated media/updated
Plugin
Trigger name Trigger slug
Plugin activated plugin/activated
Plugin deactivated plugin/deactivated
Plugin installed plugin/installed
Plugin removed plugin/removed
Plugin updated plugin/updated
Post, Page and Custom Post Type

This covers all the custom post types, as well. Use post, page, product, another_post_type instead of the {post_type_slug}.

Trigger name Trigger slug
Post added post/{post_type_slug}/added
Post saved as a draft post/{post_type_slug}/drafted
Post sent for review post/{post_type_slug}/pending
Post approved post/{post_type_slug}/approved
Post published post/{post_type_slug}/published
Post trashed post/{post_type_slug}/trashed
Post updated post/{post_type_slug}/updated
Post scheduled post/{post_type_slug}/scheduled
Category, Tag and Custom Taxonomy

This covers all the taxonomies. Use category, post_tag, another_taxonomy instead of the {taxonomy_slug}.

Trigger name Trigger slug
Taxonomy term created taxonomny/{taxonomy_slug}/created
Taxonomy term deleted taxonomny/{taxonomy_slug}/deleted
Taxonomy term updated taxonomny/{taxonomy_slug}/updated
Theme
Trigger name Trigger slug
Theme installed theme/installed
Theme switched theme/switched
Theme updated theme/updated
User
Trigger name Trigger slug
User deleted user/deleted
User login user/login
User login failed user/login_failed
User logout user/logout
User password changed user/password_changed
User password reset request user/password_reset_request
User profile updated user/profile_updated
User role changed user/role_changed
WordPress
Trigger name Trigger slug
Available updates wordpress/updates_available
Privacy
Trigger name Trigger slug
Personal Data erased privacy/data-erased
Personal Data erase request privacy/data-erase-request
Personal Data exported privacy/data-exported
Personal Data export request privacy/data-export-request

Extensibility

The Notification plugin have multiple APIs which gives you the ability to customize the plugin. The most important ones are:

  • Trigger API - you can wrap any WordPress' do_action into a Trigger.
  • Carrier API - you can register a custom Carrier, like a service connection. Carriers are independent from Triggers and works with all default and custom Triggers out of the box. It's packed with configuration form builder.
  • Recipient API - you can register a custom Recipients for your Carriers. Like automatically pulled users from external database or simply custom user query with meta etc.
  • Resolver API - you can create another Merge Tag resolver, ie. {customtag param1} which is handled differently than a standard Merge Tag.
  • Settings API - for quick plugin Settings registration

Bundling the plugin

You can ship this plugin as a part of your plugin or theme. Just copy the plugin directory into your folder and require load.php file. Read more about the plugin bundling and plugin loading stack.

White labeling

You can integrate this plugin with your system with a simple white labeling, it's a single notification_whitelabel() function to call. Read the full white labeling documentation.

Quick links

Development version

You can download build development version from the Development workflow. Click the latest run and download generated artifact.

GitHub

https://github.com/bracketspace/notification
Comments
  • 1. emtpy metabox/acf value when triggered from rest-api

    when I save post (draft or publish status) in Admin Page, Notifications works very well. but if i send same data from rest api with metabox data or acf data.

    then Notifications fired with empty values.

    For Example) If i send new Post data like { title: "title", content: "content", meta_box: { "extradata": "extra" } }

    and my trigger has {postmeta {post_ID} extradata}. but this fired with blank value.

    I tested

    1. post "status = draft" data from rest-api => "draft trigger" fired => but it fired with blank data.
    2. i changed the status to "publish" on Admin page => "publish trigger" fired => worked with well.

    "add trigger" also fired with blank.

    I tested with "metabox" and "acf" but same result

    Reviewed by devjiro76 at 2019-03-09 18:47
  • 2. Trigger Not Firing During Gravity Forms Hook

    Bug description

    Using the 'gform_advancedpostcreation_post_after_creation' action hook, I am creating another post (CPT) using wp_insert_post. Neither the 'published' nor 'added' trigger works. The post is created properly but trigger is not fired. However, if I create the post manually through the admin section, it works properly.

    Expected behavior

    The trigger should fire.

    Environment

    • PHP: 7.4
    • WordPress: 5.9.2
    • Notification plugin: 8.0.10
    Reviewed by thekendog at 2022-03-11 18:00
  • 3. Scheduled posts and WPML

    Bug description

    I have multilingual website (finnish, english, swedish). When I create scheduled post (finnish) the merge tags in notifiction are different language (swedish) than the post which triggered notification. This happens only multilingual posts which are all scheduled to publish at same time.

    To reproduce

    Steps to reproduce the behavior:

    1. Create scheduled post which will notify conditionally (permalink for example) when the post is published.
    2. Translate the post to other languages available by duplicating the original post and then translate it independently (by pushing Translate independently button) and schedule publish time to the same as original. Note, notification will not trigger to other languages.
    3. When notification triggers by conditional rule only to the original post, the email tags are filled with other language.

    Expected behavior

    I would except that tags of the notification are filled with the metafields of the original post, not the translation which is published at same time.

    Environment

    • PHP: 7.4.3
    • WordPress: 5.8.2
    • Notification plugin: 8.0.5
    • Notification : Conditionals: 2.0.0
    • Notification : Custom Fields: 2.0.0
    • WPML Multilingual CMS: 4.4.12

    Additional context

    This did't happened before Notification plugin 8.0.

    Problem does't occur if translations are scheduled couple of minutes later than the original post which triggers the notification.

    Reviewed by plarjos at 2021-11-19 13:56
  • 4. Custom post type not showing on settings page

    I am trying to add a notification for my custom post type called 'message', but it isn't showing in the post types list on the settings page. Only Page and Post are showing but i have a few other custom post types as well. Any ideas why? Thanks

    Reviewed by rozv at 2017-01-13 17:14
  • 5. Notification gets cleared when using HTML tags

    IMPORTANT: See the Troubleshooting page: https://docs.bracketspace.com/notification/user-guide/troubleshooting before creating an issue.

    Bug description

    I'm using your WordPress plugin Notifications and are quite happy with it. But I'm constantly failing to create HTML notifications.

    Every time when I add tags of HTML into the body and hit save, the whole notification gets cleared. I've checked all the different settings and also the logging but there is no output at all. Please find attached some screenshots of my simple test.

    Thanks in advance for your support

    To reproduce

    Steps to reproduce the behavior:

    1. Create a new notification
    2. Add some kind of HTML tags into the body
    3. Save the notification
    4. Notification gets cleared

    Expected behavior

    A clear and concise description of what you expected to happen.

    Environment

    • PHP: 7.4.15
    • WordPress: 5.6.2
    • Notification plugin: 7.2.3

    Screenshots

    No HTML, after save: no_html_after_save With HTML, before save: with_html_before_save With HTML, after save: with_html_after_save

    Additional context

    ### wp-core ###
    
    version: 5.6.2
    site_language: de_DE
    user_language: de_DE
    timezone: Europe/Berlin
    permalink: /%year%/%monthnum%/%day%/%postname%/
    https_status: true
    multisite: false
    user_registration: 1
    blog_public: 1
    default_comment_status: closed
    environment_type: production
    user_count: 20
    dotorg_communication: true
    
    ### wp-paths-sizes ###
    
    wordpress_path: /redacted_path
    wordpress_size: 69,79 MB (73181845 bytes)
    uploads_path: /redacted_path/wp-content/uploads
    uploads_size: 689,39 MB (722878657 bytes)
    themes_path: /redacted_path/wp-content/themes
    themes_size: 33,90 MB (35549269 bytes)
    plugins_path: /redacted_path/wp-content/plugins
    plugins_size: 59,58 MB (62469273 bytes)
    database_size: 12,38 MB (12977258 bytes)
    total_size: 865,04 MB (907056302 bytes)
    
    ### wp-active-theme ###
    
    name: Sparkling (sparkling)
    version: 2.4.8
    author: Colorlib
    author_website: http://colorlib.com/
    parent_theme: none
    theme_features: core-block-patterns, automatic-feed-links, post-thumbnails, menus, post-formats, custom-background, html5, title-tag, custom-header, infinite-scroll, woocommerce, wc-product-gallery-zoom, wc-product-gallery-lightbox, wc-product-gallery-slider, widgets
    theme_path: /redacted_path/wp-content/themes/sparkling
    auto_update: Deaktiviert
    
    ### wp-themes-inactive (1) ###
    
    Fiji 2: version: 1.1.1, author: Flothemes, Automatische Aktualisierungen deaktiviert
    
    ### wp-plugins-active (10) ###
    
    Archived Post Status: version: 0.3.7, author: Frankie Jarrett, Automatische Aktualisierungen deaktiviert
    Breeze: version: 1.1.9, author: Cloudways, Automatische Aktualisierungen deaktiviert
    Category Posts Widget: version: 4.9.10, author: TipTopPress, Automatische Aktualisierungen deaktiviert
    EWWW Image Optimizer: version: 6.0.3, author: Exactly WWW, Automatische Aktualisierungen deaktiviert
    Link To Bible: version: 2.5.8, author: Thomas Kuhlmann, Automatische Aktualisierungen deaktiviert
    Notification: version: 7.2.3, author: BracketSpace (latest version: 7.2.4), Automatische Aktualisierungen deaktiviert
    OG: version: 2.8.9, author: Marcin Pietrzak, Automatische Aktualisierungen deaktiviert
    Redirection: version: 5.0.1, author: John Godley, Automatische Aktualisierungen deaktiviert
    WP Featherlight: version: 1.3.4, author: Cipher, Automatische Aktualisierungen deaktiviert
    WP Statistics: version: 13.0.6, author: VeronaLabs, Automatische Aktualisierungen deaktiviert
    
    ### wp-media ###
    
    image_editor: EWWWIO_Imagick_Editor
    imagick_module_version: 1691
    imagemagick_version: ImageMagick 6.9.11-39 Q16 x86_64 2020-12-01 https://imagemagick.org
    file_uploads: File uploads is turned off
    post_max_size: 76M
    upload_max_filesize: 64M
    max_effective_size: 64 MB
    max_file_uploads: 20
    gd_version: bundled (2.1.0 compatible)
    ghostscript_version: not available
    
    ### wp-server ###
    
    server_architecture: Linux localhost 3.10.0-1127.10.1.el7.x86_64 #1 SMP Linux localhost 3.10.0-1127.10.1.el7.x86_64 #1 SMP Linux localhost 3.10.0-1127.10.1.el7.x86_64 #1 SMP
    httpd_software: Apache/2.4.46 (Unix)
    php_version: 7.4.15 64bit
    php_sapi: cgi-fcgi
    max_input_variables: 4000
    time_limit: 240
    memory_limit: 256M
    max_input_time: 60
    upload_max_filesize: 64M
    php_post_max_size: 76M
    curl_version: 7.73.0 OpenSSL/1.0.2u
    suhosin: false
    imagick_availability: true
    pretty_permalinks: true
    htaccess_extra_rules: true
    
    ### wp-database ###
    
    extension: mysqli
    server_version: 5.6.42-log
    client_version: 5.6.45
    
    ### wp-constants ###
    
    WP_HOME: undefined
    WP_SITEURL: undefined
    WP_CONTENT_DIR: /redacted_path/wp-content
    WP_PLUGIN_DIR: /redacted_path/wp-content/plugins
    WP_MAX_MEMORY_LIMIT: 256M
    WP_DEBUG: false
    WP_DEBUG_DISPLAY: true
    WP_DEBUG_LOG: false
    SCRIPT_DEBUG: false
    WP_CACHE: false
    CONCATENATE_SCRIPTS: undefined
    COMPRESS_SCRIPTS: undefined
    COMPRESS_CSS: undefined
    WP_LOCAL_DEV: undefined
    DB_CHARSET: utf8mb4
    DB_COLLATE: undefined
    
    ### wp-filesystem ###
    
    wordpress: writable
    wp-content: writable
    uploads: writable
    plugins: writable
    themes: writable
    
    
    Reviewed by escoand at 2021-03-10 21:23
  • 6. Feature request: post_publication_datetime for Published trigger

    Would it be possible to have the post_publication_datetime merge tag for <post_type> Published trigger? We already can use it for Scheduled trigger, but somehow it's missing for Published. Both current values (creation and modification) don't always reflect the published date time.

    Reviewed by jphorn at 2019-08-01 13:35
  • 7. Notification sent to wrong adress

    Hi! Thanks for a great plugin! I have two notifications registered for when a user is registered; one for sending a confirm email to {user_email} and one for sending a notice about new user to my own email. Now the users gets two (of the same confirming email) and I get none. So Notification is sending two emails but is skipping the later and duplication the first. Now if I try to add a third notification to my own email (about user registration) the user will get three emails and I will still get none. I don't know if this i a bug with the new update or if it's a result from me trying to add custom merge tags as instructed at bracketspace.com

    Reviewed by JohanHjalmarsson at 2018-04-09 11:37
  • 8. Default WordPress emails still work

    So I've set up a custom notification for a post comment. I want it to replace the default email, so I check the New comment box in the Integration section of the plugin. But the default notification email is still sent. How do I fix this? It's not very nice to receive two notifications.

    Reviewed by ivankharitonov at 2019-09-13 08:47
  • 9. New option to allow unfiltered html in email body

    Hi, I've added a new option in settings to allow unfiltered html in email body. The default value is false so the behaviour of the plugin doesn't change, unless this option is not enabled explicitly. Once the option is enabled the EditorField is disabled and TextareaField is used in place, this is needed because the editor, in visual mode, mess up with unfiltered html. The utility of this is to be able to use complex html templates.

    On a side note, I'd like to contribute adding an italian translation. Should I do this on translate.wordpress.org or is there any other way?

    Reviewed by martinellimarco at 2018-07-22 21:59
  • 10. hooking into notification_register_recipient not working

    Hi,

    I want to be able to create custom recipients.

    I've created a BackofficeRecipient which extends BracketSpace\Notification\Abstracts\Recipient. Calling the class with:

    notification_register_recipient('email', new BackofficeRecipient());
    

    does not result in the desired action.

    Also wrapping the code in an action ('notification/boot/initial') of filter ('notification/recipients'), does nothing. Am I doing something wrong, or can you not a customer recipient like that?

    With the existing code, it worked before, but apparently, upgrade to a new version of notifications plugin, broke that.

    Reviewed by edwinsiebel at 2019-09-25 06:43
  • 11. Bug: Encoding in comment action URLs

    The comment actions URLs have encoding in them, which renders the URL invalid.

    {comment_approve_action_url} > https://example.com/wp-admin/comment.php?action=approve&#038;c=834196#wpbody-content

    {comment_trash_action_url} > https://example.com/wp-admin/comment.php?action=trash&#038;c=834196#wpbody-content

    Both are setup as Slack message buttons.

    2019-07-08_15-55-32

    PS Could you please also add comment_reply_link ?

    Reviewed by jphorn at 2019-07-08 13:59
  • 12. Bump async from 2.6.3 to 2.6.4

    Bumps async from 2.6.3 to 2.6.4.

    Changelog

    Sourced from async's changelog.

    v2.6.4

    • Fix potential prototype pollution exploit (#1828)
    Commits
    Maintainer changes

    This version was pushed to npm by hargasinski, a new releaser for async since your current version.


    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    Reviewed by dependabot[bot] at 2022-04-28 20:08
  • 13. Custom merge tag trigger context incomplete

    Bug description

    I have a custom merge tag that runs on the user/registered trigger. Prior to version 8.0.10 the $trigger param passed to the resolver callback contained the proper context (i.e. user ID, user object, etc). However, I believe this commit broke that context, and now user data are null.

    To reproduce

    /**
     * @param \BracketSpace\Notification\Defaults\Trigger\User\UserTrigger $trigger
     */
    add_action('notification/trigger/registered', function ($trigger) {
        $trigger->add_merge_tag(
            new \BracketSpace\Notification\Defaults\MergeTag\UrlTag([
                'slug'     => 'user_password_setup_link_with_redirect',
                'name'     => 'User password setup link with redirect',
                'resolver' => function ($trigger) {
                    $path = 'wp-login.php?action=rp&key='
                        . get_password_reset_key($trigger->user_object) . '&login='
                        . rawurlencode($trigger->user_object->user_login)
                        . '&redirect_to=';
    
                    return network_site_url($path, 'login');
                },
                'group'    => 'User',
            ])
        );
    });
    

    Expected behavior

    The trigger context should contain the registered user's data.

    Environment

    • PHP: 7.4
    • WordPress: 5.9.1
    • Notification plugin: 8.0.10
    Reviewed by timothyjensen at 2022-03-01 20:24
  • 14. (Custom) trigger not sending emails

    I'm using version 7.2.4, and created a custom trigger (with an email carrier). Everything was working fine, the trigger was triggered, and mails where sent.

    After updating to version 8.0.10 and re-working the code I now don't get any mails.

    My code before the update

    Code in "triggers.php"

    class TriggerNotificationUpdateToAll extends \BracketSpace\Notification\Abstracts\Trigger
    {
        public function __construct()
        {
            parent::__construct(
                'my_plugin/manual_trigger',
                'Update an alle schicken'
            );
    
            $this->add_action('trigger_notification_to_all', 10, 2);
            $this->set_group('Support');
            $this->set_description('Triggered with trigger_notification_to_all action.');
        }
    
        public function action()
        {
            // This trigger should always process.
        }
    
        public function merge_tags()
        {
            // This trigger doesn't include any Merge Tags.
        }
    }
    

    Code in function.php

    add_action('notification/init', function () {
        require_once(get_template_directory() . '/resources/includes/notifications/triggers.php');
    });
    
    add_action('notification/elements', function () {
        $custom_trigger_1 = new TriggerNotificationUpdateToAll;
        notification_register_trigger($custom_trigger_1);
    });
    

    My code after the update

    I would like to update to the current version, but I can't get it running.

    New code in "triggers.php", as described here:

    https://docs.bracketspace.com/notification/developer/triggers/custom-trigger

    
    use BracketSpace\Notification\Abstracts\Trigger as AbstractTrigger;
    
    class TriggerNotificationUpdateToAll extends AbstractTrigger 
    {
        public function __construct()
        {
            parent::__construct(
                'my_plugin/manual_trigger',
                'Update an alle schicken'
            );
    
            $this->add_action('trigger_notification_to_all', 10, 2);
            $this->set_group('Support');
            $this->set_description('Triggered with trigger_notification_to_all action.');
        }
    
        public function context()
        {
            // This trigger should always process.
        }
    
        public function merge_tags()
        {
            // This trigger doesn't include any Merge Tags.
        }
    }
    

    New code in function.php

    use BracketSpace\Notification\Register;
    add_action( 'notification/init', function() {
        require_once(get_template_directory() . '/resources/includes/notifications/triggers.php');
        Register::trigger( new TriggerNotificationUpdateToAll() );
    } );
    

    So, the problem is that now there are no mails being sent.

    If I turn notification logging on, then the log shows the notifications, so at least the trigger is triggered ... but, as I wrote, no mails are actually sent out.

    I also tried using a built in trigger - like "Page updated" - but it's the same. The notification shows up in the log, but no mails are sent. (With v7.2.4 and the old code it's working / sending, and with v8.0.10 it's not!)

    What am I missing?

    Environment

    • PHP: 7.4
    • WordPress: 5.9
    Reviewed by mockmeup at 2022-02-15 14:37
  • 15. Bump enshrined/svg-sanitize from 0.14.1 to 0.15.0

    Bumps enshrined/svg-sanitize from 0.14.1 to 0.15.0.

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    Reviewed by dependabot[bot] at 2022-02-15 00:45
  • 16. Password reset trigger fired at user registration

    Bug description

    When I create a new user, he gets the email to activate his account and a link to reset his password.

    To reproduce

    Steps to reproduce the behavior:

    1. Setup the User password reset request and User registration trigger with email as carrier and {user_email} tag as recipient
    2. Create a new user
    3. Get two instead of one mail

    Expected behavior

    Only get the mail from User registration trigger

    Environment

    • PHP: 7.4
    • WordPress: 5.9
    • Notification plugin: 8.0.10
    Reviewed by tomo2403 at 2022-02-14 16:36
Google Chat - Laravel Notification Channel
 Google Chat - Laravel Notification Channel

Google Chat - Laravel Notification Channel This package makes it easy to send notifications using Google Chat , (formerly known as Hangouts Chat) with

May 4, 2022
Livewire Package to display Toast Notification based on TALL Stack.
Livewire Package to display Toast Notification based on TALL Stack.

livewire-toast Livewire Package to display Toast Notification based on TALL Stack. Requirements Make sure that Livewire is installed properly on your

Mar 28, 2022
Multiple channels of laravel exception notification(DingTalk、FeiShu、ServerChan、WeWork、XiZhi). - 多种通道的 laravel 异常通知(钉钉群机器人、飞书群机器人、Server 酱、企业微信群机器人、息知)。
Multiple channels of laravel exception notification(DingTalk、FeiShu、ServerChan、WeWork、XiZhi). - 多种通道的 laravel 异常通知(钉钉群机器人、飞书群机器人、Server 酱、企业微信群机器人、息知)。

laravel-exception-notify 简体中文 | ENGLISH Multiple channels of laravel exception notification(DingTalk、FeiShu、ServerChan、WeWork、XiZhi). - 多种通道的 laravel

May 27, 2022
ApnsPHP: Apple Push Notification & Feedback Provider
ApnsPHP: Apple Push Notification & Feedback Provider

ApnsPHP: Apple Push Notification & Feedback Provider A full set of open source PHP classes to interact with the Apple Push Notification service for th

Apr 17, 2022
Laravel SMS Notification Channel

Laravel SMS Notification Channel Installation composer require guangda/laravel-sms-notification-channel env 配置 SMS_PROVIDER=yunpian SMS_SIGNATURE=【签名

Dec 29, 2021
Slack notification for Laravel as it should be. Easy, fast, simple and highly testable.
Slack notification for Laravel as it should be. Easy, fast, simple and highly testable.

Based on illuminate/mail About Laravel Slack Slack notification for Laravel as it should be. Easy, fast, simple and highly testable. Since it uses On-

May 13, 2022
A Toast notification library for the Laravel TALL stack.
A Toast notification library for the Laravel TALL stack.

A Toast notification library for the Laravel TALL stack. You can push notifications from the backend or frontend to render customizable toasts with almost zero footprint on the published CSS/JS ????

May 20, 2022
A filterable git commit summary notification mailer
A filterable git commit summary notification mailer

Git commit notification A symfony application to allow receiving commit notification for all commits in a certain time period. Features: Receive one m

Jan 5, 2022
Bootstrap 4 & 5 replacement for jGrowl notification
Bootstrap 4 & 5 replacement for jGrowl notification

XoopsGrowl module for XOOPS CMS 2.5.11+ XoopsGrowl is a module for XOOPS CMS to configure an alternative to the jGrowl notification using Bootstrap Al

Oct 28, 2021
Bootstrap 4 & 5 replacement for jGrowl notification
Bootstrap 4 & 5 replacement for jGrowl notification

XoopsGrowl module for XOOPS CMS 2.5.11+ XoopsGrowl is a module for XOOPS CMS to configure an alternative to the jGrowl notification using Bootstrap Al

Oct 24, 2021
Lark Notification Channel for laravel.

Lark notifications channel for Laravel This package makes it easy to send Lark using the Laravel notification system. Supports 5.5+, 6.x, 7.x and 8.x.

Nov 3, 2021
AmaranJS stylish notification for your laravel application.

AmaranJS Laravel 5 Package AmaranJS L5 package is a Laravel wrapper for my jquery plugin AmaranJS.You can create easy and stylish notifications with A

Oct 3, 2019
Our Laravel Sendgrid Notification package

laravel-sendgrid-notification-channel Laravel Sendgrid Notification channel Installation To get started, you need to require this package: composer re

Feb 3, 2022
Lara-Izitoast : Laravel Notification Package
 Lara-Izitoast : Laravel Notification Package

Lara-Izitoast : Laravel Notification Package This is a laravel notification wrapper build with http://izitoast.marcelodolce.com javascript library. Ho

Jan 4, 2022
Notification package for Laravel

Package is looking for maintainers Please contact me if interested. Notification package for Laravel4 / Laravel5 A simple notification management pack

Dec 26, 2021
An SMS notification channel for the PHP framework Laravel.

Laravel SMS notification channel An SMS notification channel for the PHP framework Laravel. Supported SMS gateways: 46elks Cellsynt Telenor SMS Pro Tw

Jan 22, 2022
Laravel notification manager

Easily manage notifications and notification subscriptions in your Laravel application.

Apr 6, 2022
Api.video-wordpress-plugin - The official api.video plugin for WordPress
Api.video-wordpress-plugin - The official api.video plugin for WordPress

api.video WordPress Plugin api.video is the video infrastructure for product builders. Lightning fast video APIs for integrating, scaling, and managin

Mar 2, 2022
If you are beginner in WordPress plugin development or if you want to develop your own store product plugin you use this plugin
If you are beginner in WordPress plugin development or if you want to develop your own store product plugin you use this plugin

hirwa-products-plugin If you are beginner in WordPress plugin development or if you want to develop your own store product plugin you use this plugin

Nov 25, 2021
@Authy notification channel for @Laravel, with the ability to send in-app, sms, and call verification tokens.
@Authy notification channel for @Laravel, with the ability to send in-app, sms, and call verification tokens.

Authy Notification Channel for Laravel Authy notification channel for Laravel, with the ability to send in-app, sms, and call verification tokens. Tab

Feb 14, 2022