Hey guys. To let you know, I've enabled browser caching. I may have put it in a little too aggressive and you may see old versions of pages, even after you post a new message, etc. Simply hold down shift while you refresh the page to get an absolutely new version. I'm still working on the issue, so you shouldn't have to worry about it for too long.

Thanks,
MM

Update: I've made some changes, so please hit me up if you still see issues.

Can you not just enable browser caching for certain types of content (ie: Jpegs, movies, etc) or only mobile devices determined by the browser agent string?
I purposely turn off any caching on my pc's/laptops to ensure a fresh copy of a page is always delivered. Why not in the age of high-speed connections?
And it helps to keep hard drives from filling up because of bloated cache folders - mentioning no names *cough*Chrome*cough*IE*cough.

Or you could simply enable HTTPS and that sorts the caching problem. Enabling this really should be a consideration for the future anyway, considering Google are prioritising HTTPS sites in their search results.

Sorry to geek-out there for a minute - back to messy business now

Katie x

This is exactly what I've done as of this morning; hence this post...
MM

Strangely, I'm still experiencing an issue when loading the site using Internet Explorer, but not when using Chrome. The issue only came up over the past few days, so I don't know that it's something on my end.

(Also -- on an unrelated note -- Chrome has never loaded up the chat ribbon situated on the lower part of the screen.)

Have you tried emptying your cache on IE? Otherwise it might not know to start checking for fresh pages again. Don't know what's up with the chat bar... I develop most on Chrome and it's OK on my end... are you on the latest version? Anybody have this prob?

I did that for IE, and set it to refresh in perpetuity, though now it'll be a bit of a pain to put my login information each time. :/

But things are looking up. I resolved the Chrome issue. It was the fault of an extension.

Hmm we are telling your browser not to cache pages; Only content. Hopefully you shouldn't have to have it set that aggressively?

Could be. But with the issue resolved with Chrome, I'm more than happy to abandon IE altogether. So if nobody else is having the problem then I'd say you're in ship shape.