Pel

Hi, we are experiencing the same issue

Thanks @nfong for the tip re: core Sitemaps in WP 5.5. That’s the direction we’re taking our clients as well.

With the most recently released version of the plug-in and define('UPDRAFTPLUS_S3_OLDLIB', true); we are now able to successfully upload to S3 with SSL Certificate Verification turn on and using the plugin’s default SSL certs, so this seems like a good solution since it doesn’t sacrifice security.

Thank you for your help.

@davidanderson Yes, we are using a recommended AWS naming convention of com.domain.bucket-name

We are on WordPress 5.9.1 and PHP 7.3.30

Hi, we noticed a new release targeted at some of these AWS issues so upgraded to v2.22.5.25.

To test, we removed define('UPDRAFTPLUS_S3_OLDLIB', true) from wp-config.php and turned SSL certificate validation back ON.

An issue still persists so we’ll upload the conflicting plugin via the Paid Support Request form per your suggestion.

The error we are now receiving is:

PHP Fatal error (TypeError) has occurred during backup uploads to the s3. Error Message: Argument 1 passed to Aws\Common\Client\AbstractClient::__construct() must implement interface Aws\Common\Credentials\CredentialsInterface, array given, called in /var/www/html/wp-content/plugins/updraftplus/vendor/aws/aws-sdk-php/src/MultiRegionClient.php on line 53 (Code: 0, line 73 in /var/www/html/wp-content/plugins/wpdm-amazon-s3/aws/Aws/Common/Client/AbstractClient.php)

• This reply was modified 2 years, 9 months ago by Pel. Reason: Issue actually persists on staging as well
• This reply was modified 2 years, 9 months ago by Pel. Reason: fixed typo

Thank you, that worked. Not ideal to have to turn off SSL cert validation but will have to do until we figure out a permanent solution to upgrade the outdated plug-in.

Hi, apologies for not having already tried that before posting.

The conflict is with the WPDM – Amazon s3 plug-in.

With that plug-in disabled, both the S3 settings test and remote backup upload work successfully.

Unfortunately, we can’t update that plug-in due to some incompatibilities with our system and it’s a core function that we need to keep.

We tried adding the define('UPDRAFTPLUS_S3_OLDLIB', true); setting to wp-config.php and with that enabled the S3 settings test passes and is able to access the bucket and create a file:

S3 settings test result: Success: Region: US: We accessed the bucket, and were able to create files within it.

But the actual upload of remote backups fail with the following error:

Amazon S3: Error: Failed to access bucket [REDACTED]. Check your permissions and credentials. (1) UpdraftPlus_S3::getBucket(): [51] SSL: no alternative certificate subject name matches target host name

But access should work give the success of the S3 settings test. Any thoughts on how we might be able to resolve and keep using the old S3 lib?

Thank you.

Given the similar post in the forum, I should mention that we do not have AWS Plugin for WP installed.

We tried the manual migration on the latest version of the plugin on this instance that’s having issues and the DB tables still have not been created.

Sample error (db name and prefix changed):

WordPress database error Table ‘xxxxx.prefix_ig_lists’ doesn’t exist for query SELECT id, name FROM prefix_ig_lists WHERE deleted_at IS NULL OR deleted_at = ‘0000-00-00 00:00:00′ made by do_action(’email-subscribers_page_es_subscribers’), WP_Hook->do_action, WP_Hook->apply_filters, Email_Subscribers_Admin->load_audience, ES_Subscribers_Table->plugin_settings_page, ES_Subscribers_Table->prepare_items, ES_Subscribers_Table->search_box, ES_Common::prepare_list_dropdown_options, ES_DB_Lists::get_list_id_name_map

• This reply was modified 5 years, 6 months ago by Pel.
• This reply was modified 5 years, 6 months ago by Pel.

Hi, has this filter been added?

We understand updating the plugin with new functionality but having so many breaking changes that aren’t backwards compatible is frustrating.

Thanks for your suggestions re: how to change messages but as you mentioned, directly altering a plugin is terrible practice as the changes will be overridden by subsequent updates.

Could you please add a filter so this can be done in a sustainable way? I’m sure there are many people who will want to change the messages as language is such a subjective thing.

I think this would do the trick before the return statements:

$messages = apply_filters( “es_subscription_messages”, $messages );

…also, since the submit button is named “submit” it hijacks the JS form submit method and so we can’t use that in place of es_submit_pages().

Yes, we are having the same issue.

Firefox JS Console Error: “TypeError: target is undefined”

Chrome Console Error: “Uncaught TypeError: Cannot read property ‘parentElement’ of undefined”

On Line 7 of es-widget-page.js

Note for anyone else following along in case this may be of help. We added the following code to prevent the Return key from submitting the form in Chrome.

jQuery('form').bind("keypress", function (e) {
   if (e.keyCode == 13) return false;
});