This topic contains 5 replies, has 3 voices, and was last updated by V K 1 year ago.
January 2, 2017 at 1:59 pm #11524
Version 2.35 introduces a new call to pluggable.php which breaks Postman (and probably any other plugin that uses wp_mail):
“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”
Please see the end of this thread on how to fix it:
VKJanuary 3, 2017 at 1:26 am #11528
Was the prior version of the plugin working for you, or is this a new installation?
We remain at your service.January 3, 2017 at 9:30 am #11531
Yes, the previous version does not have that line related to pluggable-php in the code. I downgraded immediately because I need to have email sending working. From the thread I linked to:
“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.”
VKJanuary 6, 2017 at 4:25 pm #11545
I have this same issue, exactly.January 7, 2017 at 2:35 pm #11549
Check the newest update, and advise if you have any further issue.
We remain at your service.January 7, 2017 at 11:30 pm #11550
Unfortunately version 2.36 still causes the same error message. It doesn’t seem to be an issue with double include, it is the include itself. Please do not reference pluggable.php directly: Here is another thread about fixing this: