I'm working on a Rails app and was updating a page.
The page has a whole bunch of background images defined in css. When I refreshed the page (cmd+r on the mac), nothing changed. When I went into the Chrome inspector and unchecked then rechecked the css rules, the images appeared. Also, if I opened a new private browsing window (cmd+shift+n), the images all correctly displayed.
Am I running into some weird kind of cacheing issue?
Chrome: Version 21.0.1180.89
Mac OS X: 10.8.2
You need to do a hard refresh that bypasses the browser cache. I don't know the key combination on a mac, but it's probably similar to Windows: ctrl-shift-R. This is not the same as a normal refresh (ctrl-r on Windows) that does not bypass the cache.
Aparently on a Mac the equivalent key combination is cmd-shift-r.
Try forcing the browser to load your new css file. I usually add a query string (?v=1.0) to the link, like this:
<link rel="stylesheet" href="style.css?v=1.0" "type="text/css"/>
and then I change the number (?=1.1) each time I've done some changes in the css file.
This usually fixes it in Chrome.
Hope that helps!
I have this issue from time to time myself, especially when I am making lots of changes, I find clearing your browser cache works best, unless you have specifically set up some sort of caching.
Also make sure to check the "Disable Cache" is the inspector settings.
Screenshot taken October 10, 2016. Please update if changes have taken implemented by Google.
Command + Shift + Delete
Empty cache from the "beginning of time"
Related
I already attach query string to my url
"~/App_Theme/cssstyle/default.css?v=1"
but the style on the page was still not updated. In my IE's developer tool on css tab show both css file.
How can I fixed this problem?
Thank you in advance.
Each time you make a change and want to force the browser to fetch the latest version, you need to update the number on the end of your path, so something like:
"~/App_Theme/cssstyle/default.css?v=2"
then
"~/App_Theme/cssstyle/default.css?v=3"
etc. The number can be anything, it doesn't need to be sequential. It just tells the browser that a different version is required.
In your case, your changes are not visible because you are specifying a particular version of your file. If you remove the version number parameter from your path, then clear the cache, you should see your changes:
"~/App_Theme/cssstyle/default.css"
You can also press Ctrl+F5 to force the browser to do a 'hard refresh', which re-fetches all assets.
As a last resort (and a good habit to get into if you're developing) is clearing the cache regularly. In most browsers, you can do this with Ctrl+Shift+Del. You can also do this automatically in Chrome by selecting Disable cache (while dev tools are open), and leaving the dev tools open with F12
In most browsers it is Ctrl+F5, (on windows)
This is happening randomly out in the field. I am embedding the editor in a ASP.Net MVC application. When users clear their cache and restart the browser, it works again. Any ideas how to fix it?
You must convince your browser to clear it's cache for the icons.png image.
Go to htt://yoursite.com/path/to/ckeditor/skins/moono/icons.png
and then use Ctrl+F5 or Cmd+Shift+R (mac users) to tell your browser to not use the cache and fetch a new one, which will then be stored in the cache.
You CANNOT do this from the editor page for some reason, probably by the way that the css and image is loaded. And for me, this trick only worked in Firefox and not Chrome. However, if in Chrome you do Shift+Ctrl+N (new incogneto window) then go to your editor, you'll see that it is working. That's how your visitors will see it UNLESS they have the icons.png image cached in there browser as well. The only way to fix this is to change the URL of the image, which will require replacing the new url in the CSS file (it's the background image for all the buttons).
I'm having problems with cache, I think.
I have a website in Joomla, and I have some .css (layout.css, position.css, .... ) and I have at home of the website, 3 buttons, I tested in localhost, and when I see the home well, I upload everything to production, to my server.
Now, I just edited some styles of these buttons, for example, the width, in order to see them better...but I'm having a problem with the cache, because sometimes I see them with new changes, but other times I see with the old styles.....I realized that this happens especially with chrome
Could you help me, please?
Best regards, Daniel
You can force the browser to use the latest stylesheet. Read more here:
http://www.impressivewebs.com/force-browser-newest-stylesheet/
I hope that helps.
Try delete cache data when new version is done, see hint.
In FF you can delete cache data by use a combination of keys Ctrl+F5.
Chrome is an awesome browser but the cache is a bit of pain, I use the incognito mode as this also switches off the cache from my experience.
I have looked into this time and again and have read solutions but they simply do not work.
Supposedly, one can bypass the cache in Chrome by hitting F12, clicking the gear in the bottom-right corner, and checking "Disable cache." This does not work for me. I still get a page with cached CSS. In Firefox, I go under Net and check "Disable Browser Cache" to no avail. HTML is not an issue, just the CSS and, possibly, JS.
IE, however, doesn't have this problem. I update the page's CSS and IE updates accordingly. For obvious reasons this is not an ideal situation.
I go to my-site.com/style.css in Chrome and Firefox and the file there is not the file I see with FTP/SSH/IE. If this looks like a bug (it does to me), then please let me know. If I'm just being dumb, then please tell me what I am missing. Please.
Thank you.
One way to avoid caching is to explicitly change the url in someway. What I would suggest is to append a querystring parameter to the css url like:
http://mysite.com/content/css/File.css?version=1234
and update the version or another way is to attach the DateTimeOffset instead of an auto incremented number.
I have a weird issue. I am opening a popup window in IE6 with SSL enabled on the server.
When the following executes it seems to lock the browser up. I know this is vague. This is the JScript that appears to be the problem. Gotta love your IE6!
function PopoffWindow(url) {
var features = "height=400,width=550,top=60,left=100,"
+ "toolbar=no,location=no,menubar=no,status=no,"
+ "scrollbars=yes,resizable=yes";
var win = window.open(url, "DSRocks", features);
win.focus();
return win;
}
This is not a problem in IE7 or Firefox. And the problem seems to be isolated to this server (with SSL). Anyone have any insight on this?
Thanks,
Nick
Is it possible that the window.open call does not return quickly enough to allow you to perform a .focus() on it, in the next line?
What happens if you throw an alert() between those two lines?
have you tried assign the window a name? IE6 sometimes does funny things when you open an unnamed window. just add a "windowName", before the url
With a problem like this, it is usually best to get back to basics. A few things to check:
How are you testing IE6? Are you using the Microsoft Internet Explorer Application Compatibility VPC Image or some workstation install where you've managed to get IE6 and IE7 working on the same PC? Having both IE6 and IE7 on the same PC may appear to work, but lead to issues like you are seeing. Even if you are using an existing VPC Image, you may want to download (or extract from an existing download) a fresh copy and see if it happens on that copy of IE6.
Have you cleared the Temporary Internet Files, Cookies and History of the IE6 install? I know it sounds obvious and stupid, but perhaps a resource that is being loaded in the PopUp window is corrupt in cache, causing the problem.
Have you disabled every Add-on in IE6?
I think the first thing to determine is whether the problem is with every copy of IE6, or just your copy of IE6 (covered by the first bullet point).
Grant,
Thanks. But the problem is with all IE6 instances that are viewing the hosted site. I will try to add an alert before the focus() to see if this is the issue. As for the windowname.. that is the second parameter I am passing, "DSRocks".
The problem was with a JSON webservice call. Please see this link for details:
http://codeclimber.net.nz/archive/2006/12/22/How-to-enable-an-ASP.NET-WebService-to-listen-to-HTTP.aspx