Client Dependency Showing Different Stylesheets to Different Browsers?
We've got a 4.5.2 site that's using the ClientDependency stuff on the front end to combine and minify all the JS and CSS. We have a wierd issue where every now and then it will either serve up an older out of date version of the CSS (even though it was showing the updated version previously), and even more randomly today it was showing the latest version to all non-ie browsers, and anyone on IE got an older version. It's definitely not a browser caching issue, as we cleared caches, and tried accessing the site on machines that had never visited before.
Deleting the ClientDependency files in the App_Data folder makes it behave again, but then it will randomly flip out every now and again with the above behaviour!
Has anyone else come accross something similar when using ClientDependency?
CDF definitely doesn't do any browser checking whatsoever so this is strange. We've used this framework in TONS of sites and not come up with this issue. Where are you viewing the site from, same offices, different offices, etc... ? Many clients are hidden being server side caches which makes things horrible for us web devs. Instead of just clearing your App_Data folder, change the version in the config... thats why its there to clear all caches, even client side. Clearing the App_Data folder just clears your servers internal CDF cache. Changing the version in your config is a far better approach and is there for a reason.
You don;t have any IE conditional stuff in you HTML do you, often forgotten about and can do wonders to make you scratch your head as to why it looks different in IE :)
@shannon, that's what I thought, it's wierd that it happens for different browsers. The server is hosted in a datacentre, and we had the same issue for our main office, London office and clients offices in three different locations. Will update the version number from now on to see if that does the trick! The only thing that I can think of is that they might have set future expiry dates on the CSS folders, would that cause any issues with CDF?
Client Dependency Showing Different Stylesheets to Different Browsers?
We've got a 4.5.2 site that's using the ClientDependency stuff on the front end to combine and minify all the JS and CSS. We have a wierd issue where every now and then it will either serve up an older out of date version of the CSS (even though it was showing the updated version previously), and even more randomly today it was showing the latest version to all non-ie browsers, and anyone on IE got an older version. It's definitely not a browser caching issue, as we cleared caches, and tried accessing the site on machines that had never visited before.
Deleting the ClientDependency files in the App_Data folder makes it behave again, but then it will randomly flip out every now and again with the above behaviour!
Has anyone else come accross something similar when using ClientDependency?
CDF definitely doesn't do any browser checking whatsoever so this is strange. We've used this framework in TONS of sites and not come up with this issue. Where are you viewing the site from, same offices, different offices, etc... ? Many clients are hidden being server side caches which makes things horrible for us web devs. Instead of just clearing your App_Data folder, change the version in the config... thats why its there to clear all caches, even client side. Clearing the App_Data folder just clears your servers internal CDF cache. Changing the version in your config is a far better approach and is there for a reason.
You don;t have any IE conditional stuff in you HTML do you, often forgotten about and can do wonders to make you scratch your head as to why it looks different in IE :)
Something to check.
Pete
Thanks for the quick replies guys!
@pete, nope, I checked for conditional IE stuff.
@shannon, that's what I thought, it's wierd that it happens for different browsers. The server is hosted in a datacentre, and we had the same issue for our main office, London office and clients offices in three different locations. Will update the version number from now on to see if that does the trick! The only thing that I can think of is that they might have set future expiry dates on the CSS folders, would that cause any issues with CDF?
is working on a reply...