Better Notifications for WP plugin review and common issues

BNFW sends notifications via WordPress wp_mail(). Verify: (1) the notification is enabled (toggle switch in BNFW → Notifications → [notification]); (2) the trigger event is occurring correctly — test the specific event (submit a new comment, register a user) and verify BNFW fires; (3) WordPress email is functional — use WP Mail SMTP test email to confirm; (4) check spam folders for the notification recipient; (5) the recipient email address in the notification configuration is correct; (6) configure WP Mail SMTP with a proper SMTP service for reliable delivery of BNFW notifications.

Shortcode values that do not replace indicate: (1) the shortcode is not valid for the notification type — some shortcodes are context-specific (e.g., [post_title] only works in post-related notification events, not in user registration events); (2) the shortcode has a typo — shortcodes are case-sensitive; (3) verify the shortcode in BNFW’s documentation for the specific notification event; (4) the event may not have the expected data available — for custom events, verify the shortcode’s data is populated at the time of notification.

Duplicate notifications occur when: (1) BNFW has two notification rules configured for the same event — check BNFW → Notifications for duplicate rules targeting the same event and recipient; (2) BNFW’s notification and the original WordPress core notification are both sending for the same event — in BNFW settings, check “Disable default WordPress notifications” if you want BNFW to fully replace (not supplement) the default notifications; (3) another notification plugin is also configured for the same event.

In BNFW → Add New Notification, select the Notification Type → Post Published. Set the recipient to “Author” (using the [author_email] shortcode or the “Post Author” recipient option). Configure the email subject (e.g., “Your post [post_title] has been published!”) and body with dynamic content: “Hi [author_display_name], your post [post_title] is now live at [post_permalink].” This notification fires whenever any post is published. For specific post types only, configure the Post Type filter in the notification settings.

In BNFW → Add New Notification, select Notification Type → New User Registered. In the recipient configuration, add a specific email address (e.g., hr@company.com) as a custom recipient. Configure a notification template with the new user’s details: [user_name], [user_email], [user_role], [user_registered_date]. This creates an additional notification beyond WordPress’s default new user admin email, allowing department-specific teams to be informed of new registrations without giving them WordPress admin access.

BNFW can supplement but not easily replace WooCommerce’s transaction emails (order confirmation, shipping notification, etc.). WooCommerce’s own email system is separate and customizable through WooCommerce → Settings → Emails. BNFW can add additional WordPress-level notifications for WooCommerce events (new order alert to staff, product low stock alert) but works alongside WooCommerce’s own notification system rather than replacing it. For complete WooCommerce email customization (appearance, content), dedicated WooCommerce email plugins are more appropriate.

HTML email rendering in BNFW requires the Pro version. The free version sends notifications as plain text (readable but not styled). With Pro, the email body accepts standard HTML tags and inline CSS for styled emails. For HTML emails to render correctly across email clients, use table-based HTML layout (avoiding CSS grid or flexbox which most email clients do not support) and inline styles. Test HTML emails across email clients using a tool like Litmus or Email on Acid.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.