Skip to main content
Inspiring
April 12, 2018
Answered

Active CSS values not going live when uploaded

  • April 12, 2018
  • 3 replies
  • 557 views

Hello!

I'm trying to debug a site that isn't loading the Bootstrap sticky footer correctly and I keep experiencing a very frustrating situation in which I make changes to stylesheets, upload them, reload the page in the browser, and NOT see the changes take effect.  I don't see them in the browser rendering OR when inspecting the elements in the browser's dev console.     I keep seeing the same CSS properties and values displayed in the dev console, although I can clearly see different properties and values  in the css stylesheet, at the same position referenced in the dev console.

I feel certain I'm uploading the right documents but I don't know if something has become mixed up with the DW Site or what else could be causing this.  Anybody have any ideas??

I'm using CS6.  Thanks!

    This topic has been closed for replies.
    Correct answer Jon Fritz

    It almost sounds like a sticky cache in your browser.

    Are you using Chrome by chance?

    If so, turn off caching in the dev console. When you hit F12 to open the console, across the top are items like Elements, Console, Sources, etc. click the Network tab and make sure Disable Cache is checked, then reload the page.

    3 replies

    P BAuthor
    Inspiring
    April 12, 2018

    Jon,

    Sticky cache it was.  Did as you said and it updated right away.  Didn't know that could happen.  Thanks for jumping in so quick and getting me unstuck!

    Do you happen to know if that setting will reset back to default everytime I launch the console?

    Jon Fritz
    Community Expert
    Community Expert
    April 12, 2018

    The setting will stick, however, it's only disabled as long as the dev tools are open.

    Once you close them to take a look at your page, it will start caching again until you open F12.

    P BAuthor
    Inspiring
    April 12, 2018

    Thanks again, Jon.  Nice to have the wind back in my sails.

    WolfShade
    Legend
    April 12, 2018

    To add to what Jon said, every time I make any changes, whether content, structure, or CSS, I _always_ refresh the browser using CTRL-F5 (I don't know what the Mac equivalent is) to grab fresh data and not use cached content.

    But certainly Jon's suggestion is a "one and done" solution, assuming cache is the culprit.

    V/r,

    ^ _ ^

    P BAuthor
    Inspiring
    April 12, 2018

    Wolfshade,

    Thanks also for jumping in and sharing that tip.  I didn't know I had the option of grabbing fresh content with just a couple of keystrokes instead of dumping all browser cache.  Thanks!

    Jon Fritz
    Community Expert
    Jon FritzCommunity ExpertCorrect answer
    Community Expert
    April 12, 2018

    It almost sounds like a sticky cache in your browser.

    Are you using Chrome by chance?

    If so, turn off caching in the dev console. When you hit F12 to open the console, across the top are items like Elements, Console, Sources, etc. click the Network tab and make sure Disable Cache is checked, then reload the page.