Editor 1.2.4 release notes

Wednesday 23rd October, 2013

Editor 1.2.4 is an minor update to Editor, finishing off the 1.2.x series, in preparation for Editor 1.3.

Release notes

New: onInitEdit and onInitRemove callbacks pass the row(s) and data to be acted upon
New: Add the action type to the onPreSubmit and onPostSubmit events
New: PHP - SQL Server driver for Editor.
New: PHP, SQL Server - Support for server-side processing (SQLServer 2012+)

Update: examples - Update Bootstrap example to use Bootstrap 3.0.0 release
Update: examples - Local storage now uses the radio input type rather than select for fields.
Update: PHP - Improved error handling. Exceptions now have their message shown by DataTables' default fnServerData's error handling option (sError).
Update: PHP - database drivers 'swallow' errors to ensure valid JSON is returned

Fix: JS - Remove trailing white-space for JSHint
Fix: JS - dateFormat validator would not allow empty values (dateFormat_required) is the validator to use for required fields so this was little wrong.
Fix: JS - date fields which were added using add() after Editor had been initialised were not being correctly initialised as a date field.
Fix: JS - order() when called, when the form is visible has no immediate effect.
Fix: JS - Server-side processing with aliased names was broken
Fix: JS - The old DTValidate class was being incorrectly referenced. Should be Validate
Fix: JS - update for radio didn't select current value
Fix: JS - Checkbox update doesn't reselect current values - 14081
Fix: JS - Radio field type was always type casting as string, breaking boolean
Fix: JS - i18n with multiple instances used only the strings from the last instance
Fix: Docs - edit() example had a typo, was using the create() method!
Fix - examples: Bootstrap integration should use $().on() rather than the old $().live() method.
Fix - examples: Manager was not being correctly selected
Fix - examples: Deep object delete wasn't working due to an incorrect property read
Fix: PHP, Postgres - Table aliases would break the query due to invalid SQL