CSS Not Publishing Correctly

I’m having issues with the CSS not publishing correctly to my site. I obviously performed a clearing of my local cache. I even loaded the site in various browsers and incognito and still the update isn’t there. I also made a content change on the site to see if that would help push the CSS change but no luck.

All I changed was the background image alignment for this site I’m working on. I changed from center point alignment to bottom middle alignment. See images below.

Local version:

Live published version:

I searched the forums but couldn’t find anyone with same exact issue. Would love some guidance!

Thanks.

It looks like the image is resizing to fit the width of the browser window.

If you share your public link I can find out more.

Here is the webflow design link: https://webflow.com/design/learnloop

And here is the public facing link: http://learnloop.co/

Thanks for looking into it.

And yes it should be fitting the width which is what I want. The issue I’m having is the alignment CSS updates are not publishing. The image tha tis live is cutting off her head, and I want the image to bottom align to that div so her head is always showing.

Hi Danny, I cannot see your public link as posted (see instructions on how to share a public link). In the web inspector the CSS is showing the hero image with the background-position as 50% 50%:

.hero-section {
  position: relative;
  overflow-x: visible;
  overflow-y: visible;
  height: 700px;
  background-image: url(http://uploads.webflow.com/545862fa72a66a8c2dd8c277/54586867a2207e922f31eb47_wonder.jpg);
  background-position: 50% 50%;
  background-size: cover;
  background-repeat: no-repeat;
  background-attachment: scroll;
}

If the problem persists try logging out of webflow and logging back in and then making the change.

Sorry here is the design share link: Webflow - LearnLoop

I checked the public link and it is also set to 50% 50%.

if you click the bottom arrow under preset does it change to 50% 100%?

2 Likes

You’re the man, logging out then logging back in fixed the problem for whatever reason :smile:
I’ll be sure to do that if this happens again in the future!

3 Likes