Forum Posts Feed
Forum bug?
< Next Topic | Back to topic list | Previous Topic >
Posted by Chris Murtland
Aug 1, 2006 at 01:49 AM
This problem has been fixed. My code initially assumed that a new user would only post one unapproved message then wait until being approved before posting more. Now the approval mechanism retroactively approves all messages by the user. Sorry for the mixup.
Chris
Posted by Jack Crawford
Aug 17, 2006 at 03:02 AM
Chris
Occasionally after I log in and go to a topic I find that the blue reply boxes are not visible. This is happening to me at the moment with the Index Cards Software thread.
I wonder whether it has anything to do with the fact that I often view the topics without logging in and then only log in if I want to contribute. The problem has happened to me several times.
Has anyone else seen this behaviour?
Jack
Posted by Derek Cornish
Aug 17, 2006 at 04:19 AM
Jack -
I use Firefox and find that after logging in I need to go back to the tabbed web-page of messages I was looking at, and refresh the page. The blue boxes then come up.
I expect the same thing happens with IE - pressing the back arrow goes back to the cached version of the messages, and the web-page has to be refreshed for the boxes to show.
Is this what you were referring to?
Derek
Posted by Jack Crawford
Aug 17, 2006 at 04:38 AM
I’m not sure Derek whether it is a problem with the log-in or just a simple need to refresh the screen regularly. I tend to read this forum on my work PC so it may also be something to do with the online set-up here.
I’ll keep an eye on it and report back if I think it something more serious. Thanks for your response.
Jack
Posted by Chris Murtland
Aug 17, 2006 at 06:28 PM
Jack,
I haven’t noticed this behavior before, but will look into it. Do you happen to know what browser and version number you are using at work?
Derek is correct in that using the “back” button to go back to the topic list after logging in generally won’t refresh the page so that it recognizes you are now logged in. I may be able to play around with caching behavior to remedy this.
Thanks,
Chris