Difference between revisions of "PT Calendar Version 3.2 Upgrade"
From ADF Docs
Gcronkright (talk | contribs) (→Overview) |
Gcronkright (talk | contribs) |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | Back to [[PT_Calendar|PT Calendar]] | ||
| + | |||
| + | IMPORTANT: v3.2 of this application requires '''ADF 1.7''' or greater | ||
| + | |||
== Overview == | == Overview == | ||
| − | This guide is to upgrade the PT | + | This guide is to upgrade the PT Calendar v3.2 from v3.1. If you are updating from a version earlier than v3.0, please follow the [[PT_Calendar_Version_3_Upgrade|Version 3.0 Upgrade Guide]] before upgrading to v3.2. |
| + | |||
| + | <!-- == Custom Element Updates == --> | ||
| + | |||
| + | == ADF Application Code Review == | ||
| + | This is only for reviewing the code that is in the "/ADF/apps/" directory, not at the site level. | ||
| + | |||
| + | # Download the application from the Community project page. | ||
| + | # Unzip the application zip folder. | ||
| + | # Analyze the updated app code compared to the current app code on your server. | ||
| + | ## Identify any customizations that you have made to the application code to make sure these are not overwritten by the app update. | ||
| + | ## 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. | ||
| + | # Once this is complete, then move your app customizations into the new app code package. | ||
== Application Code == | == Application Code == | ||
| − | # | + | # Rename directory "/ADF/apps/pt_calendar" to "/ADF/apps/pt_calendar_v3.1". |
| − | # | + | # Rename file "/ADF/apps/pt_calendar_v3.1/appBeanConfig.cfm" to "/ADF/apps/pt_calendar_v3/appBeanConfig.cfm.old". |
| − | # | + | # Move the PT Calendar v3.2 into the "/ADF/apps/pt_calendar/" directory. |
| − | + | # Reset the ADF | |
| − | |||
| − | |||
== Site Level Customizations Review == | == Site Level Customizations Review == | ||
| − | This is only for reviewing the site level customizations in the "/_cs_apps/ | + | This is only for reviewing the site level customizations in the "/_cs_apps/pt_calendar/" directory, not in the ADF directory. |
# Analyze the updated app code compared to the app customization code on your server. | # Analyze the updated app code compared to the app customization code on your server. | ||
| Line 18: | Line 32: | ||
## 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. | ## 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. | ||
# Once completed, Reset the ADF. | # Once completed, Reset the ADF. | ||
| + | |||
| + | == Reset the ADF == | ||
| + | [[Reset ADF|Reset the ADF]] for the server and site. | ||
Latest revision as of 17:39, 5 May 2016
Back to PT Calendar
IMPORTANT: v3.2 of this application requires ADF 1.7 or greater
Contents
Overview
This guide is to upgrade the PT Calendar v3.2 from v3.1. If you are updating from a version earlier than v3.0, please follow the Version 3.0 Upgrade Guide before upgrading to v3.2.
ADF Application Code Review
This is only for reviewing the code that is in the "/ADF/apps/" directory, not at the site level.
- Download the application from the Community project page.
- Unzip the application zip folder.
- Analyze the updated app code compared to the current app code on your server.
- Identify any customizations that you have made to the application code to make sure these are not overwritten by the app update.
- 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.
- Once this is complete, then move your app customizations into the new app code package.
Application Code
- Rename directory "/ADF/apps/pt_calendar" to "/ADF/apps/pt_calendar_v3.1".
- Rename file "/ADF/apps/pt_calendar_v3.1/appBeanConfig.cfm" to "/ADF/apps/pt_calendar_v3/appBeanConfig.cfm.old".
- Move the PT Calendar v3.2 into the "/ADF/apps/pt_calendar/" directory.
- Reset the ADF
Site Level Customizations Review
This is only for reviewing the site level customizations in the "/_cs_apps/pt_calendar/" directory, not in the ADF directory.
- Analyze the updated app code compared to the app customization code on your server.
- Identify any customizations that you have made to the application code to make sure these are updated with any functionality.
- 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.
- 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.
- Once completed, Reset the ADF.
Reset the ADF
Reset the ADF for the server and site.
