Skip site navigation (1) Skip section navigation (2)

ANNOUNCE: Bricolage-Devel 1.5.2

From: David Wheeler <david(at)kineticode(dot)com>
To: Bricolage Developers <bricolage-devel(at)lists(dot)sourceforge(dot)net>
Cc: Bricolage General <bricolage-general(at)lists(dot)sourceforge(dot)net>
Subject: ANNOUNCE: Bricolage-Devel 1.5.2
Date: 2003-04-03 00:37:01
Message-ID: AAC29190-656C-11D7-BD94-0003931A964A@kineticode.com (view raw or flat)
Thread:
Lists: pgsql-announcepgsql-general
The Bricolage team is pleased to announce the release of Bricolage-Devel
1.5.2, a release candidate for what will soon become Bricolage
1.6.0. Users of 1.5.1 are strongly encouraged to upgrade to 1.5.2, as
assets have an unfortunate habit of disappearing from workflow in 1.5.1.

In addition to all of the new features and bug fixes from the 1.5.0 and
1.5.1 releases, this version of the open-source content management
system fixes several significant bugs and tweaks a few important
features. The most significant changes include:

     *   Out of the box, the Story Editors, Media Producers, and Template
         Developers groups now have READ permission to access members of
         the "All Categories" and "All Elements" groups, which allow them
         to actually create assets based on elements and within
         categories.

     *   Workflow and Desk permissions are a little more sensible
         now. CREATE permission can be granted for the start desk in each
         workflow, instead of for the entire workflow. This allows a
         lower permission to be set on the workflow (e.g., READ), and
         then higher permissions on the individual desks in the workflow.

     *   New "Tuning" sections have been added to Bric::DBA.

     *   The default required length for usernames and passwords has been
         changed from 6 to 5. This is to make dealing with the default
         "admin" login easier.

     *   It is once again possible to delete elements when they are not
         associated with any story or media asset.

     *   Bric::Config now does its best to find a workable httpd.conf 
file
         during "make test".

     *   Previews of assets that are not checked out work again.

     *   Workflow and desk permissions relative to the assets they
         contain are now restored to their previous behavior. Desks no
         longer simply inherit the permission granted on any of the
         workflows they're in. This issue was resolved by creating a new
         secret asset group ID for each workflow.

     *   Assets will no longer appear to randomly disappear from
          workflow.

For a complete list of the changes, see the changes file at
http://sourceforge.net/project/shownotes.php?release_id=150544. Although
this release gives every appearance of being as stable as any previous
release of Bricolage, it does contain a fair bit of new code that needs
to be put through the ringer. It is, however, feature complete for
1.6.0, which we expect to release in the second week of April.

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 and
HTML::Template 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 "Most Impressive" in 2002 by
eWeek.

Learn more about Bricolage and download it from the Bricolage home page,
http://bricolage.cc/.

Enjoy!

--The Bricolage Team


pgsql-announce by date

Next:From: Robert TreatDate: 2003-04-11 14:18:26
Subject: PostgreSQL Weekly News - April 9th 2003
Previous:From: Robert TreatDate: 2003-04-02 17:06:50
Subject: PostgreSQL Weekly News - April 2nd 2003

pgsql-general by date

Next:From: Ryan MahoneyDate: 2003-04-03 01:03:46
Subject: Re: Postgresql capabilities question
Previous:From: John WellsDate: 2003-04-03 00:33:46
Subject: Postgresql capabilities question

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group