Font changes will not push to live environment

  • Resolved mstrgntlmn

    (@mstrgntlmn)


    1 year, 6 months ago

    I am trying to make sitewide font changes. I have edited my CSS in VSC to the following:

    @media (min-width: 1200px) 
{ h1, h2 { font-size: 3.25rem } }

    When I push this change (the font-size was 6rem), it takes effect in my Staging environment:

    But not in the live environment:

    I have pushed the changes to both servers, cleared cache in Kinsta and WordPress, pushed the staging environment to the live environment in Kinsta. There have been other changes made, like swapping out images, and those all update fine, it’s only the font-size changes. I’m aware there could be rogue CSS screwing things up, but then the issue would be present in both environments, right?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Moderator bcworkz

    (@bcworkz)

    You’ve apparently flushed server side caching. Have you also flushed your browser’s cache? I frequently need to do so on various sites where I’ve updated the CSS. CSS files in particular seem to be especially “sticky”.

    Thread Starter mstrgntlmn

    (@mstrgntlmn)

    Thanks for the reply. Yes, I have cleared cache browser side, tried it incognito, different browsers, different computers, etc. haha still no change unfortunately.

    Moderator bcworkz

    (@bcworkz)

    Verify the production server has the correct version of the altered CSS file via FTP. If it’s correct and you’ve flushed server and client side caches, the only situation I’ve seen where a page fails to reflect the change is when a reverse proxy service is involved and the proxy server’s cache had not been cleared.

    Thread Starter mstrgntlmn

    (@mstrgntlmn)

    Looks like I’ll be doing some research on reverse proxy servers. I just went in and verified that the production server does have the altered CSS file, so there must be something else blocking it. Why only the font changes? It’s still so weird to me. Anyway, thanks, I’ll look into that and see what I can find.

    Moderator bcworkz

    (@bcworkz)

    If you are unaware of having a reverse proxy, it’s likely you don’t have one.

    As you guessed earlier, some other CSS could be overriding your font rule. This would show up in your browser’s element inspector tool. Your rule would be struck through and the overriding rule would be shown along with its source. This behavior should be the same as in staging though, unless they are not identical installations. For example, if production runs a CSS optimizer but staging does not, this could cause different rules to have precedence.

    Thread Starter mstrgntlmn

    (@mstrgntlmn)

    It was the CDN cache in Kinsta that needed to be cleared. I had no idea there were multiple caches I had to flush in Kinsta. Thanks everyone for your assistance!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Font changes will not push to live environment’ is closed to new replies.