Difference between revisions of "Upgrade Guide v2.3"
From ADF Docs
Gcronkright (talk | contribs) |
Gcronkright (talk | contribs) (→Post-Upgrade Steps) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 45: | Line 45: | ||
## ?resetADF=1 | ## ?resetADF=1 | ||
# The reset command will add text to the top line of the page. If you see the following text with the date/time stamp: | # The reset command will add text to the top line of the page. If you see the following text with the date/time stamp: | ||
| − | ## ADF v2. | + | ## ADF v2.3 has been reset successfully! |
| − | # Upgrade was successful and you are running the ADF v2. | + | # Upgrade was successful and you are running the ADF v2.3. |
=== ADF Version Output === | === ADF Version Output === | ||
| Line 52: | Line 52: | ||
## ?ADFDumpVar=application.ADF.version | ## ?ADFDumpVar=application.ADF.version | ||
# This command with output the ADF version at the top of the page. If you see the following text: | # This command with output the ADF version at the top of the page. If you see the following text: | ||
| − | ## 2. | + | ## 2.3 |
| − | # Upgrade was successful and you are running the ADF v2. | + | # Upgrade was successful and you are running the ADF v2.3. |
== Post-Upgrade Steps == | == Post-Upgrade Steps == | ||
| + | |||
| + | === Update Site Level Override Components === | ||
| + | |||
| + | * Any site level override ADF Lib components located in the "_cs_apps/lib/" folder will need to be renamed and the component "extends" updated to point to the latest version of the matching ADF Lib components. | ||
| + | |||
| + | Example: "_cs_apps/lib/scripts_1_1.cfc" needs to become "scripts_2_0.cfc" and the extends value in the component tag | ||
| + | will need to point to "ADF.lib.scripts.scripts_2_0" | ||
| + | |||
| + | === Update Custom App Lib Component References === | ||
| + | * Update any ADF Lib component references in your custom ADF Apps to the latest versions of the matching ADF 2.0 Lib components in the App's appBeanConfig.cfm file (in the root of the App directory). | ||
| + | |||
| + | Example: "addConstructorDependency(appBeanName, "scripts_1_2", "scripts"); " needs to become | ||
| + | "addConstructorDependency(appBeanName, "scripts_2_0", "scripts");" | ||
| + | |||
=== Register ADF Scripts as CommonSpot Resources === | === Register ADF Scripts as CommonSpot Resources === | ||
| Line 85: | Line 99: | ||
For more information regarding the registration of ADF 2.0 ThirdParty Scripts as Resources in CommonSpot 10, please refer to the README information in the "/lib/scripts/scripts_2_0_READ_ME.txt" file. | For more information regarding the registration of ADF 2.0 ThirdParty Scripts as Resources in CommonSpot 10, please refer to the README information in the "/lib/scripts/scripts_2_0_READ_ME.txt" file. | ||
--> | --> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Related Guides == | == Related Guides == | ||
Latest revision as of 16:38, 24 January 2022
Contents
Current Version
Follow the guide below if you are upgrading to ADF v2.3.
Before upgrading, please review the v2.3 Release Notes
If you are upgrading from ADF v2.2 or earlier, then please follow the guides for previous ADF versions:
IMPORTANT: ADF 2.x can only be used with CommonSpot 10 or above.
Upgrade
Follow the steps below to upgrade the ADF directory:
- Download the ADF v2.3 from the Community site project page.
- On your server, rename the "/ADF/" directory to "/ADF-2.2/".
- Create a new "/ADF/" directory. Setup any necessary security or permissions for the new "/ADF/" directory.
- Export the download ADF zip folder into the "/ADF/" directory.
- Copy the contents of the "/ADF-2.2/apps/" directory into the "/ADF/apps/" directory.
- Reset the ADF through the web browser with the following URL parameter:
- ?resetADF=1
Note: If you have security permissions on the "/ADF/" directory make sure to set them up because the folder was renamed and then created new.
Validate Upgrade
There are 2 methods to validate the ADF upgrade.
ADF Reset
- Reset the ADF through the web browser with the following URL parameter:
- ?resetADF=1
- The reset command will add text to the top line of the page. If you see the following text with the date/time stamp:
- ADF v2.3 has been reset successfully!
- Upgrade was successful and you are running the ADF v2.3.
ADF Version Output
- In the browser, add the following URL parameter:
- ?ADFDumpVar=application.ADF.version
- This command with output the ADF version at the top of the page. If you see the following text:
- 2.3
- Upgrade was successful and you are running the ADF v2.3.
Post-Upgrade Steps
Update Site Level Override Components
- Any site level override ADF Lib components located in the "_cs_apps/lib/" folder will need to be renamed and the component "extends" updated to point to the latest version of the matching ADF Lib components.
Example: "_cs_apps/lib/scripts_1_1.cfc" needs to become "scripts_2_0.cfc" and the extends value in the component tag will need to point to "ADF.lib.scripts.scripts_2_0"
Update Custom App Lib Component References
- Update any ADF Lib component references in your custom ADF Apps to the latest versions of the matching ADF 2.0 Lib components in the App's appBeanConfig.cfm file (in the root of the App directory).
Example: "addConstructorDependency(appBeanName, "scripts_1_2", "scripts"); " needs to become "addConstructorDependency(appBeanName, "scripts_2_0", "scripts");"
Register ADF Scripts as CommonSpot Resources
- Register the ADF Script Resources with CommonSpot (for ADF 2.0 and above only!)
- Run the Register ALL Scripts tool.
IMPORTANT: The ADF thirdParty scripts libraries will not function when using ADF.scripts_2_0 loadScripts calls unless they are registered as Resources in CommonSpot 10.x.
