Delicious Brains Support

Hi @golfball-uhu,

This is indeed weird and might be difficult for us to diagnose as we simply do not know much regarding your site’s setup.

As for the query, it should be okay to press ‘ok’ in this instance, just make sure you have a database backup just in case.

Regarding the error, just to double check, when you are looking at your files using FTP, were you sure that the following folder is no longer existing ? ‘/var/www/web14/htdocs/testshop/wp-content/plugins/better-search-replace/’

If it is indeed no longer existing, then the most usual suspect that can cause these issues are the cache. Kindly make sure that any server, object or database cache are cleared (you could try asking your hosting support to help with this).

Kindly let us know how it goes,
Thank you.

Hi @mrbm,

I’m not sure on how wpmudev domain mapping works, but it would be best if you could try testing the ‘as3cf_filter_post_local_to_provider’ filter and see if it works in isolation (outside another filter, on it’s own function).

Depending on how you are remapping your domain, you might need to use the following – https://deliciousbrains.com/wp-offload-media/doc/filtering-urls-for-multiple-domains/

Thank you.

Hi @pauljbis,

Yes, your hosting provider can help give you any error logs available from the server. We’ll await for your updates.

Hi @torlockc!

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

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 @mrbm!

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

We’re not familiar with how Rank Math works, but perhaps adjusting the filter priority might help? If the original code suggested by Rank Math doesn’t work, it might be best to reach out to them first.

Please let us know how it goes!

Hi there!

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

Based on that error, it seems that the Access Keys are invalid. Could you please make sure that your AWS access keys are valid and that the IAM user has the “AmazonSESFullAccess” permissions.

Please let us know how that goes.

Hi there!

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

We don’t directly support Contabo, but it seems that it is S3-compatible according to their website.

It might need a bit of coding and editing, but you may be able to use our plugin with Contabo.

Our colleague, Ian, wrote a great post where he used filters to get Minio (another S3-compatible storage) working with Offload Media – https://deliciousbrains.com/s3-compatible-storage-provider-minio/

Hi there!

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

WP Offload Media can only offload media files that exists on your WordPress Media Library. If the images you’ve linked to your posts do not exist on the Media Library then I’m afraid WP Offload Media won’t be able to handle and offload those files.

You’ll need to upload those images first on your WordPress Media Library for WP Offload Media to notice and offload those files.

Please note that both WP Offload Media Lite and ‘Pro’ can automatically offload newly uploaded media files. However, WP Offload Media ‘pro’ can also offload existing media files while WP Offload Media Lite cannot.

More info here – https://deliciousbrains.com/wp-offload-media/upgrade/

We offer a 100% No-Risk 60-Day Money Back Guarantee. If for any reason you are not happy with our product or service, simply let us know within 60 days of your purchase and we’ll refund 100% of your money. No questions asked.

https://deliciousbrains.com/wp-offload-media/pricing/#guarantee

Hi there!

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

That error/notice usually occurs when you haven’t setup an external cron. WP Offload SES relies heavily on cron functioning correctly for background processing. Here’s how you can set up an external cron:

https://deliciousbrains.com/wp-offload-ses/doc/cron-setup/

Hi there!

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

While we would like to be able to integrate using R2 into our plugin as it is a popular request, at preset R2 does not handle private objects in a way that is compatible with WP Offload Media.

As such, we can not support using R2 without limiting the functionality of WP Offload Media for R2 users by removing a feature that is needed for secure delivery of downloadable product files and other media that should not be publicly accessible.

We’re keeping an eye on the Cloudflare R2 service and hope to support it in the future should it become more compatible through changes to either R2 or WP Offload Media.

In the meantime, I’ve added your vote to our internal tracker.

Hi René,

May we know what error you get when you run the query?

Also, the query you posted seems to be missing a space. Not sure if it’s WordPress’ forum’s fault. There should be a space between FROM and wp_options.

DELETE FROM wp_options WHERE option_name LIKE ‘%bsr%’

Please create a backup of your site before running the query.

You may also ask your hosting provider for assistance if you’re unsure on how to run the query on your server.

Also, if Better Search Replace is already uninstalled and deleted, then you shouldn’t get a fatal error from the plugin. The error message was from April 29. Do you still get the error message today?

Additionally, kindly ensure that the path of the error matches your site’s document path.

The error log says your site is in here: /var/www/web14/htdocs/testshop/ Please compare this value to your site’s Dashboard >> Tools >> Site Health >> Info tab >> Directories and Sizes.

Hi @simkog ,

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

I looked into this, and I think it’s because GenerateBlocks also stores an image’s ID other than the background image’s URL. See screenshot below:

https://share.getcloudapp.com/GGu7w4eD

Better Search Replace can only replace strings that you search for, and so it doesn’t replace the image ID unless you run another search for it.

I think it will be best to also contact the dev team of GenerateBlocks to confirm this behavior. Perhaps they also have a filter where a background image’s ID is not saved in the post content.

Hi @ppayne!

Better Search Replace Support Team here. Glad to know you were able to sort it out!

You’re right. The database saves ampersand (&) characters as &, so you would need to use it for the search as well.

Hi @dreamsrealised22,

Thank you for sending that in! While we saw some errors related to Bluehost WP Plugin and Elementor, we didn’t find anything related to BSR.

Can you please check your browser’s debugging console to see if there are any errors reported when this occurs?

https://deliciousbrains.com/wp-migrate-db-pro/doc/debugging-browser-console-errors/

The guide is for our other plugin, but should still work for Better Search Replace.

Hi @pauljbis!

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

To answer your questions:

1. It’s best to check the error logs to get more info on what’s happening. If you haven’t already, please enable WP debug to capture any errors, notices, and warnings to a file called debug.log in the wp-content directory.

2. You would need to use the exact same string so that the plugin is able to detect it.

Please let us know how it goes!