Today is once again release day for WP Offload S3 🎉 and with it comes some new features and improvements.
We’ve merged compatibility addons into the core plugin, added support for copying files between buckets, as well as made some other updates to improve the speed of your workflow and your page load.
Compatibility Addons For All
WP Offload S3 is designed in such a way that it should play nicely with the majority of third party plugins. However, in some cases we have to introduce code to get them to work. Up until today, this was done via separate plugins we called compatibility addons. We had compatibility addons for each of the following plugins:
In WP Offload S3 1.5 compatibility addons are no longer required. Instead, the compatibility code is part of the core WP Offload S3 plugin. We’re also making compatiblity with these plugins available to all license holders, so no more need to upgrade just for plugin compatibility!
When you upgrade to WP Offload S3 1.5 any existing compatibility addon plugins will automatically be deactivated and a notice shown. You will then be able to safely delete the now-retired compatibility plugins.
Recently, Evan wrote about using WP Offload S3 in development and staging environments. One of the strategies discussed was mirroring your production bucket in your staging or development environments. To streamline this process, we’re pleased to introduce the Copy Files tool. When you change your bucket via the WP Offload S3 settings screen, you will now be prompted to copy your existing offloaded files to the new bucket.
The tool will work quietly in the background and can be paused, cancelled or resumed at anytime.
The tool works using the CopyObject command, which results in the move tool completing very quickly because the files are moved directly between S3 buckets without ever hitting the local server. Command Objects are also used to copy large batches of files in parallel, which keeps local server usage to a minimum.
Content Filtering Cache
WP Offload S3 1.2 introduced content filtering which ensures that S3 URLs are no longer stored in the database. Instead, the local URLs are rewritten to S3 on page load. However, for the rewriting process to perform optimally we had to utilize a caching mechanism that maps attachment URLs to their corresponding attachment ID. This cache is currently stored in the
postmeta table, which can cause the table to grow unnecessarily large. In this release, we automatically utilize a persistent object cache instead if one is available. This should help to decrease the size of the
postmeta table going forward.
Improved CLI Support
Support for the
wp media regenerate command has been introduced, which allows image sizes to be regenerated even when the local files have been removed from the server.
That’s a Wrap
As always, this release also includes a number of improvements and bug fixes. Check out the full WP Offload S3 changelog for more details.
Next, we plan on making considerable improvements to the Assets addon. If you’re not already subscribed, sign up below to be the first to hear about the announcement. What would you like to see next for WP Offload S3? What do you think of the changes this release brings to WP Offload S3? Let us know in the comments below.
Been waiting to give WP Offload S3 a try? Remember we have a 60-day money-back guarantee so you can give it a go risk-free: https://deliciousbrains.com/wp-offload-media/