Says wp_mail already declared

  • Resolved pnaw10

    (@pnaw10)


    5 years, 11 months ago

    Hello, I suddenly started seeing the following error on my WordPress dashboard:

    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/petert11/public_html/wp-includes/pluggable.php:173

    As you know, pluggable.php line 173 is just where WordPress declares wp_mail to be a pluggable function, so that was no help in finding the cause of this problem.

    I downloaded my entire plugins directory to my computer and had Notepad++ scan everything for any instance of function wp_mail() and the only one that came up was the one in the Post SMTP plugin. None of my other plugins have it, and I haven’t changed themes at all lately.

    Diagnostic test output:

    HostName: ecngx245.inmotionhosting.com
    OS: Linux ecngx245.inmotionhosting.com 3.10.0-714.10.2.lve1.5.19.7.el7.x86_64 #1 SMP Fri Sep 28 08:37:09 EDT 2018 x86_64
    PHP: Linux 7.1.23 en_US.UTF-8
    PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=Yes, zlib_encode=Yes
    WordPress: 4.9.8 en_US UTF-8
    WordPress Theme: Blox Theme
    WordPress Plugins: VaultPress, Redux Framework, Ivory Search, Admin Custom Login, Akismet Anti-Spam, Architect – a DIY content block builder (Premium), BoldGrid Gallery, BoldGrid Inspirations, BoldGrid Staging, Duplicate Post, Easy Shortcode Buttons, Formidable Forms Pro, Formidable Forms, HTML5 Responsive FAQ, Inline Google Spreadsheet Viewer, Jetpack by WordPress.com, Page Links To, Post and Page Builder Premium, Post and Page Builder, Post SMTP, ShiftNav Pro – Responsive Mobile Menu, NextScripts: Social Networks Auto-Poster, Tabby Responsive Tabs, Yoast SEO, WP Maintenance Mode, WPS Hide Login
    WordPress wp_mail Owner: /home/petert11/public_html/wp-includes/pluggable.php
    WordPress wp_mail Filter(s): wp_staticize_emoji_for_email
    Postman: 1.9.5
    Postman Sender Domain (Envelope|Message): peterthedj.com | peterthedj.com
    Postman Prevent Message Sender Override (Email|Name): No | No
    Postman Active Transport: SMTP (smtp:tls:oauth2://smtp.gmail.com:587)
    Postman Active Transport Status (Ready|Connected): Yes | Yes
    Postman Deliveries (Success|Fail): 305 | 7

    I can still get email from contact form submissions, but the body of the email is just the raw HTML code from the form results, rather than rendering the HTML as it did before. And they aren’t showing up in the Post SMTP log.

    I’m stumped as to what could be causing this error, I can’t find anything else that is declaring the wp_mail function.

    • This topic was modified 5 years, 11 months ago by pnaw10.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter pnaw10

    (@pnaw10)

    Update: I wanted to see if deactivating and then reactivating the plugin would resolve the error. I deactivated, and the error is still showing on my dashboard. How and why would an error from an inactive plugin be able to appear on my dashboard?

    Hi,

    Please search for pluggable.php in your plugins folder.

    Thread Starter pnaw10

    (@pnaw10)

    There is no other pluggable.php in the plugins folder or any of its subfolders.

    Not the file, search for text refference in other plugins.

    You have a plugin the include inside it that file by doing something like:

    require_once ABSPATH . '/wp-includes/pluggable.php';

    The above was just an example so just search inside the files for the string: pluggable.php.

    Thread Starter pnaw10

    (@pnaw10)

    Originally switched to another SMTP plugin, as that was easier than trying to continue troubleshooting this one — at least for the time being.

    Since then, I’ve switched back to Post SMTP and everything is working fine once again.

    In the meantime, I had disabled a suite of theme-design plugins (BoldGrid) that I had recently installed because a premium membership is “included” with my new hosting plan. Although BoldGrid should have NOTHING to do with sending mail, my guess is that one or more of BoldGrid’s six (yes, six!) plugins may have been the cuplrit. When I searched all of the files in the plugins folder for instances of pluggable.php most if not all of the BoldGrid plugins had references to it.

    Several other plugins also made mention of pluggable.php but those were all plugins I’ve had for quite some time.

    I didn’t bother to further inspect the code of the BoldGrid plugin files, because after trying it, I think BoldGrid is a pile of garbage. Since I don’t intend to use it and Post SMTP appears to be working properly again, I’m not concerned with pinpointing the exact source of the cause… but wanted to provide an update in case anyone else encounters similar conflicts in the future. If so, hopefully this can be a starting point for such a person.

    The other SMTP plugin I was using in the interim was OK as well, but I found it lacking in a few ways. Particularly, it was lacking a log feature. I like that Post SMTP has logs so I can “audit” email generated by my website versus what actually appeared in my inbox. Not that I’ve ever had anything disappear en route, but it’s good to know I can always check just to be sure.

    Thank you for your hard work and dedication to this project.

    Thank you for your kind words and taking the time writing such amazing and detaild response.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Says wp_mail already declared’ is closed to new replies.