Broken images on collection item update if it was originally published throught the API

Community resources Bugs
1

I’m creating this issue as a reference, I have also contacted Webflow support about this. I’ll update the thread with any responses I might get.

When a collection item is published through your public API (or Zapier), the content can include images with any src. Yet when you update that item and publish it afterwards from Webflow itself all images are broken.

Original URL: https://images.storychief.com/account_8889/unsplash-image_5f1c12a37f6b82d346429e757b6ea3b6_800.jpg

After update & publish: https://uploads-ssl.webflow.com/account_8889/unsplash-image_5f1c12a37f6b82d346429e757b6ea3b6_800.jpg

I see 2 possible solutions to this bug:

  1. Webflow sideloads all incoming images and hosts them on uploads-ssl.webflow.com
  2. Webflow stops transforming image URL’s when the source is not a webflow domain (here: uploads-ssl.webflow.com).
2

Also created a wishlist idea for this as well.

3

I received a response from Webflow support. It appears they are no immediate plans to solve this (2 year old) bug.

This is a bug we are aware of when rich text content has images with external refs are imported into the Webflow CMS, as you've noticed when the post is updated in Webflow the image URLs are then updated to urls referencing the Webflow CDN (leading to an error as there is no image loaded there).

At the moment, the only workaround is that the image will need to be re-uploaded inside the Webflow CMS on affected items.

I don't have a timeline of when an improvement will be implemented, but I have recorded your instance as a reference to the item we have related to this
4

Gregory, if we only use storychief to edit the content inside a CMS item – there are no problems, right?

5

Hey @Ricardo_Giuliani
That’s correct. The issue is clearly coming from the rich text editor of Webflow. If the richt text content is updated whithin Webflow, it will break all image URLs.

6

Ok, we’ll steer clear from that. It’s helpful to know! We will rely on storychief and custom fields alone!

7

Update.
We tried posting images in this format: //images.storychief.io/... instead of https://images.storychief.io/... in the hope that would be a workaround, but sadly it isn’t.

8

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.