Can see site.css changes on local test browsers, but not online ...

[George DeLuca]

I'm using Dreamweaver 2021, MacBook Pro 12.7.6, macOS Monterey. Yesterday, I uploaded a full website to DreamHost. No problems. Here's the site: wheelerblockpress.com. Today, I haven't been able to upload the site.css file at all. It uploads without error messages but I don't see the changes online, only on the local test browsers. For example, I made changes and checked with Dreamweaver's Safari and Chrome test features and the changes were made. I looked on line and no changes. I contacted DreamHost and they showed me screenshots of the test changes as I made them. This is a very strange problem and I'm totally stumped after 11 hours trying to figure it out. 

[Ben M]

Can you provide details as to what should be changing and is not? From what you describe it sounds like it could be a caching issue, but without knowing what style changes we are looking for, it's hard to tell what version we are seeing.

Also when you upload the file via DW next time, can you enable the FTP log (Site->Advanced->FTP Log) to see if there are any notes when the file is uploaded. And if you haven't tried already, can you try another FTP program to see if the same results persist?

[George DeLuca]

Any changes I make to site.css don't process through to the live site. For example, today, I made a change in css, reducing a margin from 3rem to 2rem. The change happened on my screen in real time. I checked DW test Safari and Chrome and the change was successful. I uploaded the site.css file with the html file and nothing happened. 

Yesterday, I unplugged my modem twice, each time seemed to force the change in my online browsers. This morning I tried the simple change noted above, and nothing. I agree it's likely in the caching. Another clue is my phone renders the site exactly as described here. When the website finally renders in my online macbook browsers, that's when it renders on my phone.

[Ben M]

Any changes I make to site.css don't process through to the live site. For example, today, I made a change in css, reducing a margin from 3rem to 2rem. The change happened on my screen in real time. I checked DW test Safari and Chrome and the change was successful. I uploaded the site.css file with the html file and nothing happened. 

Yesterday, I unplugged my modem twice, each time seemed to force the change in my online browsers. This morning I tried the simple change noted above, and nothing. I agree it's likely in the caching. Another clue is my phone renders the site exactly as described here. When the website finally renders in my online macbook browsers, that's when it renders on my phone.

By @George DeLuca

Which specific rule did you change from 3rem to 2rem? I am seeing many instances of that value on margins so it's hard to determine if I am seeing it and it's just a caching issue or something with the file transfer.

Based on your current response that your modem unplugging was forcing a change, this could be a caching issue locally with your network. Are you able to utilize another wifi or go on a 5G wireless network to compare being on your local network vs. being on another network?

[George DeLuca]

That was just an example. The bottom line Is: the html uploads fine, but the css goes through the motions but nothing happens. To be clear, the css upload does not land on the server. You can probably imagine how irritating it is.

However, I did figure out a work around, one that I remembered using back in the 90s and early 2000s. I upload my file updates, then drag and drop the css file into its folder on the server, save and replace—done.  

[Nancy OShea]

Are you not being prompted to upload Dependent Files? 

See screenshot from Preferences. 

Using version-based filenames on HTML assets is a standard technique for cache busting, which forces web browsers to download the latest version of a file when it changes, rather than using the outdated, cached version.  So style.css becomes style-latest-version.css.  

[George DeLuca]

Thanks Nancy ...

Good catch.

George

[Jesus_Magana0501 · Accepted solution]

The problem is the "CACHE" on your browser.

You shoud REFRESH the webpage, but browsers normally open the page from the cache.

Force refresh on your browser:

MAC - CMD+OPTION+R reloads the page ignoring cache
WIN CTRL+SHIFT+R reloads the page ignoring cache as well as CTRL+F5    OR    SHIFT+ "Reload ICON" on your browser

In addition to it, if you want to review all your changes clear up the browser cache in Safary.

Enable the "Develop" menu by going to Safari > Settings > Advanced and checking "Show Develop menu in menu bar."

Then, click Develop > Empty Caches in the top menu bar.

Hope it helps!

Jesus M Renoud

[George DeLuca]

Thank you! That works!