Editor 1.2.2 release notes

This latest update for Editor focuses on addressing issues that have cropped up in the 1.2.x series and smaller new features. The new features include the node and order method which, respectively, will give you the field node (so it can be used else where such as inline editing) and get/set the field order. Also in this release is an enhancement to the PHP libraries which will automatically detect and respond as required to server-side processing requests from Editor, allowing Editor to work with massive data sets very easily.

Release notes

New

• New - API: node method - get the input container node for a particular field. This means you can potentially use the node else where in the document (inline editing for example).* New - API: order method - get and set the order of the fields, based on field names, in the form.
• New - init: Editor field containers can now have a custom class applied to them by using the 'className' property for field definitions.
• New - init: seperator option for the checkbox field type which allows the checkbox values selected to be submitted to the server as a string rather than an array (if given)
• New - Example: Example showing server-side processing and Editor in action.
• New - PHP: Database 'where' conditions can now be nested by passing in the first parameter as a function which is then called, with the action of the function being to add additional 'where' conditions to the query. The conditions added inside the closure, are wrapped by parentheses, giving the database layer now the ability to preform complex 'where' conditions.
• New - PHP: The Editor class will automatically detect and act upon server-side processing requests from DataTables. This means that in order to switch to using server-side processing with DataTables, when using the Editor classes, you simply need to add "bServerSide": true, "sServerMethod": 'POST' to your DataTables initialisation. The PHP classes will take care of the server-side processing implementation, allowing DataTables and Editor to work with massive databases (many millions of rows).

Updates

• Update - core: Fields are always inserted on display, in order. This allows ordering to occur, and also nodes to be used else where (see the above two new features).
• Update - core: Updating version numbering to semver - this only has an impact on development builds - no changes to releases
• Update - examples: Update all examples to use DataTables 1.9.4's mData rather than mDataProp
• Update - examples: All examples now have the new layout with tabs and extra information
• Update - examples: Adding more information about each demo such as displaying the PHP used, but also making the information more accessible by showing it in tabs.
• Update - docs: Small improvements to the requirements text
• Update - docs: Improve internal referencing in the documentation and make changes needed for the latest DataTables JSDoc template which now uses markdown.
• Update - PHP: Add implode and explode methods to the Format class which can be used with checkbox arrays that are submitted by the client-side.

Fixes

• Fix: IE8- had a display layout problem with fields which could cause them to stack incorrectly.
• Fix: If there is a field reported in error but there is no error status message we now simply show "Error". This shouldn't occur - it is an error on the server, but this at least avoids breaking the UI for the end user if it does happen now.
• Fix: The 'scroll to error' on submit error was broken due to an incorrect variable reference.
• Fix: The example given in the Editor class used the wrong variables for the TableTools initialisation
• Fix: If the first input element was disabled, IE8 would throw an error (12395). We now focus on the first visible, enabled input,select or textarea control in the form.
• Fix: Message and error API methods incorrectly were treating empty strings in the second parameter as form level messages, rather than the field level that they should have been (so it was impossible to clear errors).
• Fix: Don't throw errors on scroll to field error if the field is not displayed
• Fix - PHP: Required validation was broken unless the required type string length matched the required flag.

Web-site

• Web-site: Correct links to the self-referencing documentation