Release Notes v1.5.1 - Revision history

Mcarroll: /* Important Notes */

2012-01-18T17:06:16Z

‎Important Notes

Mcarroll: /* Notable Bug Fixes */

2012-01-18T17:06:04Z

‎Notable Bug Fixes

Mcarroll: /* Notable Bug Fixes */

2012-01-18T17:05:54Z

‎Notable Bug Fixes

Mcarroll: /* Notable Bug Fixes */

2012-01-18T17:05:37Z

‎Notable Bug Fixes

Mcarroll: /* Enhancements */

2012-01-18T17:05:12Z

‎Enhancements

Mcarroll: /* Enhancements */

2012-01-18T17:04:51Z

‎Enhancements

Mcarroll: /* Notable Bug Fixes */

2012-01-18T17:03:56Z

‎Notable Bug Fixes

Mcarroll: Created page with '== About this Document == Application Development Framework (ADF) version 1.5.1 updates the recent 1.5 release with: * Enhancements * Notable Bug Fixes For detailed instruction…'

2012-01-18T17:03:39Z

Created page with '== About this Document == Application Development Framework (ADF) version 1.5.1 updates the recent 1.5 release with: * Enhancements * Notable Bug Fixes For detailed instruction…'

New page

== About this Document ==
Application Development Framework (ADF) version 1.5.1 updates the recent 1.5 release with:
* Enhancements
* Notable Bug Fixes

For detailed instructions for installing the ADF, see the [[Installation|ADF v1.5 Installation Guide]].

For detailed instructions for upgrading from a previous version of the ADF, see the [[Upgrade_Guide_v1.5.1|ADF v1.5.1 Upgrade Guide]].

Before installing or upgrading to this release of the ADF, please review these Important Notes.

== Important Notes ==
Review the following important notes before installing or upgrading to the ADF 1.5.1.

If you are upgrading from a release earlier than 1.5, we strongly recommend that you also read the [[Release_Notes_v1.5|1.5 Release Notes]].

'''Scripts Backwards Compatibility'''
With the v1.5 updates to the Third Party jquery files we removed the build version from the JS file name. Older function calls to the scripts "loadJQuery" and "loadJQueryUI" functions have the version argument contain the build number (i.e. "1.3.2”). This call will throw a JavaScript error message because the JavaScript path will not be resolved.
This bug fix trims the build number from the version argument for the "loadJQuery" and "loadJQueryUI" functions in the scripts v1.0 and v1.1. For example, when the version argument is "1.3.2", the ADF will load the file for "1.3".

'''JQuery No-Conflict Mode'''
With CommonSpot 6.2, an issue occurs with the field type definition dialog not rendering correctly if you have a registered custom field type that is loading Jquery. To resolve this issue, you need to force Jquery into "no-conflict" mode when loading. In ADF 1.5 we fixed this issue globally by forcing Jquery into "no-conflict" mode through the scripts loadJQuery function when the site is running CommonSpot 6.2.

This caused backwards compatibility issues with custom code that contain Jquery code utilizing the "$" symbol. When forcing JQuery into "no-conflict" mode, all code for the "$" symbol needs to be replaced with "jQuery". Jquery does not recognize the "$" symbol as Jquery when in "no-conflict" mode.

The fix in the ADF 1.5 resolved the solution on a global scale. Any custom code would need to be updated for the "$" symbol. We have removed the global forcing of Jquery "no-conflict” in 1.5.1. This means by default Jquery will not load in "no-conflict" mode. There is an argument in the scripts "loadJQuery" function to enable "no-conflict" mode when loading Jquery. We updated the ADF custom field types property files that are loading Jquery to set the "no-conflict" argument to true. This enables only the ADF custom field type property files to load Jquery in "no-conflict" mode to prevent the CommonSpot 6.2 issue with the field type definition dialog.

We are updating the ADF applications to have this same fix. If you have custom field types within your site, you'll need to make this fix to the property files. The update is the following:
Current: "application.ADF.scripts.loadJQuery();"
New: "application.ADF.scripts.loadJQuery(noConflict=true);"
This update is only required on the custom field type property file (these are normally files with the suffix of "_props").

After upgrading the ADF to 1.5.1, please check any custom element field definitions to make sure the field definition dialog is running correctly. If not, check any ADF applications custom fields (/ADF/apps/), customized application custom field types (/_cs_app/), and your sites custom field types (/customfields/).

== Enhancements ==

The 1.5.1 release includes the following enhancements:

'''Jquery Updates and Plug-Ins'''
ADF v1.5.1 contains the latest Jquery 1.7 build and the 1.6 latest build. The scripts_1_1.loadJQuery function was updated to load Jquery version 1.7 by default. Three Jquery plug-ins (fancybox, flowplayer and mousewheel) were added to the third party and scripts load functions were created.

'''Extensions/customcf'''
genericElementManagement - Added attribute for themeName that can be passed via the custom script parameters dialog.

'''Extensions/customfields'''
Custom Text Area - Updated to use the wrapFieldHTML from ADF lib forms_1_1.

'''Extensions/datasheet-modules'''
pageIDlist-to-linkList - Handles converting the lists of pageIDs into stacked lists of PageURL links with pageTitles.

== Notable Bug Fixes ==
This release fixes issues with:

'''Scripts Backwards Compatibility'''
See the Important Notes for a detailed explanation.
This bug fix trims the build number from the version argument for the "loadJQuery" and "loadJQueryUI" functions in the scripts v1.0 and v1.1. For example, when the version argument is "1.3.2", the ADF will load the file for "1.3".

'''JQuery No-Conflict Mode'''
See the Important Notes for a detailed explanation.
We have removed the global forcing of Jquery "no-conflict” in 1.5.1. This means by default Jquery will not load in "no-conflict" mode. Updated the following ADF custom field types: app config page,c ustom element select field, element selector, file uploader, and sample.

'''Custom Field Type Security'''
Developing custom fields to utilize the forms_1_1.wrapFieldHTML function were not handling the field type security correctly for CommonSpot 6.x versions. This has been updated for the CommonSpot 6.x variable for fieldPermission. For details on this variable, please see the CommonSpot 6.2 Developers Guide section 3.3.2.6.4 Field Level Security.

'''Sample Field'''
Updates were made to the sample field type to set the default values into a structure. This structure is then joined with the properties current field values to automate the validation for if a property field has been defined.

'''Lib/Forms'''
* Forms_1_1.renderAddEditForm - Added check that the input field contains the name attribute.

'''Extensions/datasheet-modules'''
* subsiteID-to-link - Added the other bad subsite fix that was missed about the currentSortValue as well.
'''
Extensions/customfields'''
* General Chooser - The field now honors the "required" setting in Standard Options and forces the user to make a choice.
* Custom Checkbox Field - Added a call to the loadJQuery method in the scripts lib.
* Star Rating - Commented out JS code to prevent JS error in the form.
* File Uploader - Moved the the hidden field code for the CFT inside the TD tag.

@@ Line 15: / Line 15: @@
 If you are upgrading from a release earlier than 1.5, we strongly recommend that you also read the [[Release_Notes_v1.5|1.5 Release Notes]].
-'''Scripts Backwards Compatibility'''
+'''Scripts Backwards Compatibility'''<br>
 With the v1.5 updates to the Third Party jquery files we removed the build version from the JS file name.  Older function calls to the scripts "loadJQuery" and "loadJQueryUI" functions have the version argument contain the build number (i.e. "1.3.2”).  This call will throw a JavaScript error message because the JavaScript path will not be resolved.
 This bug fix trims the build number from the version argument for the "loadJQuery" and "loadJQueryUI" functions in the scripts v1.0 and v1.1.  For example, when the version argument is "1.3.2", the ADF will load the file for "1.3".
-'''JQuery No-Conflict Mode'''
+'''JQuery No-Conflict Mode'''<br>
 With CommonSpot 6.2, an issue occurs with the field type definition dialog not rendering correctly if you have a registered custom field type that is loading Jquery.  To resolve this issue, you need to force Jquery into "no-conflict" mode when loading.  In ADF 1.5 we fixed this issue globally by forcing Jquery into "no-conflict" mode through the scripts loadJQuery function when the site is running CommonSpot 6.2.

@@ Line 63: / Line 63: @@
 Developing custom fields to utilize the forms_1_1.wrapFieldHTML function were not handling the field type security correctly for CommonSpot 6.x versions.  This has been updated for the CommonSpot 6.x variable for fieldPermission.  For details on this variable, please see the CommonSpot 6.2 Developers Guide section 3.3.2.6.4 Field Level Security.
-'''Sample Field'''
+'''Sample Field'''<br>
 Updates were made to the sample field type to set the default values into a structure.  This structure is then joined with the properties current field values to automate the validation for if a property field has been defined.

@@ Line 52: / Line 52: @@
 This release fixes issues with:
-'''Scripts Backwards Compatibility'''
+'''Scripts Backwards Compatibility'''<br>
 See the Important Notes for a detailed explanation.
 This bug fix trims the build number from the version argument for the "loadJQuery" and "loadJQueryUI" functions in the scripts v1.0 and v1.1.  For example, when the version argument is "1.3.2", the ADF will load the file for "1.3".
-'''JQuery No-Conflict Mode'''
+'''JQuery No-Conflict Mode'''<br>
 See the Important Notes for a detailed explanation.
 We have removed the global forcing of Jquery "no-conflict” in 1.5.1.  This means by default Jquery will not load in "no-conflict" mode.  Updated the following ADF custom field types: app config page,c ustom element select field, element selector, file uploader, and sample.
-'''Custom Field Type Security'''
+'''Custom Field Type Security'''<br>
 Developing custom fields to utilize the forms_1_1.wrapFieldHTML function were not handling the field type security correctly for CommonSpot 6.x versions.  This has been updated for the CommonSpot 6.x variable for fieldPermission.  For details on this variable, please see the CommonSpot 6.2 Developers Guide section 3.3.2.6.4 Field Level Security.
-'''Sample Field'''
+'''Sample Field'''<br>
 Updates were made to the sample field type to set the default values into a structure.  This structure is then joined with the properties current field values to automate the validation for if a property field has been defined.
-'''Lib/Forms'''
+'''Lib/Forms'''<br>
 * Forms_1_1.renderAddEditForm - Added check that the input field contains the name attribute.

@@ Line 37: / Line 37: @@
 The 1.5.1 release includes the following enhancements:
-'''Jquery Updates and Plug-Ins'''
+'''Jquery Updates and Plug-Ins'''<br>
 ADF v1.5.1 contains the latest Jquery 1.7 build and the 1.6 latest build.  The scripts_1_1.loadJQuery function was updated to load Jquery version 1.7 by default.  Three Jquery plug-ins (fancybox, flowplayer and mousewheel) were added to the third party and scripts load functions were created.
-'''Extensions/customcf'''
+'''Extensions/customcf'''<br>
 genericElementManagement - Added attribute for themeName that can be passed via the custom script parameters dialog.
-'''Extensions/customfields'''
+'''Extensions/customfields'''<br>
 Custom Text Area - Updated to use the wrapFieldHTML from ADF lib forms_1_1.
-'''Extensions/datasheet-modules'''
+'''Extensions/datasheet-modules'''<br>
 pageIDlist-to-linkList - Handles converting the lists of pageIDs into stacked lists of PageURL links with pageTitles.

@@ Line 71: / Line 71: @@
 '''Extensions/datasheet-modules'''
 * subsiteID-to-link - Added the other bad subsite fix that was missed about the currentSortValue as well.
 '''
-Extensions/customfields'''
+'''Extensions/customfields'''
 * General Chooser - The field now honors the "required" setting in Standard Options and forces the user to make a choice.
 * Custom Checkbox Field - Added a call to the loadJQuery method in the scripts lib.
 * Star Rating - Commented out JS code to prevent JS error in the form.
 * File Uploader - Moved the the hidden field code for the CFT inside the TD tag.