[WWdevel] some 2.3 notes for you all (UPDATE)

[Sam H. <sh...@ma...>]

-- Apache 2 --

this seems to be working, but there are probably lingering bugs in  
code that doesn't get much exercise. have other people been testing  
it? it should probably be an "experimental feature" in 2.3.0.

-- WW/Moodle --

make Course Title/Institution optional in Course Admin (but also pre- 
fill these values from mod.html?)

improve wwassignment user experience a bit by creating the bridge  
object before showing the mod.html form. that way, we can check for  
and report the existence of the WeBWorK course in mod.html. if it  
doesn't exist yet, give a message like "The WeBWorK course SCH103  
does not exist yet: _Create WeBWorK Course SCH103_".

fix problems with teacher login in sql_moodle -- this might not be  
replicable, mike or i will check this. <http:// 
bugs.webwork.rochester.edu/show_bug.cgi?id=1043>

moodle cookies are sometimes(?) not being parsed under apache 2.  
probably has something to do with raw commas in the cookie. <http:// 
comox.textdrive.com/pipermail/wp-trac/2006-April/001297.html>

-- Gateway Testing --

Gavin says: "The Gateway mods are tested---by hand, by myself---but  
not extensively. Which may mean that they're stable, but I usually  
reserve that characterization for when something has survived a  
semester of use. There are two possibly remaining issues: (1) I  
managed to completely lock IE and Windows a couple of times when  
playing with it.  That didn't happen later in testing, and one of the  
times it locked was from the ProblemSets page, not in a Gateway test,  
so I'm not sure if it is a problem, or if it is, if it's a Gateway  
problem, an IE problem, or a WeBWorK problem; and (2) there's a  
complication when a user who is able to print multiple sets tries to  
print a gateway test: the multi-set selector doesn't show the set  
versions, which makes printing not work.  I'm calling it a known bug  
for now."

he added another database field: i'd REALLY like to have an automatic  
update mechanism in place so that adding this field wouldn't have to  
happen manually. see below.

-- Automatic Database Update --

wwdb_check does simple things like adding tables/columns/indexes,  
changing column types, and the like. this is sufficient for gavin's  
current changes.

i'll be adding a framework to that script to allow it to execute  
arbitrary Perl or SQL code to affect more complicated upgrades. for  
now, it'll be inside wwdb_check, but eventually it'll go into a library.