LogoLogo
WordPress.orgExtensionsSupport
Version 6
Version 6
  • Notification – Custom Notifications and Alerts for WordPress
  • Known issues
  • User guide
    • How Notification plugin works
    • Who can use this plugin
    • How to create Notifications
    • Custom Post Type support
    • How to escape { character
    • Background processing
    • Troubleshooting
    • How to setup different FROM address for different Notifications
  • Developer
    • General
      • Plugin loading chain
      • Extension possibilities
      • Creating an extension
      • Bundling Notification plugin
      • White label mode
    • Notifications
      • Suppressing the Notification
      • JSON synchronization
      • Programmatic Notifications
    • Triggers
      • List of all default Triggers
      • Custom Trigger
      • Enable support for non-public Custom Post Type
      • Adding Merge Tags to existing Triggers
      • Postponing the Trigger action
      • Delaying Trigger execution with Cron
    • Carriers
      • Suppressing the Carrier
    • Snippets
      • General
        • Automatic Trigger testing
        • Allow other roles to edit Notifications
      • Triggers
        • Post
        • User
      • Integations
        • WP All Import
        • MemberPress
        • Gutenberg
  • Extensions
    • Installation
    • Planned extensions
    • 3rd Party Extensions
    • Custom Fields
    • Scheduled Triggers
Powered by GitBook
On this page
  • Multiple exactly the same Notifications
  • Gutenberg and custom field
  • Pods custom fields

Was this helpful?

Known issues

PreviousNotification – Custom Notifications and Alerts for WordPressNextHow Notification plugin works

Last updated 5 years ago

Was this helpful?

Multiple exactly the same Notifications

Problem occurs when Triggers gets executed multiple times during the same request, ie. when you are adding multiple posts via a loop.

This is related to the Notification plugin internal architecture and postponing feature. The plugin doesn't keep the action context and this is why so many same notifications is sent.

A quick fix to prevent that is to use below filter. Please note that if you are saving custom fields, they may not get recognized.

add_filter( 'notification/integration/custom_fields/should_postpone_save_post', '__return_false' );

Gutenberg and custom field

When using Gutenberg it's not possible to get every post information AND custom fields at the same time. Everything is saved separately in separate AJAX requests and there's no way we can access all the updated data at once.

You should enable the to get rid of this issue.

Pods custom fields

Custom fields saved via Pods framework doesn't get recognized by the Notification plugin thus cannot be used with the Custom Fields extension.

You can try to enable the to get rid of this issue.

Background processing
Background processing