2012-03-23, 05:53:40
Sorry not to have thought to turn on DEBUG, Connie. Will make sure I do that next time I run into trouble.
OK, so it was nearly 24 hours before I had time to take further action to investigate. I started off in Chromium again, and there was no problem at all - dialogues are now working fine.
I was certainly getting the problem last night, and I have certainly done nothing in the meantime to my server or the GS 3.1 installation. I'm also sure I haven't knowingly cleared Chromium's cache.
So, obviously I am full of joy that the site now works perfectly, and feel a bit of an idiot for not being able to pinpoint the problem. During today I was forming a loose theory around cookies, based on the fact that I had been logged into a GS 3.0 install which I replaced with a 3.1 install. Possibly there was a 3.0 cookie for the domain floating about causing problems? Other than being a rough guess, I recall similar issues when forgetting to enable site-wide cookies in GS 3.0 - always solved by clearing the browser cache.
OK, so it was nearly 24 hours before I had time to take further action to investigate. I started off in Chromium again, and there was no problem at all - dialogues are now working fine.
I was certainly getting the problem last night, and I have certainly done nothing in the meantime to my server or the GS 3.1 installation. I'm also sure I haven't knowingly cleared Chromium's cache.
So, obviously I am full of joy that the site now works perfectly, and feel a bit of an idiot for not being able to pinpoint the problem. During today I was forming a loose theory around cookies, based on the fact that I had been logged into a GS 3.0 install which I replaced with a 3.1 install. Possibly there was a 3.0 cookie for the domain floating about causing problems? Other than being a rough guess, I recall similar issues when forgetting to enable site-wide cookies in GS 3.0 - always solved by clearing the browser cache.