Friday 16th December, 2016
Editor 1.6.1 release notes
This is a relatively quick turnaround bug fix release due to a compatibility error that was found with versions of jQuery 1.11 and older. There are a couple of other small fixes that have also been identified since the 1.6 release.
For full details of the new features in Editor 1.6, please see the 1.6.0 release notes.
Downloads
Downloads of specific versions of Editor are only available to license holders. Please see the download page for information about the current release version.
Release notes
Fixes
- Javascript
- Compatibility error with older versions of jQuery (1.11 and earlier)
- Return key in a
textarea
should not submit the form - When using Editor without the
ajax
option, but usingidSrc
, a Javascript error would be thrown when editing data. - When the server returns a status code of >=400 for an Ajax request and valid JSON, regardless of if the
error
orfieldErrors
properties are set in the returned JSON, Editor will process this as an error. minDate()
andmaxDate()
methods would trigger an error if used before displaying adatetime
field.- If the JSON returned from the server doesn't contain a
data
property, don't throw an error as it might still be a valid reply (e.g. validation error).
- PHP
- If a primary key column is requested as a
Field
or in a modal, don't attempt to reselect it as this can result in an SQL error. - Oracle integration. Specify a return size for the primary key value when reading it. Required by PHP.
- Custom
Field->options()
function would result in a PHP error
- If a primary key column is requested as a
- Styling
- Improved styling for inline editing with Bootstrap
- .NET
- If a primary key column is requested as a
Field
or in a modal, don't attempt to reselect it as this can result in an SQL error.
- If a primary key column is requested as a
- Documentation
- HTML custom tags (
editor-field
) cannot be self closing. Updated the template documentation to reflect this.
- HTML custom tags (