Search
181 results 81-90
General
- Editor 1.5.0 release notes › Release notes › Javascriptimportant for the DataTables download builder. New - JS: Integration
- Editor 1.4.2 release notes › DownloadsEditor 1.4.2 for PHP Editor 1.4.2 for .NET Editor 1.4.2 for JS+CSS only Downloads of specific versions of Editor are only available to license holders. Please see the download page for information about the current release version.
- Editor 1.4.1 release notes › DownloadsEditor 1.4.1 for PHP Editor 1.4.1 for .NET Editor 1.4.1 for JS+CSS only Downloads of specific versions of Editor are only available to license holders. Please see the download page for information about the current release version.
- Editor 1.4.0 release notes › DownloadsEditor 1.4.0 for PHP Editor 1.4.0 for .NET Editor 1.4.0 for JS+CSS only Downloads of specific versions of Editor are only available to license holders. Please see the download page for information about the current release version.
- Editor 1.3.2 release notesavailable on the DataTables download page. Details of all
- Require.jsload them from our download builder or include them
- Editor 1.4.0 beta release notes › Release notes › DocsFixes Fix - docs: submit() documentation updated to reflect the parameter passed into the success callback Fix - docs: Correct typo in postSubmit
- Editor 1.3.3 release notes › Release notes › FixesFix: Inline editing could result in making the table uneditable (until reload) due to an event listener not being removed. This was ultimately caused by the close method not being triggered. This was particularly noticeable if using tab control or the Ajax response from the server was very slow. Fix: submitComplete wasn't being triggered if there was an Editor field or form error (valid JSON required - it was being triggered in the case where invalid JSON was returned) Fix: Inline editing in IE10- with return submit could activate button click methods on elements that are not related to Editor Fix: Improved keyboard accessibility for the form submit buttons Fix: use data as the property to automatically determine the field to be edited for inline and bubble editing, rather than the name. Typically they are the same, but don't need to be. Fix: Radio fields may not always be updated if they are detached from the DOM Fix: Button class needs a space to separate it from the main form button class Fix: Style error in lightbox code - extra semi-colon (jshint) Fix: Missing semi-colons (jshint) PHP Fix - PHP: Exception could occur when trying to read data that does not exist Fix - PHP: If a leftJoin refers to a field that isn't included, no action is taken on it Fix - PHP: minMaxNum validator had a typo in it causing it to fail Docs Fix - docs: Typos in add() and select documentation Fix - docs: ajax.data had an incorrect link in it Examples Fix - example: Tab control used the on prefix for events from 1.2 Fix - example: Remove setInterval from inline tab example Fix - example: Inline tabbing - tab control should only be activated when inline editing Fix - examples: Typos in simple and field defaults examples Fix - examples: Typo of 'Extension' in examples
- Editor 1.3.1 release notes › Release notes › FixesFix: Attach submit event directly to the form element Fix: Remove debug statement Fix: fields with name=0 were causing an error Fix: Bootstrap integration error for title setting Fix PHP: A join with a table alias could cause a PHP error Fix PHP: Compatibility with PHP 5.3 when checking for a closure Fix PHP: PHP 5.3 compatibility for server-side processing Fix PHP: Field class could show an error on create Fix examples: Add missing standalone example index page Fix examples: Typos Fix examples: Demo tabs weren't quite working in the examples Fix examples: REST demo needed database name to be updated Fix examples: REST example needed a path update
- Editor 1.3.0 release notes › Release notes › FixesFix: SQL Server needed a couple of GO statements Fix: Documentation for the database headers was off Fix: SQL Server driver didn't work with a port specified Fix: If the primary key is specified in the create, use the key given Fix: localStorage example used the incorrect id for row finding Fix: If a column name matched a php function name, an error could occur Fix: Potential async error on submit. If, using the API, to open a form before the edit is complete, the information stored for the next edit could potentially be removed, resulting in a Javascript error. Fix: Checkbox and radio inputs have nicer styling Fix: Remove redundant code from the lightbox controller Fix: Button labels defined as an extended button were being overwritten by the language settings. Fix: Back / next example was throwing errors if you try to go beyond the extent of the table Fix: The submitted data tab now does the data submitted as HTTP varaibles rather than JSON (it is not submitted in JSON so this was misleading). Fix: Validate methods should check for a null value and allow it unless the field is required. This is done to allow fields which are not required to not be submitted. In the case where the field is not sent as part of the forms data, the value checked for validation is null (this is the only way it can be null - passing in 'null' gives the string null!) so the validation checks can see if that is a valid value or not. Possibly this should be split into another option? A required() method perhaps. The problem with the current method is that null and '' are treated the same - so where '' is a valid input, but you want to require it, you would need to write a custom validation method at the moment. Problem with spliting it up is it makes the initilaisation more verbose Fix: validate() should use the set formatter return if the server formatter was specified Fix: Numeric validation wasn't correctly respecting the required flags Fix - docs: Fix typos Fix example: Correct link in tableFormatting example Fix: localStorage example couldn't delete multiple rows Fix - PHP: Date formatter was stripping time part