Login via InfiniteWP turns plugin off

Sure,

No reason Infinite WP should override this function.

Tell Infinite WP devs about this conflict, ask them not to redefine wp_mail , as it render other plugins inoperable.

It includes “pluggable.php” which defines wp_mail(), it does not customise the wp_mail function.

So no plugin can include “pluggable.php”?

There is a reason why pluggable.php is loaded after the plugins.

Manually including pluggable.php in a plugin kills all pluggable functionnalities, and is a bad practice.

fyi, ManageWP did this very same thing too, 2 years ago.
Then fixed it quickly, as it was causing other conflicts with other plugins, not just the email ones, not just wp_ses.

Hi Sylvain Deaure,
This is Babu from InfiniteWP Development Team. I acknowledge that having the require/include pluggable.php in our plugin is a bad practice. We will make changes to the code blocks where we currently use the pluggable functions.
I have installed both the WP SES plugin and the InfiniteWP Client plugin on a WP Install to see if the issue could be replicated. The iwp-client does not conflict with your code in the first place (We will make changes to pluggable.php). Even after deletion of iwp client plugin, WP-SES gives the same wp_mail override by another plugin error. There are no other plugins activated on my WP install when I got this error from WP-SES log file. Kindly have a check on your code and see if this can be fixed from your side ??
Logs from your plugin :

1464592880	Start Logging
1464592899	ERROR	wp_mail override by another plugin !!
1464592899	Then deactivating plugin
1464592899	wp_mail already defined in \htdocs\wpsite1\wordpress\wp-includes\pluggable.php

Let me know if you need more details on the issue. I will be more than glad to help you recreate the issue.

Hi Babu, thanks for taking care.

The warning is in response to this call :

function_exists(‘wp_mail’)

during plugin load.

No way I can do it sooner, can’t see how to fix from my side.
Hacking the plugin load order could help, but may conflict with others. Doesn’t seems like a good idea.

In your case, logs show pluggable.php as the source of the function definition. This means that pluggable.php was included or required at that time.

I have to admit I don’t understand why this file would still be included after iwp client deletion.
Wordpress by itself only requires it after plugins are loaded.

A backtrace log in pluggable.php could tell from where it has been required.

Thanks for the help