Priority Support

Your Account

Cart total: £0.00

Known Compatibility Issues

This page is designed to give you a heads-up on any known compatibility issues, hopefully before you run into them. I’ll update this page by adding and removing information where appropriate.

Social Plugins

Some users have reported multiple emails being sent out when used in conjunction with a plugin that shares posts with social networks. This is not an issue with BNFW. Any plugins that I find that exhibit this behaviour are listed below for convenience:

Membership / Profile Plugins

The Profile Builder or Restrict Content Pro plugins aren’t compatible with the “Lost Password – For User” notifications as they override the way the password reset happens in WordPress and are adding their own custom implementations.

Members, whilst an incredibly popular plugin, and one I’d love to support, lacks hooks for a lot of things. As such, it’s very difficult to support it. If you need to add User Roles / Capabilities, I recommend setting them up in Members, and then de-activating (but not removing) the plugin. Any roles / capabilities you have created should remain and BNFW should function as normal.

Gravity Forms and Plugins with Front-end Forms

Whilst these mostly work without issue, there have been reports of duplicate notifications occurring or notifications not triggering at all when using a plugin that utilises a front-end form for user registration or adding new posts or updating old ones. A notable example is Gravity Forms’ User Registration add-on, which is a complicated plugin to support.

Import Plugins

The Cimy User Manager plugin doesn’t save first or last names on initial import and seems to do it afterwards instead. As such, certain shortcodes, such as [global_user_firstname] do not output anything when BNFW sends out new user registration notifications. Users have also experienced issues with other notifications when this plugin is used in conjunction with BNFW.

APIs

Any plugin that posts via an external API or if you do anything using the WP REST API most likely won’t trigger notifications and will fail silently. This is because this interface doesn’t provide details of the current user which BNFW relies on to trigger a lot of different notifications.