…person who would ever notice them.
…and a checkbox to the job profile. Make the profile prettier for the error message and whatnot, too.
…or "value" methods. Updated all calls to these methods that I could find. Kept the old method names around for backwards compatibility. Also added get_values() and set_values() to get the values for multivalue fields.
* Fixed favicon.ico. Not sure how long it has been broken. * Fixed publication of aliases when the aliased is published. I had a typo from when I implemented this feature last week that would have caused *all* stories to be republished. Oops! :-) * Fix for Bug # 981. Stories are now properly expired when the BRIC_QUEUED bricolage.conf diretive is enabled. * Fix for Bug # 982. The "Delete" button now deletes checked subelements in element profiles. * Fix for Bug # 984. Templates checked out of the library are now properly reshelved if the checkout is cancelled. * Fixed Bug # 989. Media created with the default "Image" and "Photograph" media type elements will now properly supply a "Lock val" check box for autopopulated fields. Fixed Bug # 990. Super Bulk Edit now works for media as well as stories. * Fix for Bug # 991. A media document cannot be related to an element unless it has a file associated with it. * Removed ancient debugging statement in the related_media component. * Fix for Bug # 992. The prompt for a password from the installer no longer echos the password to the terminal. Requires Term::ReadPassword. The installer will now also prompt for confirmation of the password. * When a template is moved to a new category, its ACL is now properly updated in the cached copy in the user's session, as well as in the database. * Fixed Bug # 966. When a template is moved to a new category, the old version of the template is undeployed when the new version is deployed to the new category. The versions in the sandbox are properly synced, as well. I'll be updating the bug reports in the morning.
The virtual FTP server now correctly creates a utility template when a template with an unknown name is uploaded. The virtual FTP server now moves templates into workflow when they're uploaded and puts them into the user's sandbox. This behavior allows the user to test the template changes without imposing possible bugs upon other Bricolage users. This approach is much safer than the previous behavior, which simply checked in and deployed a template upon upload. Teamplates can still be deployed via the virtual FTP server by appending ".deploy" to their names. The original behavior of always deploying templates upon upload can be restored by enabling the "FTP_DEPLOY_ON_UPLOAD" bricolage.conf directive. The virtual FTP server now pays proper attention to all permissions. Added "-k" option to bric_ftpd to kill a currently running virtual FTP server. This is made possible by the addition of the new "FTP_PID_FILE" bricolage.conf directive. These next two items address Bug # . Asset groups associated with categories are now activated or deactivated whenever their corresponding categories are now activated or deactivated. This prevents them from showing up in the permissions interface. Added a check box to the permissions interface to enable the display of inactive groups. This is primarily so that permissions can be modified on inactive category groups, since they still affect access to any documents and templates in those categories, even after they're deactivated. Added "ANY" fuction to be used with select parameters to story, media, and template (formatting) list. Pass a list of values to this function to have any of of them match for a given parameter. This is especially useful for matching on, say, a list of URIs or category IDs. This function is automatically available in templates
…hat it alone handles displaying error messages, and puts debugging information into HTML comments neither QA_MODE nor TEMPLATE_QA_MODE is enabled. I deleted error.html, which is no longer necessary. Also added an "element" attribute to Burner so that $burner->get_element should always return the currently-burning element, and added throw_error() to Burner so that template developers can throw nice exceptions for their users to see. This requires that all Mason template dhandlers be replaced, so I added a script to do so (copied verbatim from 1.2.0).
key_name attribute of elements rather than the has_name() method. Although has_name() is still supported, it really should be deprecated. At least it now compares whatever is passed to the key_name, as well. The name is now merely used for display purposes.
Using the "Check in to" select list on My Workspace to check assets into the desk they're already on will no longer remove them from all desks altogether. Bric::Biz::Workflow::Parts::Desk now does nothing when calls to its transfer() or accept() methods pass in the source and destination desks as the same desks. When templates are deployed from a desk, they now get a "Template removed from Workflow" event logged.
…in the database, but we neglected to put it in the burn root all those ages ago!