GitLab

Showing the SecurityID in the URL is a bit of a security no-no.  Instead, we pass
it into the POST request as part of the ajax.  Note that this means that this request
requires JavaScript; in the scheme of things that's probably a slight benefit, given
that this action is a delete action.  We wouldn't want it accidentally followed!

fixing SS 3.1 deprecated issues

NEW: default the action that a new transition is created from.

BUG:  WorkflowFieldItemController::doSave() when the object is a newly created

BUG: when a edit form in WorkflowFieldItemController doesn't load a record, when saving it $form->getRecord() return null, so we need to reassign the the current $record to the object that this form is saved into.

I don't haven't tested this - but as the patch is simply checking for the existence of $record and Form::loadDataFrom() is expecting a DataObject, I'll can merge it.

BUG: add timeformat config as it has been removed from TimeField #8260

ManyManyList->removeAll() bug as listed http://open.silverstripe.org/ticket/8258

http://open.silverstripe.org/ticket/8258 

BUGFIX: set the receivers to the notifying email "To" list, rather than "Bcc" field, populate "Cc" field with current Member's email, leave "Bcc" not used for now.
BUGIX: given DataObjects' $summery_fields are so varied, and end-user of the module are likely know nothing about what is in $summery_fields, make all viewable fields to be available to notifying email template.

Don't create bad QueuedJobs when saving new records

The $definition argument is sometimes passed null, which violates the WorkflowDefinition type hint (at least in PHP 5.3.19). By making the default argument null, this issue seems to go away.

API Added creation of workflow defs from templates

MINOR: Added exhaustive HOWTO and updated VERSION file

BUGFIX: When no effective workflow is enabled, PHP Notice's were thrown ...

BUGFIX: When no effective workflow is enabled, PHP Notice's were thrown for undefined variable $uth on WorkflowEmbargoExpiryExtension
BUGFIX: WorkflowEmbargoExpiryExtension validation was kicking-in when scheduled dates were not filled-in; implemented getter+setter for effective workflow checking to prevent this
MINOR: Changed intro text on WorkflowEmbargoExpiryExtension depending on effective workflow

* WorkflowTemplate container class for defining workflow templates in config
  that will then be processed in code
* Added ability to select a template when creating a new workflow definition
* workflow actions created based on a structure defined in a template
* Added tests to ensure actions created properly
* Added config for simple review workflow
* Display workflow template description when viewing a definition with that template as its source
* Added getNamedTemplate method to service for locating a template by its name
* Trigger definition population directly via WorkflowTemplate's api
* Accept the definition as a parameter to createActions so that the actions
  get bound to the definition directly
* Actions get sort order populated immediately
* Added doco for yml config options
* Added simple test case for action creation
* Added description field for templates
* Templates can be specified in yml configuration
* Can specify actions + transitions (and relationship between the two)
* Can provide a description for the template, and a version number. Version
  number is not strict, but if different from the version stored, is assumed
  that there is an 'upgrade' that can be applied.
* Workflow definition indicates whether the workflow is bound to a template
  and allows user to selectively update the definition if the definition
  has been changed

MINOR: Updated changelog for v2.1.0

ENHANCEMENT: Workflow-definition buttons are shown disabled if current C...

ENHANCEMENT: Added validation on Embargo extension to show message when ...

ENHANCEMENT: Workflow-definition buttons are shown disabled if current CMS user does not have canEdit() perms on a workflow-definition (Issue #59)
MINOR: CSS tweaks to ensure button hover and focus states do not show when buttons are disabled

MINOR: Changed error display date-format to US format until such time as we can pull-in the current CMS-user's date/time format settings #47

ENHANCEMENT: Added validation on Embargo extension to show message when an embargo date already exists on a content-object (Issue #47)

Issues/47 b

BUGFIX: Fixed error on TreeDropDownField when selecting user-restriction...