Drupal 4.4.1 release
The Drupal project has released version 4.4.1 of its open-source content management platform today. As no critical bugs have been identified, this is a minor bugfix and maintenance release. There are no new features in this installment.
As an open source software project maintained and developed by a community, Drupal is free to download and use. You can download Drupal 4.4.1 by clicking the link below:
Fixes and changes in Drupal 4.4.0:
- See the Drupal 4.4.0 release announcement.
Fixes and changes in Drupal 4.4.1:
- Bug #7135: fixed saving of comment viewing options in PostgreSQL.
- Bug #7406: fixed incorrect parameters being passed to the 'user delete' hook.
- Bug #7094: umlauts in ISO-8859-1 RSS feeds were not displayed correctly.
- Bug #6444: it was not possible to update the 'changed' timestamp of posts.
- Bug: deleting an RSS feed's news items did not reset the feed's cache status.
- Bug #7332: Chameleon theme - added some whitespace within the <body>-tag.
- Bug #6887: changed
fread()s for PHP compatibility. Used by
- Bug #4635: wildcard characters were not translated when searching for users.
- Bug #7161: the pager would occasionally get the 'last page'-link wrong.
- Bug #7163:
mt.getCategoryList()(blogapi module) should return an empty array by default.
- Bug: UTF-8 strings were not always truncated properly.
- Bug #7088: fixed incorrect comment links in the search results.
- Bug #7120: Pushbutton theme - made the title of posts the same size on home page as on the node page and improved the various header styles to give better visual indication of hierarchy.
- Bug #7121: added missing PostgreSQL update function to
- Bug #4765: fixed broken permission in the blogapi module.
- Bug #7110: some of the aggregator module's help text was never shown.
- Bug #7082: Pushbutton theme - corrected some font sizes as well as comment spacing.
- Bug: added missing
misc/forum-closed.gificon for closed forum topics.
- Bug #6982: fixed problem with 'page node' links.
- Bug #7045: made it possible to URL-alias links emitted by the tracker module by fixing the use of
For the most trouble free transition from an existing installation, it is recommended that you first upgrade existing installations to Drupal 4.4.0. If you are upgrading from Drupal 4.3.x or below, please consult the Drupal 4.4.0 release announcement for more information.
To upgrade from Drupal 4.4.0, upload all of the files and directories in the Drupal 4.4.1 package to your webserver, replacing older copies of the files.
- No database changes have been made since Drupal 4.4.0 so there is no need to run Drupal's upgrade script.
- No API changes have been made since Drupal 4.4.0 so all contributed themes and modules that work for 4.4.0 will work with 4.4.1.
Though, like with any upgrade, it is a good idea to backup your database first.
Bugs are best reported using the bug tracker rather than by using the comments below:
- A list of all pending bugs filed against Drupal 4.4.0.
- A list of all pending bugs filed against Drupal 4.4.1.
- Search the bug reports.
- Track changes in the stable DRUPAL-4-4 branch.
May 2nd: there was a problem with the packaging of Drupal because the DRUPAL-4-4-1 CVS tag was initially incorrect. As a consequence, Drupal HEAD got packaged instead of Drupal 4.4.1. This problem has been fixed.