Forum Moderators: mack
Could it be the scripts have caused the problem?
Could be... hard to know without more information. :)
Whenever I suspect a new script/server change is causing a new problem, I will remove it/undo it and see if the problem goes away. Once you've identified the culprit, then you can begin dissecting it to further isolate the exact cause of the problem.
If so, why does it not affect all of our users?
You need more information about your users that are having the problem and your users that aren't experiencing the problem. What you don't want is to blindly make changes and hope the affected users stop complaining -- they may just stop trying. You need to build an accurate and repeatable test case so you can pinpoint the problem. That may mean installing a particular browser on a particular type of machine, or finding someone with that configuration to assist you.
What browsers? What operating systems? What sequence of events or sets of behaviors are triggering the problem?
Most users who are willing to notify you of a problem are willing to at least answer basic questions of browser and OS.
Make the problem repeatable, then start testing variations to solve the problem.
