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() or preview_another()
burner
methods is the same as the story currently being burned, it
will no
longer be published or previewed again by burn_another() or
preview_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 Template Toolkit and HTML::Template burners work again.
[David]
* Errors thrown when setting element field values will now be
displayed as error messages within the context of the element
profile, rather than throwing a fatal exception. This is
useful for
invalid dates, for example. [David]
* The SOAP interface for categories now properly checks for
and sets
as appropriate the active attribute on categories being
created or
updated. Reported by Phillip Smith. [David]
* Updated for compatibility with PostgreSQL 8.1. [David]
* Defunct media files are now properly removed from the delivery
server whenever a media document's file name has changed.
Reported by
Brad Fox. [David]
For a complete list of the changes, see the changes list at
http://www.bricolage.cc/news/announce/changes/bricolage-1.8.7/.
For the
complete history of ongoing changes in Bricolage, see
Bric::Changes at
http://www.bricolage.cc/docs/api/current/Bric::Changes.
Download Bricolage 1.8.7 now from the Bricolage Website at
http://www.bricolage.cc/downloads/, from the SourceForge
download page
at http://sourceforge.net/project/showfiles.php?group_id=34789, and
from the Kineticode download page at
http://www.kineticode.com/bricolage/downloads/.
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.
Enjoy!
--The Bricolage Team
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() or preview_another()
burner
methods is the same as the story currently being burned, it
will no
longer be published or previewed again by burn_another() or
preview_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 Template Toolkit and HTML::Template burners work again.
[David]
* Errors thrown when setting element field values will now be
displayed as error messages within the context of the element
profile, rather than throwing a fatal exception. This is
useful for
invalid dates, for example. [David]
* The SOAP interface for categories now properly checks for
and sets
as appropriate the active attribute on categories being
created or
updated. Reported by Phillip Smith. [David]
* Updated for compatibility with PostgreSQL 8.1. [David]
* Defunct media files are now properly removed from the delivery
server whenever a media document's file name has changed.
Reported by
Brad Fox. [David]
For a complete list of the changes, see the changes list at
http://www.bricolage.cc/news/announce/changes/bricolage-1.8.7/.
For the
complete history of ongoing changes in Bricolage, see
Bric::Changes at
http://www.bricolage.cc/docs/api/current/Bric::Changes.
Download Bricolage 1.8.7 now from the Bricolage Website at
http://www.bricolage.cc/downloads/, from the SourceForge
download page
at http://sourceforge.net/project/showfiles.php?group_id=34789, and
from the Kineticode download page at
http://www.kineticode.com/bricolage/downloads/.
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.
Enjoy!
--The Bricolage Team