Delicious Brains Support

Hi there,

Thanks for the update!

The 405 HTTP error code indicates that your web server doesn’t allow the PUT HTTP method which is quite unusual these days. After the initial creation, all our settings are updated using the HTTP PUT method so this is most likely what’s causing the Deliver Offloaded Media not saving and the Save and Continue button not working.

Relying on the different HTTP methods isn’t limited to just WP Offload Media, we know that parts of Gutenberg (Block editor) will use the HTTP PUT method to update certain aspects of posts and pages. Over time, more and more functionality in WordPress is going to require that the REST API works as expected.

Before version 3.0 we didn’t use the REST API to update settings, so it’s possible that you previously had an older version of the plugin and when you’ve updated to the latest version, the issue then occurred.

The best way forward is to make sure that the web server accepts at least the more common HTTP methods: GET, POST, PUT, DELETE, and HEAD. I recommend reaching out to your server admin as they would be better equipped with assisting you on this issue.

Hi there!

Better Search Replace Support Team here, Thanks for reaching out with your query we would be happy to assist

Since you already have the Max Page Size set to 1000, could you also please lower the Max Results to 20 and see if that helps?

If the issue persists, can you please try editing your wp-config.php file on the server to replace this line:

define( ‘WP_DEBUG’, false );

With these lines –

define(‘WP_DEBUG’, true);

define(‘WP_DEBUG_LOG’, true);

define(‘WP_DEBUG_DISPLAY’, false);

This will cause all runtime errors, warnings, and notices to be written to /wp-content/debug.log, which will hopefully yield some better information about what’s going on.

Can you please try the process again and then send on the debug.log file if created?

More details about that at https://www.ads-software.com/support/article/editing-wp-config-php/#wp_debug

Once we have finished troubleshooting, you should revert that config change and delete the debug.log file.

Hi @mluzvdb ,

Thanks for the creating a new thread. You are right, we missed your other thread. We thought WordPress would somehow automatically mark your other thread as unresolved after you replied.

Thank you as well for the detailed step-by-step. I was able to replicate this issue as well. Also, skipping the “aiowps_audit_log” table also helped with the migration issue in my case.

I’ll pass this along to our dev team so that they can look further into this issue.

Hi,

WP Offload Media Support Team here. Thanks for reaching out with your query! We would be happy to assist. To try and get more information, would you please try editing your wp-config.php file and replace this line –

define( ‘WP_DEBUG’, false );

With these lines –

define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define(‘WP_DEBUG_DISPLAY’, false);

This means that any errors are logged to /wp-content/debug.log, because some errors are not visible on screen. More details about that at https://www.ads-software.com/support/article/editing-wp-config-php/#wp_debug

Can you try the process again and then attach the debug.log file with your reply.

Thank you.

Hi,

WP Offload Media Support Team here. Thanks for reaching out with your query! We would be happy to assist.

Unfortunately, if you do not have a working access keys, it would be impossible for WP Offload Media (free or pro) to access your bucket.

I would suggest to try and contact the AWS Support directly regarding this, as they would be more knowledgeable and might have a way to help you in your situation. (i.e. a way to recover access to the AWS account or bucket)

Thank you.

Hi @mrbm,

Just to confirm, the latest filter code that you have shared is now working as intended?

Hi,

To try and check if AWS credentials are working correctly, you could try browsing your buckets on the plugin – https://share.getcloudapp.com/9ZugoWD1

Regarding the main issue, are you able to change and save the other settings? is the issue limited only to ‘Deliver Offloaded Media’ setting only?
Could you kindly try disabling any type of caching that your site may have and see if it fixes the issue?

Thank you.

Hi @matstars,

Thank you for the clarification. We can’t tell what email was verified. But can you kindly try verifying the domain directly on AWS, and see if it succeeds?

Hi @torlockc,

Thank you for the update. Can you kindly confirm what PHP version the site is on? Can you also let us know what version of the plugin you were using before updating?

It might also help to ask the hosting provider for any other error logs available.

Hi @innovationv,

Thank you for the update. That message shows up for when a private file can be accessed using an unsigned URL. This happens during the plugin’s testing of the public and private delivery from the bucket using test files.

Can you kindly verify the configuration of private media settings as suggested from the error message? If you’re using CloudFront, you may refer to this guide:

https://deliciousbrains.com/wp-offload-media/doc/serve-private-media-signed-cloudfront-urls/

Hi there!

Thanks for the update!

That error happens when your site sends an email from an email address that hasn’t been verified with your AWS account. You can either verify the email address provided in the error details in the Verified Senders tab, or you can change the email address to one that is verified.

Since you’ve already attempted to verify the domain from the Setup Wizard and nothing happened, could you please instead try to verify via the Verified Senders Tab on the Settings Page of WP Offload SES and click the ‘+ Add New’ button.

If you’re not sure where that email address is being used on your site, it may be worth checking any other plugins to see if they are configured to send emails from that address. Another common reason we see is a contact form plugin configured to send emails as the form submitter instead of the website owner.

Please let us know how that goes.

Hi there!

Better Search Replace Support Team here, Thanks for reaching out with your query we would be happy to assist

Would you mind providing us the search and replace terms you’re using? We’d like to try and replicate the issue.

We look forward to your response!

Hi Mat,

WP Offload SES Support Team here. Thanks for reaching out with your query, we would be happy to assist!

It looks like this is the 2nd ticket about this issue we have received. But we want to double check. If you dismiss that message, and then send another email from the site, does that error come back up?

Please also check our documentable below to see if it helps. If your debug.log file is already enabled, are there anymore errors coming from SES or AWS?

https://deliciousbrains.com/wp-offload-ses/doc/sender-verification-errors/

Hi @jpandino ,

Thanks for the additional information. If you dismiss that message, and then send another email from the site, does that error come back up?

Amazon WorkMail is different from Amazon SES. Kindly ensure that you have completed your SES account in your AWS dashboard.

https://deliciousbrains.com/wp-offload-ses/doc/quick-start-guide/

Another thing you can try is creating a new access key for the IAM user and using the new key on your site.

You can also follow our guide below for further steps in debugging the issue.

https://deliciousbrains.com/wp-offload-ses/doc/sender-verification-errors/

Hi there!

Better Search Replace Support Team here, Thanks for reaching out with your query we would be happy to assist.

Unfortunately, these types of search isn’t supported with Better Search Replace (free or pro), but one of our other plugins, WP Migrate, supports regular expressions in its Find & Replace tool: https://deliciousbrains.com/wp-migrate-db-pro/doc/find-and-replace/#regex-find-replace.

With regular expressions, you could then do the following to search for exact matches only – https://stackoverflow.com/a/23117977

Thank you.