Release notes for WeBWorK 2.0.1

From WeBWorK_wiki
Revision as of 16:57, 29 February 2008 by Sam (talk | contribs) (New page: {{Historical}} == Introduction == This release fixes two bugs in WeBWorK 2.0. # When course databases were upgraded, ''sets'', but not ''problems'', were assigned to the global user. Th...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
This article has been retained as a historical document. It is not up-to-date and the formatting may be lacking. Use the information herein with caution.


This release fixes two bugs in WeBWorK 2.0.

  1. When course databases were upgraded, sets, but not problems, were assigned to the global user. This caused sets appear to be empty when it was assigned to a user after the upgrade. Bugzilla bugs #611 and #614 are related to this issue.
  2. The date calculation routines before() and after(), used to compare the current time to the set dates, were not inclusive.


WeBWorK 2.0.1 is available our CVS repository. Read WeBWorKCVSReadOnly for more information.

WeBWorK 2.0.1 is also available in tarball form from our SourceForge project page:


Read the section in the section in the installation manual on Upgrading WeBWorK.

Fixing courses upgraded with WeBWorK 2.0

To fix corruption of courses upgraded with WeBWorK 2.0:

  1. Log into the course with WeBWorK 1.9 and delete the global user (usually called global_user).
  2. Log into the course with WeBWorK 2.0.1. You will be prompted to upgrade the database. Do so.
  3. If you had assigned sets to any users with WeBWorK 2.0, unassign and reassign the sets to each user.


If you need help installing or using WeBWorK 2.0, visit the WeBWorK discussion group and post your question there. The developers monitor this forum.

Bug Reports & Feature Requests

Submit bug reports and feature requests at We can't fix bugs and add features if you don't tell us about them!


While we welcome patches of any sort, by patching against the latest CVS code, you save us and yourself time. A bug in this release may be fixed in CVS, and we can more easily handle patches against the latest code. Check out the latest development version from CVS and patch against that. Consult the WeBWorKCVS topic for more information.

-- Main.SamHathaway - 23 Jul 2004