Faculty have been getting occasional but deadly alternating 'line 86' and 'line 31' IE script errors when clicking on an active comments button in the faweb gradebook. They have to exit from faweb and log back in to be able to get access to that student's comment text field. BB tech support (Eric Marriott) is currently working on the problem to no avail so far. I understand that at least one other school is getting the same errors. Are you at your school? Any idea what specifically happens leading up to the error? Thanks in advance for any info on this! Sincerely, Michael Moulton [Email Removed]

Yes. Have been getting line 31 and line 3 errors that have really hurt. Often teachers have lost data as a result. Ours have also had to log out, log back in. I created a case today about this as well.

Thanks for the info on your school's situation. A tech support person named Charles Rhyne was able to duplicate the problem on a server at BB and is getting the programmers to work on it. When I spoke with the programming group in a conference call last week, they were not sure what to do to fix things but now, with a server at their office able to duplicate the problem, a solution might be forthcomming. I know what you mean when you say it really hurts. Faculty work so hard to write comments that losing them is not something we want happening to them! - Michael

Here's the latest on this BB FAWEB bug. The email from a BB rep pasted below shows how to reproduce the script error messages. I tried it and it is a way to cause the faweb system to fail. There may be others. They send me two files from the lead programmer (Charlene) as a fix but they brought down the faweb system (wrong permission settings on the files). Once I got them working, they made a new pop-up window (model) problem...the 'ready' pop-up window showed up blank on some connections. They told me to take their fix files out and to instruct faculty to only access the site from one address (not use the ip of the server or any other working alias). I made an index.htm file and set it to be the default at /faweb to redirect people, no matter where they come from, to one solid faweb URL to try to avoid the bug. They are letting me know if this will negatively effect other things in faweb. Let me know if more info on this approach would help anyone out there. Trudy Wilson from BB emailed that they have a new fix but that they can't get it to us in time for our next grade reporting period (a big, end trimester one that happens over the thanksgiving break). They say they can't support us through the problem during our reporting weekend if faculty end up losing comments without paying for a new 'billable service.' They are also not giving any indication if suggestions schools are asking for will ever get into the development cycle. They may in the end but I wish I had something...anything...I could tell my faculty and administration. I think their tools work but navigating the way they do business is proving to be difficult. My teachers really wish that the interface was less fancy with a straight-forward forms page to put info into. The modal pop up windows have this bug, are slow, seem to require very specific browser software, and make it harder for faculty to enter in their comments. An import/export option would really help those with slower connections too. I wonder where all this will go!? Michael Moulton William Penn Charter School [Email Removed] (215) 844-1800 x192 --------------- Date: Wed, 19 Nov 2003 09:55:50 -0500 From: "Trudy Wilson" [Email Removed]> To: [Email Removed]> CC: "Katherine Robson" [Email Removed]> Subject: Steps to duplicate All headers Good morning Michael, As promised, here are the steps are programmer took to duplicate the script error: From the first machine log on with one url. 1. Visit the gradebooks tab. 2. Click in a column to enable the comments button 3. Log into another machine using a different URL (I the server's IP address instead of \\Charlenecu). 4. Visit the gradebooks tab. 5. On the first machine, click the comments button. Please let me know if you have additional questions. Regards, Trudy

Hey Michael, I know the new patches for script errors have been sent to you; they were sent to us as well. Have you installed them, and have they fixed the errors? Good luck with your reporting period wrapping up. Hope that bug is gone! Let me know. Our next period ends Dec 12, so really I was waiting to see how the patches worked for you before we loaded them. Happy Thanksgiving!!!