Release notes for WeBWorK 2.1.3
This release builds on WeBWorK 2.1.2 by adding a number of incremental improvements.
- Site wide message on login page (in
- New sorting options on Instructor pages. All sorts are now case insensitive.
- Ability to change password on Classlist Editor page as well a Instructor Tools page.
- Reformatted scoring files.
- Minor changes in navigation links.
- Import/export of courses is now made to gzipped files in the
templatesdirectory rather than being downloaded directly to the administrators machine. This is still very slow, but it avoids the problem of browser timeouts.
- Answer strings are base64 encoded to protect against problems of illegal characters in answers.
- There is a big speed increase on using the Set Assigner page.
- Courses can be renamed.
- Davide Cervone has contributed a number of additions to the PG capabilities. One related to the WeBWorK 2 codebase allows macro files to be located in directories specified in
global.conf. It is also possible to specify subdirectories: e.g.
WeBWorK 2.1.3 is available from 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 tag
WeBWorK 2.1.3 is also available as a tarball from our SourceForge project page: http://sourceforge.net/project/showfiles.php?group_id=93112
We recommend you also install PGLanguageRelease2pt1pt3 at the same time you install WeBWorK 2.1.3.
Read the section in the installation manual on Upgrading WeBWorK.
If you need help installing or using WeBWorK 2.1.3, 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!
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.MichaelGage - 10 Jun 2005
-- Main.SamHathaway - 24 Jan 2006 (rewrite from WeBWorKRelease2pt1pt2)