Alan Turville wrote:Thanks Tom that seems to have sorted the problem
Actually... I think the timing here was coincidence, and now I believe it was the web server. We have since had a few reports of odd behaviour (including myself!). However, the not-so good news is that the host put our site on cache restriction without notice. What that basically means is that for some reason our site was using too many resources, and instead of pulling up information the way it should, the site was being cached into memory. The ONLY way for us to view the newest material was to force refresh (Control+F5) every page after it opened.
They temporarily put it back to normal for now, but I need to find the problem page(s) and fix it. I am still very angry about how this was handled and absolutely no notice was given to me so that I could look into it. Perhaps that is why they put it back for now, but I am still waiting for a list of pages causing the problem. Stay tuned!