…t have to be a Global Admin to use it, but must have READ permission to the categories, and PBULISH permission to the documents to be published. Also fixed the category search to limit by site context only when that preference has been set. It's more efficient, too, leaving that filtering to happen in the database.
…ks to Safe.pm.
…ed, but it's all good. First, I allowed formerly secret group classes to be non-secret. This means that preference, alert type, and group groups can now be created and managed in the UI. Then I added the group doubleList manager interface to those profiles that were missing it: Preferences, Groups, Alert Types, Element Types, Keywords, and Contributors. Keyword groups actually weren't listing their members, but the do now. Contributor groups are the same class as Contributor Types. This is nasty, but can't be avoided. I added workaround code to change the display name of the class in the UI. One hack was to provide an optional third array element to the "addition" parameter to listManager.mc that contains the name of the object to be added. Yeech. Another hack was to make sure that new contributor types continue to be created as secret groups, so that they can be distinguished from plain old contributor groups. Hacks all around! And finally, I made the table of contacts in the alert type profile nicer, with the same border colors as similar tables in the UI. Oh, and the display and plural names of the group group class needed to be updated, and I added a script to make sure that existing contributor groups are all secret groups.
…ings for fields.
…ith SOAP errors.
…created, and templates should always be properly checked out.
…ter svn changes.
…s for roles other than the default role now store their values in the same way as the default role, which means the values can be properly fetched and updated!
interface better behaved: * Added a "key_name" element to the XML schema for Element objects. * When loading an element, the handler will convert the "name" element to the likely key name if there is no key name. It will also issue a warning. * Changed the schema for fields to have a "key_name" element instead of a "name element. * When loading an element, fields with no key_name element will use the old name element, instead. No warning will be issued, since as of Bricoalge 1.8 the field name used the key name, even though it was called "name". With these changes, I'm able to use XML for an element exported from either 1.8.0 or 1.8.1 without problem.
…you click a "View" link
…he preview root is properly used for its out_dir.
…uage object so taht an code that uses localization will work properly.
…ents now work.
When Bricolage discovers a document or template on a desk but not in a workflow, it now places it in a workflows associated with the same site as the document or template is associated with. Thanks to Serge Sozonoff for the spot! Aliases of Image, Audio, or Video media documents no longer remain stuck on desks. Reported by Serge Sozonoff. The C<has_member()> method of Bric::Util::Grp is now faster when searching for a specific group member.
…ar to escape newlines.
…ne with types associated with the same site as the workflow.
…o the "containerprof" ID.