Hi,
It’s not incompatible. WordPress needs its files to be hosted by itself, under the /uploads directory. That’s the way WordPress works.
WP Offload Media is kind of a hack for WordPress, and therefore, many plugins will fail, especially the ones modifying or updating your files.
I recommend you to use a very good CDN, in order to keep the advantages of having your files under WordPress and to enjoy the speed of a CDN. Anyway, uploading your photos on S3 or somewhere else will not make it faster than your WordPress hosting (except if it’s really a bad one), you will always need a CDN so I am not sure what’s the advantages (especially over the cons) are. I don’t want to blame the plugin, I am sure it can be used in certain cases (if WordPress is used as a simple system to keep a lot of photos for example, but not a real website), but generally, I don’t think it should be.
That said, the day WordPress allows officially to keep files in a remote service, the WordPress API will support it and all the plugins will work with it. So I would be you, I would wait for that day, and/or simply use a good CDN.
I am sorry but it will hard for me to work on the compatibility with this plugin, I am not even sure if it is possible 🙁 They should really have a page about the technical implementation, share an API, and how other plugins could work with it.
Thread Starter
oweux
(@oweux)
Hello Jordy,
I appreciate you taking the time to reply to my message and the information you provide.
I was hoping there is a way for your plugin, after renaming a file, to trigger a hook-type-of-thing telling WP that a file was “deleted” then a new one “uploaded” and thus triggering the rest of the cascade of tasks that WordPress does when a file is uploaded. In our current setup all files are still stored locally, nothing is deleted.
But the more I think about it the more I can think of exceptions and complications that go beyond the scope of this type of comment/request. For example, it may not be possible because we have “Object Versioning/keep different versions” enabled.
I agree with you several levels and regarding speed; moving stuff to S3 on its own may not be that good but on platforms like AWS where you pay different prices for different types of storage it does help to move media outside of certain storage types. Combining it with a CDN is where the speed improvements come. We use CloudFlare combined with our S3 Buckets to speed up delivery and use a sub-domain like images.ourwebsite.com.
They should have a page with information that other plugin developers can use to able to safely interact with theirs.
Thanks again! Have a great weekend.
Hi,
There are already triggers in my plugin:
– mfrh_url_renamed: URL is just to tell WordPress that the URL of the file was changed so that plugins which are using the URLs instead of the IDs can update themselves.
– mfrh_path_renamed: The filename has been changed.
– mfrh_media_renamed: The whole renaming processed has been finished (and this gives the old filename, the new filename, and the media ID).
So yes, it is possible for WP Offload Media to handle those events, and on a rename, mirror the rename on the remote service.
Cheers 🙂
Thread Starter
oweux
(@oweux)
Thank you Jordy,
hopefully they will be able to look into this and maybe we can get the two plugins to work together.
Funny enough, I deal with the same issue on my site. I use both WP Offload Media and Media Renamer Pro – both excellent plugins!
Despite what Jordy says, there are very good reasons for using Offload Media – I don’t use it as a CDN; instead, it’s a vital element of our website ensuring our media is not taking up space on our hosting platform. This is essential for me really and not a ‘hack’ as Jordy suggests. The workaround I’ve figured out is to remove the media from S3, download it back to the server, rename the file and then offload back to the bucket. You can do this on an individual file or as a bulk process. But always, remove from the bucket first, rename and then upload to S3 again.
