rajuru

@sudar
Thanks for your insights. Yeah, our goal was to support php versions that wordpress supports but didn’t reach EOL. We’ll do better job clarifying that.

Thanks for testing our latest version and confirming.

Again thanks everyone for letting us know promptly and for your patience; we’re sorry for any inconvenience occurred in the meantime.

@sudar
Thanks for explanation.

The plugin not gonna work at all below php 5.3 as we use namespace. However, we require PHP 5.6.

Also I admit it was not clear. So I just logged an issue to make it clear in plugin page.

Also we’re releasing a patch to fix the issue for now.

Sorry to hear that. I got another similar complain but could not reproduce it.

What php and wordpress version are you using?

@luxman
can you please create an issue in official issue tracker with some explanation what does not work and what you tried?

@clangille
It might work with multisite now but with single configuration. We are hoping to implement pure multisite in near future.

Thanks

Good to know @drazimmermann.

Disable engagement tracking from plugging settings. This should not convert your links to tracking links.

@michaelnorth
Sorry that you had that experience.

From SparkPost document

You are receiving this error because Gmail uses the return-path domain for that error message. However, it is your from domain that the reputation is actually referencing. We have clients sending to Gmail from the same return-path and IPs that are not experiencing inbox issues.

So I’ll suggest a few things
– Add your own bounce domain. Then it’ll use your domain instead of sparkpost for the return path
– Follow this guide which will have more guides linked; to improve your deliverabilities with SparkPost.
– Also read this to get more idea about strategy to improve your reputation

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

@aggk
Unfortunately, that’s not specific to plugin itself. That response is generated by SparkPost platform. I suggest you contact support or reach out deliverability channel of SparkPost community slack.

It’s possible to do but we don’t have any plan to do it. During uninstall, plugin should cleanup database records it added.

Error: Cannot access protected property WPSparkPost\SparkPostHTTPMailer::$endpoint

Ah, that’s a super silly oversight! It must not be protected. I’ve just logged a bug. We’ll fix it ASAP.

Do you think your team could welcome this option as an opportunity of improvement?

Sure. We log all enhancement ideas. Please create an issue in https://github.com/SparkPost/wordpress-sparkpost/issues. We’ll surely consider it based on demand.

Thanks for your specific suggestions. However, settings page is for most generic use cases. Having those extra fields in the settings page may even confuse the non-enterprise users. However, if we see a growing demand for this, we can surely consider that.

You can see this buddyfix example how to use a hook.

In the same way, you can use any of the appropriate hook listed in the previous link. For example, you can customize the whole payload (data sent to sparkpost), using wpsp_request_body hook.

add_filter('wpsp_request_body', function($body){
    //you can modify anything in $body here
});

you can customize the payload as transmission api supports.

and to modify the endpoint, you can use

add_action('wpsp_init_mailer', function($obj) {
  $obj->endpoint = 'YOUR_API_ENDPOINT_HERE';
});

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

You should be able to solve all of these problem using one or more hook(s).

https://github.com/SparkPost/wordpress-sparkpost/blob/master/docs/hooks.md

Buddypress handles emails differently. You can follow this guide to enable buddypress to send via sparkpost

https://github.com/SparkPost/wordpress-sparkpost/blob/master/docs/buddypress-fix.md

Thanks for clarifying. It makes sense. I think i’ll first test it and see how it works with multisite now. API Key is not the only thing required.

Your English is just fine :).