Have you installed or updated another plugin or theme since then?
It sounds like another plugin is changing the order of the WordPress bootstrap. I remember an issue like this before where another plugin was directly loading a core WordPress file, so the WordPress API hooks that Postman needs to use never got fired.
If you keep deactivating plugins until the message goes away, you should be able to find the culprit. Please let me know when you do.
Yes i have installed a few…but i have tried deactivating them but did not work…i also checked the pluggable.php file but there was no mention of any plugin…shall i try reinstalling the postman smtp plugin ??
i also checked the pluggable.php file but there was no mention of any plugin
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.
shall i try reinstalling the postman smtp plugin ??
I don’t believe reinstalling Postman will change anything.
Try: deactivating all plugins, every single one, and then switching to the default theme. Does the error go away?
Perhaps it’s your theme.
Okay..let me try…see if it works…
I remembered which plugin it was where I saw this before… PopUp by Supsystic…
https://wordpress.org/support/topic/email-problem-14?replies=3
I deactivated several plugins…it is working now
See if you can narrow it down to a single plugin?
yeah on it…installing them one by one
Ugh… Code Canyon. You could try reporting the error to them and see how receptive the author is.
Because it’s paid-only I can’t even download the code to advise you what’s wrong or if it’s dangerous. If you want to send it to me privately, I can take a look.
I sent you the plugin. Please check and let me know if it was dangerous from the security point of view
I found the problem. It’s the same problem I found in PopUp by Subsystic.
On line two of di-aiosc/class/class.user.php
if(!function_exists('wp_get_current_user')) {
require_once(ABSPATH . "wp-includes/pluggable.php");
}
This is causing the error message in Postman. I will contact the author for you, but they may or may not care what I say. You might have to choose between AIO Support Centre and Postman.
I looked at all the core files being called directly by this plugin and I don’t see anything else that might compromise security.
Thanks…i will obviously choose postman smtp…your service and support both are great:)
Thank-you, that’s very kind š Here is the message I sent:
This code in class.user.php:
<?php
if(!function_exists('wp_get_current_user')) {
require_once(ABSPATH . "wp-includes/pluggable.php");
}
Loads pluggable.php before WordPress loads it, i.e. before the init hook. This causes problems with other plugins, such as BBPress:
The current user is being initialized without using $wp->init().
And Postman SMTP:
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.
Would you please remove the call to pluggable.php from this file. Accessing the current user should wait until the init hook. Please see http://codex.wordpress.org/Plugin_API/Action_Reference.
Thank You…I hope they will resolve the problem soon, like you did š
