Hi @parakeet,
Effectively, there will be probably some conflicts. On our side, we do need the guid of the asset to be accessible so we can sync it to Cloudinary. I had some cases where users were offloading their assets to S3 and the guid weren’t accessible anymore so you might have this kind of conflict.
On a side note, looking at the support post you opened on the WP Offload Media plugin page, here are some comments:
- You can sync your assets to Cloudinary and use our backup feature to backup your assets to your own storage as documented here so assets are stored in Cloudinary and you have a backup of those in S3 or Google Cloud.
- You mention deleting assets in your WordPress Media Library. Please do not delete assets as they will be deleted in Cloudinary as well (Assets deleted in Cloudinary won’t be deleted from WP but assets deleted in WP are deleted in Cloudinary). What you can do here is use the
Cloudinary Only storage options of the plugin to remove assets from your WordPress storage.
Hope that helps.
Best,
Loic
Hi @parakeet,
The only workaround that works would be to rewrite the attachment URL to point them to your s3 bucket so we can sync them.
add_filter('wp_get_attachment_url', function ($url)
{
if(file_exists($url))
{
return $url;
}
return str_replace("https://www.domain.com", 'https://your-s3-url', $url);
});
Best,
Loic