wp-mail conflict

  • Resolved karelles

    (@karelles)


    9 years ago

    I’ve been getting the message at the top of my admin window:
    “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.”
    I found some references in the support files and have run the Postman diagnostics, discovering that the owner of wp-mail is pluggable.php
    So I did a search (the search in the support request didn’t work so I did a backup of the plugins folder, downloaded it and searched the contents locally). I think I found the culprit: Enhanced Media Library Pro. Turning it off turns off the message.
    Unfortunately I can’t do without that plugin.
    Interestingly email (google business) still seems to be going out on the site – according to the logs.
    So,
    1) how worrisome is this?
    2) how do I get 2 valued plugins to play nice with each other?

    https://www.ads-software.com/plugins/postman-smtp/

Viewing 6 replies - 1 through 6 (of 6 total)
  • webbistro

    (@webbistro)

    Hello all,

    I am Nadia, an author of the Enhanced Media Library. Actually, EML has nothing to do with wp_mail, but please let me know if I can be of help with this issue in any way.

    Best,
    -Nadia

    Thread Starter karelles

    (@karelles)

    Hi Nadia,

    Thanks for your quick reply.

    I had read the support request on this page: https://www.ads-software.com/support/topic/plugin-not-working-declared-by-another-plugin?replies=20
    about the wp-mail conflict and followed the directions re: finding that text in another plug-in, suggesting that that plugin might be conflicting. I don’t think it actually has to do with EML having anything to do with wp-mail, but pluggable.php is loaded before postman as per the following from that support thread:
    “pluggable.php has a function called wp_mail. When Postman loads first, as it should, Postman’s wp_mail is used and pluggable.php’s wp_mail is skipped. But, if Postman is not installed, pluggable.php’s wp_mail is used. Your problem is that pluggable.php is loaded before Postman. This is incorrect. It means something is messing with the WordPress bootstrap, and could cause other problems like weird bugs or security holes. Plugins/themes are not supposed to directly call core files. That’s what the API is for.”

    I do know that when I disable EML pro, the error message goes away.

    Again, thanks for your (surprising) attention to this problem.

    webbistro

    (@webbistro)

    Hi @karelles,

    Thank you for your research! EML includes pluggable.php, some tasks EML solves just cannot be solved because there is no API functions for them, so it may cause the issue. It’s not good I know, it should have led to problems one fine morning.

    I will take a look at the issue tomorrow, it’s a bit late right now at my corner of the world. It also may take some time to find a solution. I will keep you posted.

    I just have mention notifications turned on ??

    Best,
    -Nadia

    Plugin Author Jason Hendriks

    (@jasonhendriks)

    @webbistro, IMO this is dangerous. I’ve been asked by the core team not to discuss specifics on the forum. But if you can tell me what function you needed from pluggable.php, I’m sure I could help you figure out how to get access to it correctly.

    @karelles, the only fix is for Nadia to update her plugin.

    @ipstenu one more example.

    webbistro

    (@webbistro)

    Hi Jason,

    Thank you for your attention. We are working on it right now. I will let you know if we need assistance with it.

    For everyone interested: it is going to be fixed in a day or two.

    Best,
    -Nadia

    webbistro

    (@webbistro)

    Hi all,

    EML 2.2 without pluggable.php in just launched.

    Best,
    -Nadia

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘wp-mail conflict’ is closed to new replies.