Bricolage Content Management System

Preview works again (it was broken only during 1.6.3's brief life).

Document and contributor type field information (label, options) is no longer pushed through Locale::Maketext, thus preventing errors when element and contributor type administrators create field options with brackets in them.

Documents associated with categories that have been deleted will once again work properly. Even though a category may be deactivated, any documents previously put into that category should still work, and still treat the category as a working category. And so they do.

Permissions granted on the All groups work again.

Resize now works in super bulk edit.

When a template is deployed, Bricolage now checks to see if its file name has changed since it was last deployed, and if it has, it deletes the old file.

Optimized performance of Bric::Dist::Resource queries and wrote lots of tests for them.

When a story or media document is published, Bricolage now looks to see if any files distributed for previous versions of the document are no longer associated with the document, and expires them if they are. It does so on a per-output channel basis, so note that if output channel settings have changed since the document was last published, the expiration may miss some stale files. The same goes for when destinations are changed. But this should cover the vast majority of cases.

Text input fields no longer impose a default maximum field length. This is so that element fields that have their maximum length set to 0 can truly be unlimited in length.

Passing an undef via the workflow__id parameters to the list() method of Story, Media, or Template once again causes Bricolage to correctly return only those assets that are not in workflow.

Extra blank lines between subelement tags in super bulk edit no longer causes an error.

Searches no longer return unexpected results or all objects when pagination is enabled.