Release notes for WeBWorK 2.3.2

From WeBWorK
Jump to: navigation, 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.

Contents

Introduction

The WeBWorKTeam is pleased to announce the release of WeBWorK 2.3.2. This version builds on WeBWorK 2.3.1, adding several bug fixes and low-impact feature enhancements. Changes include:

  • Fixed a problem where the mod_perl.pm module would be loaded under Apache 2.
  • Fixed a problem with listing problems from an existing set in the Library Browser. See %BUG{1110}%.
  • Improved the error message given by the Grades module when a scoring file does not exist.
  • Fixed some typos in the parser documentation.
  • Set SMTP envelope sender to $ce->{mail}{smtpSender} rather than sending user's email address. This prevents some mail servers from rejecting the mail for having a forged sender address.
  • Make the transaction log a system-wide log rather than a course-specific log. This works around the problem described in %BUG{1333}%.
  • Fix a problem in which problems from unassigned sets could not be previewed on the Problem Set Detail page. (The error message was "odd number of elements in hash assignment". See %BUG{1190}%.)
  • Added an optional JavaScript file that blocks excessive page reloads caused by holding down the F5 key in MSIE. See %BUG{1209}%.
  • Fix a problem where jsMath expressions could overlap other page elements, making them unclickable.
  • Replace underscores in set names with spaces in the links menu.
  • Improve error message given when no recipients are selected in mail merge. See %BUG{1130}%.
  • Perform format checking on From and Reply-to addresses in mail merge. See %BUG{1131}%.
  • Improve error reporting when sending an email to a user fails: errors are now reported by email to the professor and also logged to the Apache error log. See %BUG{1120}%.
  • In mail merge preview, wrap text to 80 columns. See %BUG{1147}%.
  • Allow WeBWorK to exist on the root of a server. (That is, http://your.server/ would be the WeBWorK home page.) See %BUG{1150}%.
  • Updated bin/check_modules.pl to take an apache1 or apache2 argument, controlling which Apache modules are checked for. See %BUG{1151}%.
  • Improved error message in bin/check_modules.pl when an executable is not found. See %BUG{1153}%.
  • Added support for external authentication mechanisms.
  • Added support for the Cosign authentication system.
  • Update jsMath to version 3.4a. See the jsMath changelog for more information.
  • In the file manager, show a directory listing when a directory is being deleted. The listing will show the total number of files in the direcotry, and the top level contents of the directory (with numbers of items in the each subdirectory listed, but not the contents). See %BUG{1246}%.

Installation

WeBWorK 2.3.2 is available from our CVS repository, or as a tarball from our SourceForge file release page. We recommend that you install from CVS. Keep in mind that because of the layout of files within the webwork2 directory tree, upgrading an existing installation is harder using a tarball than using CVS.

Installation instructions are available from InstallationManualV2pt3.

You must also have PGLanguageRelease2pt3pt2 installed. The installation manual also covers installing PG.

Upgrading

If you are upgrading from WeBWorK 2.2.x, you will need to upgrade your database. See "Automatic" database upgrades in the installation manual.

If your are upgrading from 2.3.x, note that 2.3.2 requires the Email::Address Perl module. Install this module before upgrading. Refer to the installation manual for information about installing Perl modules.

If you want to move your WeBWorK installation to the server root (so that http://your.server/ will be handled by WeBWorK), you must update your webwork.apache-config (if you are using Apache 1.3) or webwork.apache2-config (if you are using Apache 2) from the new .dist copy. If you do not wish to take advantage of this new feature, you don't have to update those files.

If you use the transaction log, note that is has changed from being a course-specific log to a system-wide log in global.conf.dist. Update your global.conf accordingly.

Help

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

Bug Reports & Feature Requests

Please submit bug reports and feature requests at http://bugs.webwork.rochester.edu/.

-- Main.SamHathaway - 15 Jan 2007
-- Main.SamHathaway - 05 May 2007 (updated for release)

follow us