Slowhand wrote:
[quote]Excuse me for jumping in here.
akpoff, don’t you agree that the members shouldn’t have to do all this troubleshooting? If I were having this problem, there’s no way I would even attempt to try any of this stuff. I’m a complete idiot when it comes to computers (my hubby is the expert).
Will there be a ‘fix’ for this for everyone down the road?[/quote]
Sadly even if the javascript or page was set to expire, or have set for “no cache” so your browser is forced to get the newest version of a page/script/css/etc; browsers now are trying to automate everything to cause less server load, so have ways around even “no cache”, and the browser will not do a forced refresh of the page elements even when told to by the server.
So the problem is with client software (browsers) trying to help users too much that they forget, that storing pages isn’t always helpful on a site that gets frequent updates.
I don’t know many websites these days that can/should be cache locally, but there are probably a few like archive sites. Otherwise a user is suggest to disable caching/storing of web pages locally with the way browsers run these days in order to prevent hitting this speed bump.
It is something OS and browser manufactures need to address.
The only real way he could make sure there is no conflict with older stored versions, is to use a new name that hasn’t been used before on this site for files, and that is an IT nightmare because the point of a CMS is to point to a “news.xxx” files and let the CMS pull up that file, and you just need to change the news file when you have new news and the software handles putting it in the right area and such.
Again, one of the major reason I hate suggesting to clear cookies, or cache, but since IE5+ and Mozilla2+ there has been problems related to cookies and stored versions of pages, that need to be addressed that even web2.0 won’t fix because the browser is not responding correctly.
I would suggest “clear all private data” for firefox, and make sure it clears it when it closes for stored webpages etc, and make sure windows empties the temp file folder when it closes to help prevent things like this.
Otherwise, as he said a CTRL+F5 (forced page refresh) should take care of the problem in most instances and force the browser to go to the website and make sure it has the latest version of the page to display to the user. B)
Maybe someone could sticky a news item and thread in the forum to remain stationary to help people with problems viewing things, and include some standard reasons/fixes for such problems in an FAQ manner. (granted not everoyne reads a sticky ot FAQ, but those who do will at least be able to hit CTRL+F5 on each page to try that as the least techincal fix for the problem at hand)