Bricolage Content Management System

• Added reverse date sorting option on desks (newest items first). Suggested by Bret Dawson. [Greg Heo]

• Updated the Xinha include script to reflect latest Xinha updates. [Matt Rolf]

• Updated the SFTP mover to use the faster Net::SSH2, rather than the deprecated Net::SFTP. [Sarah Mercier, Matt Rolf, Charlie Reitsma, Michael Herring]

• The to_preview option to Bric::SOAP::Workflow->publish now previews a document for all output channels, not just the primary output channel. The same of course applies to the --to-preview option to bric_soap. Suggested by Terence Bodola. [David]

• Server errors sent in response to Ajax requests are now displayed in a modal lightbox widget, rather than just getting shoved into the DOM. Also, effects that should only occur on success (such as removing a story from a desk when you move it) now only happen on success. [David]

• Changed the behavior of Bric::Util::Burner->publish_another so that, rather than immediately publishing a document, it instead adds it to a list of documents to be published and then returns. Documents added to the list are then published when all other publish jobs in a given request have finished publishing. The upshot is that if you bulk publish 50 stories that all trigger the republication of a home page story, that home page story will be republished only once, rather than 50 times. A side-effect is memory consumption, so don't send too many stories to publish_another from your templates! Sponsored by NetStumbler and Kineticode, with production testing by the National Gallery of Art. [David]

• Removed the “Related Story” and “Related Media” sections of the element profile, as they are now included in the “Content” sections of the element profile, and therefore redundant. [David]

• The upload field for related media (available when the RELATED_MEDIA_UPLOAD bricolage.conf directive is enabled) is no longer displayed in the element profile. Instead, it is displayed in the “Edit” popup window, where you can now search for an existing media document or upload a new file. This eliminates a bug when more than one upload field was displayed in the “Content” section of a document profile. It also makes it clearer that you're editing a new, related media document, as the popup looks different than the main display window (in that it has no navigation bar). [David]

• Permission and conflict messages thrown by callbacks in response to Ajax requests now cause a lightbox to be thrown up with the message highlighted. This means, for example, that if a user tries to move a story they don't have permission to move, the story will not appear to be moved in the UI and the user will be told that she lacks the permission. [David]

• The “New Story” page now uses an autocomplete field to select a primary category. [David]

• Minor improvements to the dynamic display and handling of container elements in document profiles. [David]

• Related media and/or story subelements may now be toggled to show/hide them like any other subelements in a document. [David]

• Added the “displayed” attribute to element type and container objects. Setting it on a subelement type causes the value to be set on new containers based on that type. [David]

• Container elements in the document profile are now toggled open or closed depending on their “displayed” attribute, which persists across saves and versions. This means that the appearence of a document is the same as you left it, or as the user who last checked it in left it. [David]

• New container elements added in the document profile now cause the containing element to always be toggled open, and the newly added container is also toggled open. [David]

• The installer now explicitly sets permissions on the files it installs, rather than using the same permissions as the files have in the distribution. This is because a umask could force the unpacked distribution files to have permissions that are inappropriate for installed files. Reported by Roland van Ipenburg (Bug #1360). [David]

• The installer now sets the permissions on configuration files to `0640`, rather than `0644`, as before, so that the files are no longer world-readable on the system. [David]

• `make upgrade` is now better at determining the installed configuration, rather than making you select the database server and version of Apache again, it properly remembers the already-intalled configuration. [David]

Bug Fixes

• Fixed non-standard installation path being ignored if changed during “multi” installation mode. This was done by changing the defaults files to include the BRICOLAGE_ROOT variable. So when BRICOLAGE_ROOT is changed and the others are then evaled they get changed too. [Paul Orrock]

• Updated Bric::Admin to ensure that we have at least version 1.16 of Params::CallbackRequest so that we detect mod_perl 2 correctly when running Apache 2. [Paul Orrock]

• Trying to add an element to a document that has related media fields no longer causes an error [David]

• Server errors sent in response to AJAX requests no longer send a full HTML file in reply, just the error stuff. [David]

• Eliminated redundant “Relate” column from the search results when searching for a media document to relate. [David]

• The “Un-relate” link now properly unrelates media documents. [David]

• Fixed bric_dist_mon so that it works when Bricolage is running on mod_perl 2. Reported by Roland van Ipenburg. [David]

• Improved compatibility of the installer with certain Apache configurations where the apreq2 module might be named differently. Reported by Roland van Ipenburg (Bug #1359). [David]