rajuru

@mikeharris @edugaurav Thanks for that info as it’ll be helpful to reproduce. We’ve released a patch which should not attempt db changes unless you’ve enabled email logging (you may still get same error if you’ve explicitly enabled it from settings page.).

However, just wanted to point out that, it might have been just working but multisite support is not really implemented/tested. Please track this issue https://github.com/SparkPost/wordpress-sparkpost/issues/99.

We’ll appreciate any contribution regarding multisite or any other improvements.

@edugaurav
This article explains about the error https://www.safaribooksonline.com/blog/2012/11/06/avoiding-too-many-keys-in-mysql/

My understanding of the error is like:
At first the table is created fine but the following line failed
update_option('sp_db_version', $this->db_version);

So, it’s trying to install the table each time. But because table already exists dbDelta tries to alter the table which is trying to create index on id column.

We’ll investigate this more and add a solution.

However, I guess we should also have done something in the plugin; which is not trying to install db if email logging is enabled. In that case you could just disable that option (as a temporary workaround).

Solution path:
– Please use older version for now
– We’ll make a patch soon to not try to install db if email logging is not enabled
– Fix the actual problem

@joelworsham
As the test email works, I’m suspecting there might be other plugins intercepting your password reset. Can you check if you’ve other plugins that may possibly do it?

Also, if you’ve enabled email logging in SparkPost plugin, please check whether something is useful there.

@edugaurav
Can you tell me which db server you’re using and other info like engine?

Yes that runs on load of plugin but should not create table if it already exists.

Thanks

@spadilla
Being this is WordPress plugin support forum, we’re unable to provide anything not related to (functionalities of) the plugin. If you’ve questions regarding sales/service and other non-plugin related aspect, please contact SparkPost directly.

At this point I will suggest you do some profiling to find out which step exactly taking up your time.

That’s great to hear.

Check with your host if it’s causing the slowness at origination level.

Regardless, HTTP API will be faster (at normal circumstances) and I recommend you to use it.

• This reply was modified 7 years, 1 month ago by rajuru.

That’s so cool. Thanks for making it. Here are a few suggestions:

– Try sending a test mail using the plugin and see if it still taking long.
– Try using HTTP API mailer (you’ll need to add appropriate permissions to your API Key though).
– Also I see you’re using port 2525. Try default SMTP port 587 if that’s unblocked in your host.

Please get back to us if any of this doesn’t help. We’ll investigate if there is something at our end as our status report doesn’t show any issues that can cause slowness.

Thanks

@shreyans94
I’ve a few questions to understand this and to find a solution.

– How did you determine that?
– What mailer are you using (SMTP/HTTP)?
– Did you try alternate method?

Thanks

Thanks for your feedback. We’ll appreciate if you post it in our official issue tracker as it’s there where we weigh such requests.

@philclothier
Please consider opening a PR with your implementation. github.com/SparkPost/wordpress-sparkpost

“Less experienced developers sometimes make the mistake of using the deactivation hook for this purpose.”

https://media.giphy.com/media/1125FQpCo6Ubhm/giphy.gif

?? spot on!

Hello
Plugin stores the settings in database indeed. Removing settings upon uninstall is the way plugin should work unless there were some way to explicitly ask it to not to. If all plugins stored their data and none removed it, you would end up lot of unnecessary data with no reliable way to clean these up.

So, this behavior won’t change in SparkPost plugin. We are sorry if this is inconvenient to you.

This also means you didn’t follow the installation instructions mentioned on the readme/plugin page for completion of setup.

However, I think you have a good point about alerting when setup is not complete. I think an admin wide notification (like Akismet, IIRC) could be helpful. If you open an issue in our github issue tracker, we will weigh this in future release.

Thanks

• This reply was modified 7 years, 3 months ago by rajuru.
• This reply was modified 7 years, 3 months ago by rajuru.

Please check this and see if it helps.

https://github.com/SparkPost/wordpress-sparkpost/issues/24

There are other threads about gravity forms. Being a paid plugin, there is not much we can help as we can’t see its source code.

thanks

@sooskriszta
SparkPost shows you the full key immediately after creating. So if you don’t have full key, you can generate new one. After creating it, copy it and paste in plugin’s settings page.

If you are not aware of usage of your previous key, consider deleting it to avoid potential abuse.

https://www.sparkpost.com/docs/getting-started/create-api-keys/

Thanks

Please post this issue in our official issue tracker and we’ll love to investigate more and figure out a solution.