Okay, I'm still not clear on why they happened to implement user restriction in the manner they did. Still scratching my head. I swear they sold us a development version instead of a production one.
Okay.
Deep breath. Whining done.
So, my co-developer and I are working on bringing starlims10 up to a running state. We've been in its guts, turning things on and off, writing new code, etc. So, we are finally ready to showcase a little of what we have been working on and we pull a few people in to test it out. As they log in, we quickly find that they start getting an error message about UTC issues.
That started some head scratching.
After some digging (global search works nicely!) we tracked it down. Its was in the user session and connection procedures ran during the log in process. The way it was written was...different. It called itself, which is no problem: overloading is a natural programming function. It didn't pass the right parameters, though, on the second call...which may have been why it was breaking: hard to tell. A few modification, however, and we were in business. Issue solved.
So if you start getting UTC error messages start looking in the user session and log in code. You'll probably find your answer.
