Community forum for knowledge and support

Updated 3 days ago

Image Issue in Hero

Image Issue in Hero!
Has anyone seen this weird issue before?
https://share.zight.com/rRuKQ8p6
When trying to add an image to a collection header, the image placeholder appears, and images can be selected from within Webflow/Media/Uploads area. However, when selecting an image assigned to a collection, the image does not display, effectively disappearing from the page.

Read Only Link

M
J
49 comments

@James Davis-Sigley are you able to provide a published URL as well?

@James Davis-Sigley yeah I really think its just the fact that the fields are filled out - I know you kind of showed that but actually initially you didn't have anything in that field. But when I toggle through the items, and land on the one you were editing in your video, with the landscape aerial photo - it loads up fine in that component.

and that must be an older published version because what is in designer now versus published is different

Woooow what the heck! It’s working now 🤔

Wait….its blank on mobile? 🤔 🤔

hmm not for me its not

I’ll try a different browser. Screenshot was from safari.

yeah safari is bad lol

Attachment
IMG_1508.png

K so this is brave , both on/off my wifi so can’t be caching issue 🤔 🤔

hmm idk - all of the fancy stuff goes away as soon as it goes to tablet, its just a stacked image

there's really nothing going on within this component tablet down

Sorry Matt, so are you saying its a component problem or a collection problem? Trying to understand.

saying its pretty unlikely to be a component issue

@James Davis-Sigley try checking this box and publishing and testing on mobile - maybe Webflow is trying to render an asset that isn't loading properly or something but we can rule out any interference by Webflow with this checkbox.

Attachment
image.png

or maybe it is a component issue - I'd have to look at the vanilla component - but if this dropdown was set to lazy load by default, then its a component issue but if it wasn't then I would say this may also be the reason

Attachment
image.png

hero headers should always be set to eager load with the page, never with lazy load on scroll like it is set right now.

OK, I’ve set those settings you;ve suggessted. Trying again

Just a note - this isn’t unique to this header. It’s EVERY header section

I could put header 3 on the page and as soon as I connect it to a collection image it disappears…unless I use the logo field!

okay, so not unique to this collection item, you mean?

makes sense, its a template thats just swapping out dynamic data

hmm yeah well those collections items all had header image empty except one

engineers do this to me all the time "It works fine for me" its infuriating. I'm seriously not trying to do that to you here.

im just pointing out what I'm seeing so far and there's not a lot of evidence pointing me towards the component itself

Correct - I dont think its the component

coz if I put say header89 on the page, as soon as I connect to any of those image fields the whole image disappears

and yeah, It doesn't have to just be a component issue to get help from me - a bug is a bug - so if we can figure out a solution, happy to help any way I can

Should i reach out to Webflow support?

Or maybe delete/duplicate the collection and start over

(appreciate your help)

I would maybe consider cleaning up the collection items themselves first

ok, There is only one

maybe to the point of deleting those items and then just use the webflow generate items, and it'll fill in all the fields for you real quick

Oh wait - no there isnt

so then you have nice clean data to test and work with first

which is my general rule anyway - and then from there you could delete those items, and start populating with real data and feel confident everything is displaying properly.

Oh no…..this collection is linked into EVERYTHING!

This is like the master collection for the entire site 😞

i think I might need to create a new collection and test it there

yeah with that many changes, we may not ever know what is causing this then but oh well if its resolved, its resolved

Fixed it!

Assigning an image to each of the collections worked!!

Not sure why, but it worked 🙂

I’ve made it a required field 🙂

Add a reply
Sign up and join the conversation on Slack