Difference between revisions of "PT Calendar Version 4.0 Upgrade"

Latest revision as of 23:28, 17 February 2022

Back to PT Calendar

IMPORTANT: v4.0 of this application requires ADF 2.0 or greater 

Overview

This guide is to upgrade the PT Calendar v4.0 from v3.1. If you are updating from a version earlier than v3.1, please follow the Version 3.1 Upgrade Guide before upgrading to v4.0.

Note: There is not an upgrade path from Calendar 2 or earlier to Calendar 4.x. You can only upgrade Calendar v3.x to Calendar v4. 
From Calendar 2.x or earlier you will need to treat the Calendar App as a new install.

Download

Download the Calendar Application from the Community Site Project or from the SVN Repository.

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. Rename directory "/ADF/apps/pt_calendar" to "/ADF/apps/pt_calendar_v3.1".
2. Rename file "/ADF/apps/pt_calendar_v3.1/appBeanConfig.cfm" to "/ADF/apps/pt_calendar_v3.1/appBeanConfig.cfm.old".
3. Move the PT Calendar v4.0 and into the "/ADF/apps/pt_calendar/" directory.
4. 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.

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.

Reset the ADF

Reset the ADF for the server and site.