Thanks, Well we've performed some experiments.
From the existing course, OLD, we've saved a classlist,
using this classlist we've created a new course, NEW,
built some problem sets and scored them. Everything worked.
Then we copied the OLD webwork_DB database file to
the NEW DATA directory and tried to look at the
section data from the NEW instructor page. This gives
compiler warnings of the sort here (and these were the same
compiler warnings as in the OLD course)
* Use of uninitialized value in pattern match (m//) at /usr/local/webwork/system/scripts/FILE.pl line 290.
##More details:
-------- main::dropStatus called at /usr/local/webwork/system/cgi/cgi-scripts/profCourseData.pl line 572
---- main::initializeAndLoadUp called at /usr/local/webwork/system/cgi/cgi-scripts/profCourseData.pl line 104
So we believe the webwork_DB file is somehow bad
(empty keys?, should we look in the .auth/keys file?)
in the OLD course. Could we read this file, say
in perl, print the good data back into a database
and toss out the bad data?
Andy Vogel
Syracuse University
<| Post or View Comments |>
|