Bricolage 1.8.5 Changes

2005.03.18

Improvements

  • Made story profile's subelement Preview In output-channel list consistent with the top level one (e.g. editing a Page shows the same preview OCs as editing the Story at the top level). [Scott]

  • Added Linux startup script contrib/start_scripts/linux. [David]

  • Added version_id parameter to the list() methods of the story, media, and template classes. Oversight reported by Kang-min Liu. [David]

  • Distribution via SFTP is now atomic and respects the FTP_UNLINK_BEFORE_MOVE directive. Spotted by Patrick Michael Kane. [David]

  • Related story and media elements managed through the SOAP server can now use a combination of URI and site ID to identify related assets in addition to the existing approach of using story and media IDs. [David]

  • Email sent by Bricolage now set the send date, since our understanding is that the MUA is responsible for setting the date and some SPAM filters trigger on missing Date: headers. [Cameron Miller]

  • The media type manager now validates media type names to ensure that they are of the form type/subtype with no spaces. Suggested by Marshall Roch. [David]

  • When started up by the super user, the virtual FTP server now runs as the same user as the Bricolage Apache server. This should prevent malicious users of the virtual FTP server from being able to do things as the root user that they shouldn’t. [Keith Grennan]

  • SQL errors encountered when building the database are now fatal, meaning that they will cause the entire installation to fail, rather than continuing to execute SQL statements and build an incomplete database. This prevents the creation broken databases when people didn’t notice errors in the past. [David]

  • A list of subelements is now less likely to mysteriously become out of order and thus lead to strange action-at-a-distance errors. And even if they do become out of order, the error message will be more appropriate (Warning! State inconsistent instead of Can’t call method ’get_name’ on an undefined value). Reported by Curtis Poe. [David]

  • Updated mail list information in Bric::Hacker. Reported by Marshall Roch. [David]

  • The SOAP media interface now supports creating relationships between the media documents elements and other story and media documents, just like the SOAP story interface does. [David]

  • The SOAP interface now supports Related stories and media on story type and media type elements just as in the UI. This involved the somewhat hackish necessity for including the related_story_id and related_media_id (or related_story_uri and related_media_uri) attributes in the elements XML element, but it does the trick. [David]

  • The list of elements to select from when creating a new template is now in alphabetical order. [David]

  • The XML representation of media documents used by the SOAP server now supports the media type of the file. [David]

  • The multi install destination is now the default, rather than the single install destination. The two styles (multi and single) are now also better described during installation. [David]

  • Added the checked_in parameter to the lookup(), list(), and C methods of the story, media, and template classes. If passed a true value, this parameter causes the checked in version of the most current version of the story to be returned. When a story is checked out, there are two instances of the current version: the one checked in last, and the one currently being edited. When the C parameter is a true value, then the instance last checked in is returned, rather than the instance currently checked out. This is useful for users who do not currently have a story checked out and wish to see the story as of the last check in, rather than as currently being worked on in the current checkout. If a story is not currently checked out, this parameter has no effect.

Bug Fixes

  • Versions of Perl that disallow the use of the -I argument in a setuid environment will no longer cause the upgrade to fail. Reported by Serge Sozonoff. [David]

  • The new support for a false value to the checked_out parameter to the list() methods of the story, media, and template classes is now properly supported by the SOAP list_ids method, as well. [David]

  • Calls to publish documents via SOAP will no longer fail if the published_version attribute is not specified and the document to be published has never been published before. [David]

  • The Bricolage virtual FTP server will no longer fail to start if Template Toolkit is installed but its version number is less than 2.14. Reported by Adam Rinehart. [David]

  • Fixed a bug where nothing would ever publish if you had PUBLISH_RELATED_ASSETS enabled in bricolage.conf. [Mark]

  • Added slug to the list of attributes specified in the error message for a non-unique URI in a story. Thanks to Rachel Murray for the spot! [David]

  • Fix in the SOAP server code to adjust for changes in Exception::Class 1.20. [David]

  • Stories and Media created or updated via the SOAP interface will now associate contributors of the appropriate type, instead of All Contributors. [Scott & David]

  • Deleting an element that has a template no longer causes an error. Thanks to Susan for the spot! [David]

  • Eliminated encoding errors when using the SOAP interface to output stories, media, or templates with wide characters. Reported by Scott Lanning. [David]

  • Fields with a an empty string or 0 (zero) for their values will no longer be displayed as Not defined when viewing a story. [David]

  • Reverting (stories, media, templates) no longer gives an error. Reported by Simon Wilcox, Rachel Murray, and others. [David]

  • Publishing a published version of a document that has a later version in workflow will no longer cause that later version to be mysteriously removed from workflow. This could be caused by passing a document looked up using the published_version to list() to $burner->publish_another in a template. [David]

  • The SOAP server story and media interfaces now support elements that contain both related stories and media, rather than one or the other. [David]

  • Attempting to preview a story or media document currently checked out to another user no longer causes an error. Reported by Paul Orrock. [David]

  • Desk asset buttons are no longer broken in non-English localizations. Thanks to Scott Lanning for the spot! [David]

  • Subelements will be properly deleted when selecting a Delete checkbox and clicking Save or Save and Stay in the story or media profile. It always worked in the element profile, and now it’s consistent across document profile interfaces. Spotted by Scott Lanning. [David]

  • Custom fields with default values now have their values included when they are added to stories and media. Thanks to Clare Parkinson for the spot! [David]

  • The get_desk_stamps() method in the asset classes has been deprecated (it never worked, anyway) and will be removed in Bricolage 1.10.0. The same goes for the required_satisfied() method in Bric::Biz::Workflow. Thanks to Marshall Roch for the spot! [David]

  • Subclasses of the media class no longer cause errors when distributing files via bric_queued. Thanks to Jason Edgecombe for the spot! [David]

  • Elements created via SOAP now correctly have site IDs associated with them. [David]

  • The All alphabetical search now properly escapes the % wild card character. Thanks to Frank Holtz for the spot! [David]

  • The bric_queued script now requires a username and password and will authenticate the user. This user will then be used for logging events. All events logged when a job is run via the UI are now also logged by bric_queued. [Mark and David]

  • Jobs now get a Job Created event logged when they are created. Reported by Rachel Murray. [David and Mark]

  • Eliminated Use of uninitialized value in pattern match (m//) warnings when uploading media files. Reported by Scott Lanning. [David]

  • Preview redirections now use the protocol setting of the preview output channel if it’s available, and falls back on using http:// when it’s not, instead of using the hard-coded http://. Thanks to Martin Bacovsky for the spot! [David]

  • The has_keyword() method in the Business class (from which the story and media classes inherit) now works. Thanks to Clare Parkinson for the spot! [David]

  • Templates that abort during calls preview_another() now properly abort when not using PREVIEW_LOCAL. [Paul Orrock]

  • Clicking a link in the left-side navigation after the session has expired now causes the whole window to show the login form, rather than it showing inside the nav frame, which was useless. [Marshall]

  • The names of media types (a.k.a. MIME types) can now be changed without encountering an error. Thanks to Marshall Roch for the spot! [David]

  • Media type MIME Type names are now properly required in the UI. [David]

  • Fixed typo in the virtual FTP server which was causing an error when saving a template. [Keith Grennan]

  • The JavaScript that validates form contents once again works with htmlArea, provided htmlArea itself is patched. See the relevant htmlArea bug report for the patch. As of this writing, you must run the version of htmlArea in CVS. [David & Marshall]

  • The JavaScript that handles the double list manager has been vastly optimized. It should now be able to better handle large lists, such as a list of thousands of categories. Reported by Scott. [Marshall]

  • Logging now works properly with the virtual FTP server. [Keith Grennan]

  • Some cases in which it was impossible to add actions to a destination have been fixed. Reported by Marshall Roch. Thanks to Jason Edgecombe for making available a server that exhibits the problem. [David]

  • The virtual FTP server no longer saves a template for every line in the template when the FTP client uses ASCII mode. Thanks to Keith Grennan for the spot! [David]

  • Reverting a template to a previous version now properly updates to the reverted version on the user’s sandbox. Also, canceling a checkout now properly removes a template from a user’s sandbox. [David]

  • When creating a new workflow, the workflow profile no longer forgets the selected site when you click the New Desk button. [David]

  • Changing a template in such a way that it will be deployed to a new location (by changing the category, for example) once again deletes the previous version from the previous location when it is deployed. [David]

  • Uploading a new image to a media document with a different media type than the previous image no longer causes an Imager error. [David]

  • Preview and views once again preview a story or media document as it was last checked in, rather than as it might be currently being worked on in a current checkout. [David]

blog comments powered by Disqus