I have a published site that I noticed had a typo in the legal line within the footer. I fixed the typo, republished, but the typo did not update for the homepage. The footer is a component and used in 14 locations. Shouldn’t this have updated across all instances? Can’t understand why this isn’t updating and I have no idea what to look into next.
The error is the word “it’s”, which appears in the legal line. It should read “its”.
any help solving this mystery would be appreciated.
Thanks @memetican . That was an easy fix, but there’s no way I would have found that. It’s an amazing resource to have folks like yourself available to help newbies like myself with these little issues!
To help my educational journey, how does this happen? I don’t recall ever putting an override in place for this. I’ve overridden other things, so I’m familiar with the concept. But in each of those instances, they were purposeful, so I know they exist. Can an override accidentally occur? This might be an impossible question to answer, but I’d like to get a better handle on this stuff moving forward. Or perhaps the better question is: where do you look to identify if an override is in place? Honestly, I just took your recco and clicked the Disconnect button. Was the check mark next to the Text Block2 - Text line the indication of the override?
Components are a new thing, and I think the Webflow team is still making adjustments while they settle in to the framework. They’re a big change and a lot of users have had difficulty adjusting to the massive UX changes surrounding them.
I hadn’t even noticed the checkboxes- not sure if those are new, but that looks like a useful indication. I see the Purple property binding reference at the top and the Disconnect, and those are my indications that it’s bound. Also the fact that you cannot double-click edit it in the Component master view.
As to how it happened, I haven’t dug in recently on exploring where Components are at, but at least originally, if you edited an instance element it would automatically create and bind a property, which confused the heck out of everyone.
ALT-DOUBLE-CLICK on the component, or clicking the Edit Component button in the top right corner are the ways to get to the master component.
It’s easy to master, once you know the rules, and I’m hopeful there is some sound reasoning behind all this added UX complexity, like the future introduction of 3rd party packaged “smart” components? Or possibly the ability to build your own smart components using Webflow’s new React development feature set?
I’m just guessing here, but I’ve not seen Webflow invest this much effort in a single part of the platform before, and it just doesn’t make sense to me for the current “instance overrides” feature set alone.
