• Hi,

    We have been using WP Offload S3 for over a year with no issues at all but after updating to version 1.1 on our multisite network we have encountered a lot of problems with broken images. This seems to be specifically on the Divi theme, I have updated a lot of the images which fixes the problem to a degree but even after updating some images they break on the frontend. We don’t store any images locally so any local path will be broken but I’m unsure why the frontend image URLs aren’t being updated to the S3/Cloudfront URL.

    We have contacted Elegant Themes (Divi) about this but yet to hear a reply so I thought I’d try and see if anyone could offer any advice as I’ve run out of options and we have a lot of sites with broken images.

    Thanks in advance.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor A5hleyRich

    (@a5hleyrich)

    Hi,

    Do you have an few example URLs to images that are breaking? Or, a link to the page where we can see the broken images?

    Thread Starter adam__ph

    (@adam_ph)

    Yeah sure, if you go to https://cloudcanvas.website/ you will be able to see the broken images with web inspector.

    As you can see from the site that the majority of the images load perfectly.

    Thanks!

    @adam_ph – Looks like you got it figured out at the bottom of your site. Question – were those images previously ‘featured images’ from posts/pages? We recently upgraded on a staging site and we’re finding that with Divi, if you have it set up to use ‘thumbs’ on archives/posts, meaning Divi will take the first image in the post and use it as a featured image, then – if you don’t manually upload a specific featured image that Offload S3 seems to miss changing the URL on load and attempts the local server URL, which in our case would be broken because we remove images from our server.

    Thanks

    Thread Starter adam__ph

    (@adam_ph)

    @fanalejr, thanks for replying. Unfortunately we never fixed the issue directly, in fact the images had to be hosted on a different site so offload S3 didn’t change the URL.

    It seems hit and miss with Divi as some images work fine while other are broken, even when use ‘first image as feature’ is set.

    We have run into problems with other plugins since such as PDF embed which now doesn’t show the PDFs since the update.

    We don’t store media on the local server once uploaded to S3 which which is why we are getting broken images but I still can’t understand why so many URLs aren’t being filtered.

    Plugin Contributor A5hleyRich

    (@a5hleyrich)

    Sorry for the delay in getting back to you. We have a new version due out shortly which should resolve issues with Divi.

    Thread Starter adam__ph

    (@adam_ph)

    Hi @a5hleyrich,

    No problem, this is great news thanks!

    I look forward to the update.

    Thanks,

    Hello,

    I have an active 500K license with 102,000 media files.

    I have exactly the same problem. Since I updated WP Offload S3 Pro from 1.1.4 to 1.2, my website is a mess. Some image links are broken because the URL in the HTML source is still the link of my website and is not replaced by the link on Cloudfront and no image is stored at all on my server.

    The problem particularly occurs when using global Divi libraries.

    I tried to downgrade, but it is worst. As no images is stored at all on the web server, all the image links still link to my website and are not replaced in the database by the links to Cloudfront. And it should be with the WP Offload S3 Pro 1.1.4

    What can I do now ? Please help !!

    Thread Starter adam__ph

    (@adam_ph)

    Also worth pointing out that when using WP Bakery Visual Composer the same problem happens when adding a background image.

    Massive need for the option to stop S3 Offload from using local paths when the setting to delete from server is active, it makes no sense and is causing so many issues with various sites.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Broken images with Divi theme after updating to version 1.1’ is closed to new replies.