Release Notes: This release fixes a single bug introduced in 1.4.0 in which the tarball download was sending garbage.
Release Notes: This release makes the module compatible with Apache 2.4, implements a few cosmetic changes as well as RFC3803, and fixes a fairly long list of minor bugs. It also improves the overall performance of the module (reducing memory and CPU usage).
Release Notes: This release fixes an XHTML rendering error and a cosmetic bug in the recursive search display.
Release Notes: The XHTML+XML MIME type is now used for browsers that support it. Native language support was improved. Changes in libmp4v2's API were worked around. A minor bug that caused display fields to not be set properly in some cases was fixed.
Release Notes: This release fixes a single bug, by which playlists might be downloaded with random filenames.
Release Notes: This release introduces a reworked cache backend infrastructure, now used in the MySQL cache implementation, allowing for a single database connection per request. Together with improved table structure, this release makes the MySQL cache backend much faster. It also provides a German translation.
Release Notes: This release implements the new MP4 tag access system available in libmp4v2 since version 1.9.0. It also fixes a typo from a previous version that broke the local RSS icon, and fixes incorrect math in file size display computation.
Release Notes: This version adds a Dutch translation. It is also generated against working libFLAC files, thus fixing the build issues that people have been experiencing lately with FLAC support.
Release Notes: This minor release fixes two bugs: it prevents the module from potentially overwriting music files when the Web server is really badly configured, and it fixes a small glitch in the MySQL cache backend that would corrupt the cache when downloading tarballs.
Release Notes: This release introduces the long-awaited (yet still experimental) MySQL cache backend, along with a couple of minor bugfixes (wrong size during recursive search and improper display of certain buttons). The code has been further optimized, in particular to take advantage of the new backend capabilities. The memory footprint has been slightly improved.