Editor 1.7.1 release notes
Our first update of the Editor 1.7 series since it was initially announced focuses on addressing issues that have been found since that release. On the server-side the debug()
method has been modified to be able to pass your own messages back to the client-side, which is useful for debuging event handlers - simply enable the debug mode as before and then call debug()
with any messages or data you want to be able to see in the trace information.
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
New
- Javascript
upload
anduploadMany
now show "Processing" text on the upload button after the file has been uploaded and before the server returns the processed data. This can be controlled via theprocessingText
option for both field types.- Standalone editor now allows multi-row editing by passing an array of ids to edit.
- PHP
Format::DATE_USA
constant form-d-Y
date format.Editor->debug()
can now be used to add debug messages to send to the client-side. This can be useful for tracing errors in event handlers and other Editor callbacks. To send a message back simply call thedebug()
method with the data you want to send back (e.g. a string or an array). You need to make sure that you have the debug mode already enabled (->debug( true )
) for the messages to be sent to the client.
- NodeJS
- Add
types
option so TypeScript can pick up the included type files when compiling Editor.debug()
method which can be used to add debug messages to send to the client-side. This can be useful for tracing errors in event handlers and other Editor callbacks. To send a message back simply call thedebug()
method with the data you want to send back (e.g. a string or an array). You need to make sure that you have the debug mode already enabled (.debug( true )
) for the messages to be sent to the client.
- Add
- .NET
- 'Format.DATE_USA' short hand for MM-dd-yyyy date format.
Editor.Debug()
method which can be used to add debug messages to send to the client-side. This can be useful for tracing errors in event handlers and other Editor callbacks. To send a message back simply call theDebug()
method with the data you want to send back (e.g. a string or an array). You need to make sure that you have the debug mode already enabled (.Debug( true )
) for the messages to be sent to the client.
- Examples
- Soft delete example - don't actually delete a row from the database, but rather set a flag so it is hidden from the end user.
Updates
- JS
- Throw an error if
display
is set to something that is not a valid display controller.
- Throw an error if
- PHP
- Changing
debugSql
todebug
in the returned data to reflect that it can contain more than just the SQL
- Changing
Fixes
- Javascript
- Individual cell selection and editing wasn't working (multiItem example).
- If columns or cells were selected with Select, the delete button would be enabled, but rows couldn't be deleted. Please note that this fix requires Select 1.2.5 or newer.
datetime
will now not show the previous / next arrow icons if theminDate
/maxDate
is outside the range that can be selected (i.e. the user can't move on to a month they can't select from).- Changing Editor's key event listener (for return, esc, etc) to be
keyup
rather thankeydown
. The end user should notice basically no difference, but it allows external event handlers such askeypress
anddependent()
to listen for events before Editor attempts to modify the form (e.g. submit or close) - Throw an error when attempting to use standalone editor with an id that doesn't exist on the page
- Allow
ajax.data
to return a string of data to be submitted to the server on upload. - Bootstrap integration didn't correctly add a class for styling to
select
elements - JS error would occur if a primary key value was used which had an @ or # in it.
- Styling
- Bootstrap 4 styling for inline editing improved
- PHP
- Validation functions would cause an error with PHP 5.3.
- .NodeJS
- When compiling with TypeScript, knex doesn't use a default export, so an error was given
- .NET
null
data from an options list could result in an exception being thrownDbClean
usage without a field name specified would result in an error
- Examples
- Confirm close example should ask for confirmation of closure, even if the
X
box is clicked, or esc presses, when values are different - Correct label for time duration field in row reorder example (typo)
- Correct use of
columns.className
for field types example
- Confirm close example should ask for confirmation of closure, even if the
- Docs
- Incorrect example in
field().input()
documentation - Upload field types use
display
notrender
- Incorrect example in