• Resolved krazydave

    (@krazydave)


    Just installed this on an up-to-date site and this error pops up.

    Postman: wp_mail has been declared by another plugin or theme, so you won’t be able to use Postman until the conflict is resolved.
    More info that may help – /home/xxxxxxx/public_html/wp-includes/pluggable.php:173

    I’ve searched and found that it could be a plugin conflict, however, the error remains even if all plugins are deactivated except for Post SMTP.

Viewing 3 replies - 16 through 18 (of 18 total)
  • Hi yahudah,

    I have actually the same problem with a premium membership plugin called “ARMembers”. I have inspected the whole plugin’s directory, and there are 15 entries with:

    if (!function_exists('wp_get_current_user')) {
                    include(ABSPATH . "wp-includes/pluggable.php");
                }

    You said this is a bad practice. Ok. But what can I say to the devs in order to do it differently? Just wrap this code inside a proper hook? But which one?

    Regards.

    @moxymore

    Hard to say without all of the code.
    You can disable my plugin, but I’m telling you as a friend – if I was you, I would search for another plugin.

    funnelKit GO plugin gives the same error. For those with this problem and with that one installed.

    Cheers!

Viewing 3 replies - 16 through 18 (of 18 total)
  • The topic ‘Postman: wp_mail has been declared by another plugin or theme’ is closed to new replies.