3.1.0 Release Notes

  • Change log

    • Backblaze support re-added. Note that the asset push and direct upload features do not work with Backblaze.
    • Added option to Migrate to Storage to skip uploading thumbnails. This option requires Imgix or Dynamic Images and will only appear if either is enabled.
    • Added option to Migrate to Storage to control how upload paths are handled. This option requires that you have a custom prefix defined in Cloud Storage settings and will only appear if you do.
    • Fixes for Migrate to Storage when run in ajax (non-background) mode.
    • Updated migrate command line command to include switches for skipping thumbnails and handling upload paths.


    Return of Backblaze

    So Backblaze support was added back to the plugin. Initially we were going to release it as a separate plugin, but it was going to be too much extra work to manage both.

    We do not recommend Backblaze. There are a lot of reasons why:

    • Of all the storage providers we've tested, Backblaze is consistently the slowest
    • Features like asset push and direct uploads do not work with Backblaze
    • No support for pre-signed URLs making it useless for WooCommerce or Easy Digital Downloads
    • Did we mention how slow it was?
    • Everything must be public

    Migrate to Cloud Options

    Two new options were added to the Migrate to Cloud feature:

    Screenshot of Safari (7-23-19, 1-30-30 AM).png

    Like the sign says, this allows you to skip uploading the thumbnails and extra image sizes that WordPress produces. It requires that you have Imgix or Dynamic Images enabled. In fact, this option won't be visible unless it is.

    Screenshot of Safari (7-23-19, 1-31-43 AM).png

    Prior to this update, migrate to cloud would preserve the directory structure of your local storage. Now you can specify three different modes of operation:

    • Keep original upload path - This works like Migrate to Storage has always worked, your local storage directory structure will be retained on cloud storage.
    • Replace upload path with custom prefix - This option will use the custom prefix you've defined in your Cloud Storage settings when uploading.
    • Prepend upload path with custom prefix - This option is a mix of the two. This will prepend the custom prefix to the original upload path. For example, if your original upload path was 2019/09 and your custom prefix is uploads/go/here your files would be stored in uploads/go/here/2019/09

    This option is only available/visible if you've set a custom prefix in your Cloud Storage settings.

Log in to reply