OHSU Navigation Upgrade v2.0

From ADF Docs
Revision as of 15:08, 12 September 2012 by Mcarroll (talk | contribs) (Created page with '== Overview == This guide is to upgrade the [http://community.paperthin.com/projects/ohsu_navigation/ OHSU Navigation] v1.0 from v2.1. For v2.0, the updates are only for code b…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Overview

This guide is to upgrade the OHSU Navigation v1.0 from v2.1.

For v2.0, the updates are only for code bug fixes. No updates are needed to the CommonSpot custom elements or pages.

ADF Application Code Review

This is only for reviewing the code that is in the "/ADF/apps/" directory, not at the site level.

  1. Download the application from the Community project page.
  2. Unzip the application zip folder.
  3. Analyze the updated app code compared to the current app code on your server.
    1. Identify any customizations that you have made to the application code to make sure these are not overwritten by the app update.
    2. A great tool to use is Beyond Compare to compare the new and current file to identify the exact lines of code that have been changed.
  4. Once this is complete, then move your app customizations into the new app code package.

Application Code

  1. Renamed directory "/ADF/apps/ohsu_nav" to "/ADF/apps/ohsu_nav_v1".
  2. Renamed file "/ADF/apps/ohsu_nav_v1/appBeanConfig.cfm" to "/ADF/apps/ohsu_nav_v1/appBeanConfig.cfm.old".
  3. Move the OHSU Navigation v2.0 app code into the "/ADF/apps/ohsu_nav/" directory.
  4. Reset the ADF.

Site Level Customizations Review

This is only for reviewing the site level customizations in the "/_cs_apps/ohsu_nav/" directory, not in the ADF directory.

  1. Analyze the updated app code compared to the app customization code on your server.
    1. Identify any customizations that you have made to the application code to make sure these are updated with any functionality.
    2. Again, Beyond Compare is a good tool to compare the new and current file to identify the exact lines of code that have been changed.
    3. This is important for components that have customized functions to the site level "/_cs_apps/". The best practice is to identify the function that have been customized and compare with the new app function to identify any updates. A good help is to check the function comment header to see if any updates have been made.
  2. Once completed, Reset the ADF.