Release notes for WeBWorK 2.1.1

From WeBWorK_wiki
Revision as of 16:09, 29 February 2008 by Sam (talk | contribs) (New page: {{Historical}} == Introduction == This release introduces several improvements and release fixes many bugs in WeBWorK 2.1. Among the changes made are the following: === Enhancements ==...)
(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.

Introduction

This release introduces several improvements and release fixes many bugs in WeBWorK 2.1. Among the changes made are the following:

Enhancements

  1. Added a login privilege to the permissions system
  2. Update jsMath to 1.7e, including support for additional LaTeX environments
  3. Improved the mail merge user interface
  4. Improved the default stylesheet
  5. Added an option to rename the Change Display Settings submit buttton
  6. Added summary column to the scoring module for the total value of WeBWorK problems done
  7. Optimized checking of permission levels by caching the currently logged-in user's permission level
  8. Added several features to the classlist editor
    • ability to search on any data field (%BUG{664}%)
    • ability to define a subsort (i.e. first sort by last name, then by first name) (%BUG{654}%)
    • warning is given when users with duplicate names are imported (%BUG{684}%)
  1. Added option to file manager to convert newlines on uploaded files
  2. Feedback messages now include course ID
  3. Leading and trailing whitespace is now removed on the add users page
  4. Added the ability to add a new, blank problem to an existing problem set
  5. Made changes to preserve problem display options across all pages
  6. Modified the default template to refer to the stylesheet by reference, reducing page load times

Bug fixes

  1. Fixed a bug where the Show saved answers option could not be turned off
  2. Fixed a big where an incorrect error message would be given when a database error occurred
  3. Fixed "uninitialized value" error in grading (%BUG{733}%)
  4. Fixed a bug where a weight of 0 would appear as a blank (%BUG{730}%)
  5. Fixed a bug where fun_cmp would give the error "This answer is the same as the one you just submitted" after a preview operation (%BUG{557}%)
  6. Fixed a bug where the parameter user would be defined multiple times in a form or URL
  7. Fixed a bug where non-overridden date values would be displayed as 12/31/1969 on the problem set detail page
  8. Fixed several bugs in the file manager
  9. Fixed a bug where the scoring page would crash and burn if no set was selected (%BUG{750}%)

Availability

WeBWorK 2.1.1 is available our CVS repository. Read WeBWorKCVSReadOnly for more information on how to set up a CVS connection. For those who already have a CVS connection, this update can be obtained by updating to the release: rel-2-1-patches

WeBWorK 2.1.1 is also available in tarball form from our SourceForge project page: http://sourceforge.net/project/showfiles.php?group_id=93112

We recommend you also install PGLanguageRelease2pt1pt1 at the same time you install WeBWorK 2.1.1.

Installation

Read the section in the installation manual on Upgrading WeBWorK.

Changes were made to the configuration global.conf.dist in this release. Be sure to compare your existing global.conf file with the new global.conf.dist file and make any changes necessary. The utility diff3 may be useful to you.

Help

If you need help installing or using WeBWorK 2.1.1, 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 http://bugs.webwork.rochester.edu/. We can't fix bugs and add features if you don't tell us about them!

Patches

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 - 08 Feb 2005