Editor 1.7.4 release notes

A bug fix release of Editor that addresses known issues. Also of interest will be the new ids() method which can be used to obtain the row ids of the items being edited, which can save some boilerplate code if this is information you need.

Please see the notes below for full details.

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
  • Add ids() method - this can be used to get the ids of the rows being edited or removed (or the indexes if creating a new row)
• PHP
  • Ability to set the PDO fetch type for the Result->fetch() and Result->fetchAll() methods (does not apply to Oracle or DB2 integration)
  • Support for Oracle 11g server-side processing

Updates

• Javascript
  • Automatically focus on the field input when clicking to edit multiple values
  • template() can now have null passed in as an optional parameter to remove the custom template and restore the Editor default.

Fixes

• Javascript
  • Trial version of Editor won't operate with an AMD loader as the define libraries were being obfuscated, resulting in an error (specifically in Webpack). The trial version no longer obfuscates the loaders.
  • Remove use of jQuery 3.3 deprecated functions
  • When editing a field that contains an array on a locally edited table, the aray values would incorrectly be merged. They are now correctly assigned to match the new array.
  • Form error and message information could be cleared when using jQuery 3 and switching between inline and full editing mode. This was particularly apparent when going from inline editing to the delete view.
  • Bubble and Inline editing would fail when used with a local editing table
  • Bootstrap 4 - pressing escape while the modal was being animated in would lock the display up.
  • Bootstrap 4 integration: When showing and hiding fields while the form was hidden, the form could look misaligned once then shown. This was because Bootstrap 4 uses Flexbox for grid layout, while display:block was being used to restore the field to being visible.
  • Bootstrap 4 integration - use is-invalid rather than has-error
  • Semantic UI styling displayed correctly only of the first action after a page load
• PHP
  • Oracle support for server-side processing on 11g (12c+ was already supported)
  • When using Options with an order statement where a field isn't included in the list to display, an SQL error would be thrown.
  • Allow for fields which have spaces in the database column name when binding parameters
  • SQL functions wouldn't be executed
  • Allow for / characters in SQL field names
• .NET
  • When using Options with an order statement where a field isn't included in the list to display, an SQL error would be thrown.
  • Allow for / characters in SQL column names
• NodeJS
  • Check that extended:true was used for the bodyParser and give an error if not.
  • Options.order() method would result in an error being thrown
  • When using Options with an order statement where a field isn't included in the list to display, an SQL error would be thrown.
  • Custom parameters for Node validation properties were not being applied