|
|
Version Notes - Beta releases of Discus 4.10

Version notes for the official releases of Discus 4.10. This will hold a technical change log of all code and template changes
in the beta versions of Discus and Discus Professional 4.10. For a more human-readable summary of the changes in Discus
4.10, please read the Discus 4.10 readme file.
|
 |
|
| Version |
Date |
Notes/Bugs Fixed |
| 4.10.1 |
03/14/2007 |
Discus 4.1 is a software update that includes several new features.
Spam Blocking: Protection against automated posts from "spam bots" including real-time blackhole list support,
CAPTCHA verification for public posts and user registration, and a collaborative spam signature system.
Redesigned Version Manager: Access to the new online update system, greatly simplifying upgrades and patches. Streamlined
design and "look and feel" with a check for installed Perl modules.
Board Summary Screen: The right frame in administration, when the board administrator logs in, will display a summary of the
discussion board's maintenance state, including a check to see if the software is up-to-date and a warning if a backup has not been
made within the last seven days.
Miscellaneous Enhancements: Exporting banned IP addresses to .htaccess file, greatly improved program diagnostics, blocking
of certain attachment types, better error logging, e-mail notification enhancements, better performance benchmarking, ...
|
Beginning with Discus 4.1, all code changes will be tagged with one of the following identifiers, in the level of severity:
SECURITY: Fix for a problem that would allow unauthorized access to a customer's server or restricted content on a discussion board via a problem in the software's coding.
BUG FIX: Fix for a non-security problem that has been reported by DiscusWare's developers or a customer, and has been reproduced and solved.
FEATURE: Addition of a new capability to the software product.
ENHANCEMENT: Change to an existing capability of the software product to improve its functionality, but not implemented as a fix for a security issue or a reported bug.
CHANGE: Miscellaneous back-end changes that will be transparent to all end-users and most board administrators. These generally deal with code cleanups and reimplementation or transparent technical changes to the back end code.
|
|
|