| 开发者 |
notification
bracketspace Kubitomakita tomaszadamowicz insejn mateuszgbiorczyk |
|---|---|
| 更新时间 | 2025年9月5日 21:19 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.8 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
do_action( 'my_plugin_doing_awesome_thing' ) you can create a Trigger out of it.
This allows you to use the Notification plugin as a notification system in your own plugin or theme. How? Well, because of two things:
load.php file. A function known from Advanced Custom Fields plugin.{home_url}{site_title}{site_tagline}{site_theme_name}{site_theme_version}{wordpress_version}{admin_email}{trigger_name}{trigger_slug}load.php file. It will figure out if it's loaded from theme or from plugin.
See the detailed guideIt's not needed to install 3rd-party plugins to catch your emails or other notifications. The Notification plugin comes with a logger which you can activate in the settings and see all the notification configuration parameters.
Is your WordPress sending any emails at all? The best way to test it is to try to reset your password. If you don't get any email than there's something wrong with your server configuration. You could use any SMTP plugin to fix that. You can also try to activate the debug log in plugin settings to see if the email is triggered.
Ofcourse it is! We are trying to make both parties happy - the Users and Developers. Users got their intuitive and beautiful panel in WordPress Admin and Developers got an awesome API by which they can extend the Notification plugin. So it doesn't matter if you don't have any coding skills, they are not required to setup the notifications with this plugin.
The Notification plugin works very similar to BNFW but it has better codebase and interface. You can read the full comparison in the Notification vs Better Notifications for WordPress article.
With register_trigger() function. See the detailed guide
You can write a merge tag by yourself or go with a no-brainer Custom Fields extension.
You can control when exactly the notification is sending with the Conditionals extension.
Yes, just include filter-id:some-value in the Recipient value (using the Email/Merge tag type with the Email carrier), then return your recipient list from the notification/recipient/email/some-value filter.
Yes, you can. See the detailed guide
The plugin is capable and it can send milions of emails, but probably your server is not. To send thousands of emails at once we'd suggest using SendGrid or Mailgun extensions which were designed to support high volume emails in a single API call. When using SMTP it's nearly impossible to send more than a dozen emails at once due to timeouts.
Yes, just activate the debug log in the DEBUGGING section of the plugin settings. All notifications will be caught into log visible only to you.
Yes! We're offering a custom plugin development services. Feel free to contact us to find out how we can help you.
$trigger->{$post_type} has been replaced with static prop $trigger->post.property_name attribute rather than post_type to set trigger property used by resolvers.notification/data/save and notification/data/save/after now pass Core\Notification instance in the first param instead of the WordPress adapter instance.BracketSpace\Notification\Defaults\ changed to BracketSpace\Notification\Repository\BracketSpace\Notification\Abstracts\Carrier changed to BracketSpace\Notification\Repository\Carrier\BaseCarrierBracketSpace\Notification\Abstracts\Field changed to BracketSpace\Notification\Repository\Field\BaseFieldBracketSpace\Notification\Abstracts\MergeTag changed to BracketSpace\Notification\Repository\MergeTag\BaseMergeTagBracketSpace\Notification\Abstracts\Recipient changed to BracketSpace\Notification\Repository\Recipient\BaseRecipientBracketSpace\Notification\Abstracts\Resolver changed to BracketSpace\Notification\Repository\Resolver\BaseResolverBracketSpace\Notification\Abstracts\Trigger changed to BracketSpace\Notification\Repository\Trigger\BaseTrigger
Hook depracations:
notification/data/save/after, use notification/data/saved
Function and method deprecations:
BracketSpace\Notification\Admin\PostType::getAllNotifications(), use BracketSpace\Notification\Database\NotificationDatabaseService::getAll()
notification_convert_data(), use BracketSpace\Notification\Core\Notification::from('array', $array)notification_register_settings(), use the notification/settings/register action directlynotification_get_settings(), use \Notification::component('settings')->getSettings()notification_update_setting(), use \Notification::component('settings')->updateSetting()notification_get_setting(), use \Notification::component('settings')->getSetting()notification_adapt(), use BracketSpace\Notification\Core\Notification::to()notification_adapt_from(), use BracketSpace\Notification\Core\Notification::from()notification_swap_adapter(), use ::from() and ::to() methods on the BracketSpace\Notification\Core\Notification classnotification_add(), use BracketSpace\Notification\Register::notification()notification_log(), use BracketSpace\Notification\Core\Debugger::log()notification(), use BracketSpace\Notification\Register::notificationFromArray()
Removed deprecated hooks:
notitication/admin/notifications/pre, use notification/admin/carriers/pre
notitication/admin/notifications, use notification/admin/carriersnotification/email/use_html_mime, use notification/carrier/email/use_html_mimenotification/email/recipients, use notification/carrier/email/recipientsnotification/email/subject, use notification/carrier/email/subjectnotification/email/message/pre, use notification/carrier/email/message/prenotification/email/message/use_autop, use notification/carrier/email/message/use_autopnotification/email/message, use notification/carrier/email/messagenotification/email/headers, use notification/carrier/email/headersnotification/email/attachments, use notification/carrier/email/attachmentsnotification/webhook/args, use notification/carrier/webhook/argsnotification/webhook/args/{$type}, use notification/carrier/webhook/args/{$type}notification/notification/form_fields/values, use notification/carrier/fields/values
Full changelog
BracketSpace\Notification\Defaults\ to BracketSpace\Notification\Repository\.Date, DateTime and Time) now requires timestamp argument to be callable.property_name in all Merge Tags.