And one more; when I cycle deactivate / activate the plugin all settings are forgotten. It looks like the setting were never recorded anywhere.
Matej
Plugin Contributor
rajuru
(@rajuru)
Hello @mkurent
I’m one of the developers of this plugin. I’ll try to help you here.
For issue #1
This behavior of the plugin sounds weird. I just tried to reproduce this issue and could not. What’s your WordPress & PHP version? I’ll test in those versions if they’re officially supported.
Issue # 2:
Can you send us the whole debug information (you’ll get that after check on the checkbox in the test area). You can send this to our support (support at sparkpost com).
May be some it’s affected by other plugins. Also
– are you running it in localhost?
– did you enabled sparkpost (check on the top checkbox)
issue # 3:
That’s intentional. The plugin cleans whatever data it created :).
Thanks
Hi there:
PHP Version 5.5.9-1ubuntu4.14
Wordpress 4.x
The whole debug info is what I have already wrote: Could not instantiate mail function.
Host is DigitalOcean.
And yes, I have enabled sparkpost.
We are doing migration from Mandrill and I taught that this would be much more simple.
Matej
Update: I have bee checking what is actually written in the database and the from_email filed is correct.
Strange enough, on display it gets overwritten by user name. I am using Safari in it looks like Safari is treating this field as password or something like this.
But still I cannot send mail. The same debug info persist.
Matej
Plugin Contributor
rajuru
(@rajuru)
Hello @mkurent
I just tried using the plugin in Safari and I could not reproduced the error you’ve mentioned.
Also, I tried using PHP5.6 and didn’t get any issue with test mail. Do you know specific (full) version of your WordPress?
Also it’ll be helpful if there is any other error logged in your system. Unfortunately, these information don’t seem to be enough to understand what’s really going on.
Does the plugin work if you select SMTP?
Thanks
Hi @rajuru
WP is 4.2.2
The problem with “Could not instantiate mail function.” is (and this is my guess) since on the server we do not have SMTP server. We are using Mandrill API and there is no need to have SMTP server.
This error is generated by PHPMailer when wants to connect to SMTP which is not existing nor needed if you using HTTP API.
Look here: https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
In order to regenerate this error you should disable SMTP server and use API. I am sure you will see the same problem.
The Safari problem is caused by Safari autofill. In that particular field Safari autofills WordPress username.
Matej
Plugin Contributor
rajuru
(@rajuru)
Ok, that help. We don’t need SMTP when you’re using our HTTP API. Can you again make sure you’ve selected HTTP API (instead of SMTP). If so, I’ll test on a similar environment.
Thanks
Yes. From the drop-down it was selected HTTP API.
Matej
And I have also checked in the database, how this option is registered. Here is a snippet:
s:16:"enable_sparkpost";i:1;s:14:"sending_method";s:3:"api";
Matej
Plugin Contributor
rajuru
(@rajuru)
Hello @mkurent
I could not reproduce this issue the way you’ve described. I just launched DO instance and tested this out. I’ve removed mail programs too.
Both HTTP and SMTP works fine. However, if I do not enable the plugin and I try test email, I get the above error.
Can you please post a screenshot of your settings page? (you should hide sensitive information from the screenshot). Also I will suggest, Re-activate (deactivate and then activate again) the plugin and try. Thanks
Hi Rajuru,
in this forum I cannot post a screen shot. Can we continue a discussion over email and later post a solution here, for other with a similar trouble.
Matej
Plugin Contributor
rajuru
(@rajuru)
Plugin Contributor
rajuru
(@rajuru)
As you’ve opened an issue in github, I’m closing this one. Thanks
