Forum Replies Created
WP Offload Media Lite does not have any background offload functionality, and can only offload newly added Media Library items.
WP Offload Media does have background offload functionality, and can offload both existing and new Media Library items.
WP Offload Media has its own custom table for keeping track of where each offloaded Media Library item has been offloaded to, and any attributes it may have such as being set as private etc.
WP Offload Media then uses this custom table to aid in URL re-writing and any further storage provider management tasks.
So I guess the answer is no, while another plugin may be able to adopt the offloaded objects itself, it’ll have to scan the bucket or be told where the objects are.
Maybe, if Vultr’s Object Storage S3-API is fully compatible.
We have a guide for using WP Offload Media with Wasabi that you could likely adapt to help you use Vultr’s Object Storage instead.
Please let us know how you get on, we love to hear about usage with other S3-API compatible storage providers.
Have you installed WP Offload Media Lite itself?
The Tweaks plugin helps you change the way WP Offload Media Lite works, and still needs that plugin to be installed and activated too.
Unfortunately direct offload to a storage provider without the media file first landing on the WordPress site’s server isn’t yet possible.
It’s on our to-do list, but I have no information as to when we hope to develop that feature.
Please can we see debug.log output captured during a failed offload of a newly added Media Library item?
@aspiesoft it is already possible to use a custom domain with WP Offload Media when using Google Cloud Storage as the storage provider. We have a doc that steps you through the set up process:
If I misunderstood what you were looking for, please can you give us more details?
Please can we see Diagnostic Info from WP Offload Media’s “Support” tab, and debug.log output captured during a refresh of the Media Library page?
That’s correct, in order for WP Offload Media to be able to set objects as either public or private, it needs to be able to control the ACLs for objects.
In the Google Cloud Storage Quick Start Guide we had a paragraph as follows:
IMPORTANT: If you create or update a bucket via the Google Cloud Platform Console do not enable Bucket Policy Only as this will stop WP Offload Media from managing the ACLs for objects.
When I wrote that guide “Uniform bucket-level access” was known as “Bucket Policy Only”.
I’ve updated the doc to now say:
IMPORTANT: If you create or update a bucket via the Google Cloud Platform Console do not enable “Uniform bucket-level access” as this will stop WP Offload Media from managing the ACLs for objects.
Thanks for bringing this to our attention @dhodun.
The majority of our docs are due for a refresh due to UI changes in a future release of WP Offload Media. At that time we expect to review the accuracy of the content, including adding or updating instructions and screenshots for storage and delivery providers.
There is built in integration for BuddyBoss avatar and cover images in WP Offload Media (not Lite).
Ah yes, Divi had compatibility code for WP Offload Media that needed updating, and they released a fix with version 4.14.9 (updated 2022-03-10).
Thanks for confirming that, much appreciated.
Glad you found the issue.
Out of interest, which theme was it?
Please can we see Diagnostic Info from WP Offload Media’s “Support” tab, and debug.log output captured during a failed offload?
Hi @bonumaster, thanks for the kind words, much appreciated.
> Will it replace the file uploaded in the CDN? or It will ignore in offloading? Will this plugin replace existing files if media is modified or we need to manually delete it in our DigitalOcean space?
WP Offload Media should re-offload the images after they have been processed, but it does depend on whether the watermarking process calls one of the functions that triggers the re-offload.
If it’s your own custom code that does the watermarking, then please ensure that after the files for a Media Library item have been processed that your code does something like the following…
wp_update_attachment_metadata( $item->ID, wp_generate_attachment_metadata( $item->ID, $file ) );
The important call there is
wp_update_attachment_metadata(), if you already have the attachment’s metadata you don’t need to regenerate it, just pass it in.
WP Offload Media will see the
wp_update_attachment_metadatafilter fired by the function of the same name, and copy the attachment’s file to the bucket, overwriting the previous versions if already offloaded.
I would recommend using the
as3cf_pre_upload_attachmentfilter to cancel the original offload though, and then remove that filter before doing the final
wp_update_attachment_metadata. That way you don’t waste time offloading to the bucket and re-offloading again, and it ensures CDNs only see the final watermarked files.
If you’re using a watermarking plugin, might be worth passing the above info onto the author if you’re seeing issues.
That’s probably a question for BuddyBoss.
WP Offload Media (not Lite) does have built in integration for BuddyBoss avatars and cover images.
However, it sounds like you’re dealing with Media Library items managed by BuddyBoss. WP Offload Media should be able to rewrite their URLs correctly as BuddyBoss has built in compatibility with WP Offload Media, but you’ll need to chat with BuddyBoss about their shortcodes.