Delicious Brains

Hm, that makes it sounds like the AWS keys didn’t get migrated over to the new settings format, but it’s unusual that the other settings did get migrated over.

A potential workaround could be to define them in the wp-config.php file as shown here: https://deliciousbrains.com/wp-offload-ses/doc/settings-constants/#aws-access-keys

Are these sites single site installs or multisite? Did it happen on every site upgraded or just some of them? I haven’t been able to replicate this in testing, but if there’s something in common between these installs that might help.

Hi,

Are the settings and AWS Access Keys still present in the plugin settings pages? I’m assuming they are since you’re able to send a test email.

If possible, could you enable debug logging by editing your wp-config.php file and changing this line:

define( 'WP_DEBUG', false );

To these lines:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

And then try to trigger an email again. Any errors should be logged to the wp-content/debug.log file. Once done you should revert the above changes.

Hi,

I haven’t seen any other reports of this particular issue. Were you able to see the domains/email addresses listed in the “Verified Senders” tab before resetting the keys?

Were the access keys still in the plugin and you had to delete them to reset them, or did you have to enter them as if for the first time?

Thanks for the additional info. Unfortunately I’m not seeing anything there that is obviously related to the issue. You mentioned that you’ve already found a replacement plugin, but if you’d like to troubleshoot further the next steps would be to enable debug logging and see if there is anything helpful in the PHP error logs.

You could do that by changing this line:

define( 'WP_DEBUG', false );

To these lines:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );

And then try reloading the plugin page again. Any related errors would likely be logged to the wp-content/debug.log file.

Hi,

WP Offload SES Lite actually uses the built-in PHPMailer, so it’s strange that you’re running into this.

If possible, could you please include the diagnostic info from the plugin Support tab (feel free to redact any personal information in that)?

I wonder if another plugin could be causing a conflict.

Hi,

Sorry to hear you ran into trouble with the update. Did you have any constants in your wp-config at all? I haven’t seen any other reports of this, and we didn’t run into it into testing, so it’d be interesting to see what caused it.

Yep, you don’t need to replace the GUIDs. Cheers @lukefiretoss.

This should be resolved with the latest version

This should be resolved with the latest version.

This should be resolved with the latest version.

WP Offload Media can be used with both S3 and MaxCDN for an optimal experience.

S3 is for “cloud storage”, getting stuff off your server.

Content Delivery Networks (CDNs) like MaxCDN and CloudFront can then be used to deliver that media offloaded to S3 to your site visitors much quicker via their edge servers.

https://deliciousbrains.com/wp-offload-media/doc/quick-start-guide/#using-a-cdn

Thanks!!

Hi @hmonroe,

It looks like this is a bug with parsing the headers of the Contact Form 7 plugin. We’re looking into this further and will let you know as we have further updates.

Yes, it works with PHP 7, these are just warnings.

Hi Laszlo,

WP Migrate DB Pro transfers database tables, so you could certainly transfer blog posts between sites with the plugin by transferring the wp_posts and wp_postmeta tables.

In addition, with the developer level license and the Media Files Addon, you can transfer your site’s media files during a migration.

More information can be found here.