Bricolage 1.8.7 Released
2005.10.24
Update: Due to a couple of fatal flaws in the handling of media documents, Bricolage 1.8.7 has been superseded by 1.8.8. The improvements listed below remain relevant in Bricolage 1.8.8.
The Bricolage development team is pleased to announce the release of Bricolage 1.8.7. This maintenance release addresses numerous minor issues in Bricolage 1.8.6 and adds a number of improvements, including bulk publish and templating fixes, as well as PostgreSQL 8.1 support. The most important changes include:
Improvements
The installer now prefers typical installation paths over those in the
$PATH
environment variable when searching for Apache and PostgreSQL installations. This is to favor servers installed manually over those included with the operating system. [David]Added a partial index on the
comp_time
column of the job table so as to speed up lookups of jobs yet to be completed. This was originally in a 1.6.7 upgrade script, but never made it into the SQL for new installations. Suggested by Mark Jaroski. [David]The Bulk Publish feature in the UI now only publishes the previously published versions of unexpired stories and media, rather than the latest version of expired and unexpired stories and media, thus avoiding errors when documents are checked out. [David]
If a story passed to the
burn_another()
orpreview_another()
burner methods is the same as the story currently being burned, it will no longer be published or previewed again byburn_another()
orpreview_another()
, thus mitigating the possibility of infinite loops. [David]Added an
Expired
event for when stories and media are expired. Suggested by Joshua Edelstein. [David]
Bug Fixes
The installer now prefers typical installation paths over those in the
$PATH
environment variable when searching for Apache and PostgreSQL installations. This is to favor servers installed manually over those included with the operating system. [David]Added a partial index on the
comp_time
column of the job table so as to speed up lookups of jobs yet to be completed. This was originally in a 1.6.7 upgrade script, but never made it into the SQL for new installations. Suggested by Mark Jaroski. [David]The Bulk Publish feature in the UI now only publishes the previously published versions of unexpired stories and media, rather than the latest version of expired and unexpired stories and media, thus avoiding errors when documents are checked out. [David]
If a story passed to the
burn_another()
orpreview_another()
burner methods is the same as the story currently being burned, it will no longer be published or previewed again byburn_another()
orpreview_another()
, thus mitigating the possibility of infinite loops. [David]Added an
Expired
event for when stories and media are expired. Suggested by Joshua Edelstein. [David]
For a complete list of the changes, see the changes. For the complete history of ongoing changes in Bricolage, see Bric::Changes.
About Bricolage
Bricolage is a full-featured, enterprise-class content management and
publishing system. It offers a browser-based interface for ease-of use, a
full-fledged templating system with complete HTML::Mason, HTML::Template, and
Template Toolkit support for flexibility, and many other features. It operates
in an Apache/mod_perl environment and uses the PostgreSQL RDBMS for its
repository. A comprehensive, actively-developed open source CMS, Bricolage has
been hailed as quite possibly the most capable enterprise-class open-source
application available
by eWEEK