• We are using version 1.1.5 of WP Offload S3 Lite. When going into edit an image, after reverse engineering WP core code, I found that it is trying to load a valid image stored in S3 via s3://bncore/wp-content/uploads/2016/08/IMG_1017-1.jpg. This does not appear to be working. When I go to the original URL for the same image, https://s3.amazonaws.com/bncore/wp-content/uploads/2016/08/IMG_1017-1.jpg, it works fine.

    Were using a multi site installation of WP and on a load balanced setup.

    It does not happen on all images. Is this tied to the upgrade procedure that is running?

    It only happens when trying to edit an image. All other places the image displays fine.

    Is there a way I can disable the use of the s3 protocol and just use the https protocol version of the image URL? Or is there something else I need to do for this part of WP to understand the S3 protocol?

The topic ‘Using S3 protocol breaks image paths’ is closed to new replies.