Difference between revisions of "PT Calendar Version 3.2 Upgrade"

From ADF Docs
Jump to: navigation, search
(→‎App Configuration Updates)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
== Overview ==
+
Back to [[PT_Calendar|PT Calendar]]
−
This guide is to upgrade the PT Blog v3.2 application.  If upgrading from a lower version than v3.1, please follow the [[PT_Blog_Upgrade_v3|PT Blog Upgrade v3 Guide]] to validate your installation.
 
  
−
== Custom Element Updates ==
+
IMPORTANT: v3.2 of this application requires '''ADF 1.7''' or greater
  
−
=== PTBlog2 Configuration ===
+
== Overview ==
−
Add the following field to the '''Blog Configuration''' tab of the ptBlog2 Configuration element:
+
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.
−
#a Blog Configuration URL CommonSpot Page URL field
 
−
##Field Name:  blogConfigurationURL
 
−
##Field Label: Blog Configuration URL
 
−
##Type: CommonSpot Page URL
 
−
##Properties:
 
−
###None
 
  
−
== Application Code ==
+
<!-- == Custom Element Updates == -->
−
# Renamed directory "/ADF/apps/pt_blog" to "/ADF/apps/pt_blog_v3_1".
 
−
# Renamed file "/ADF/apps/pt_blog_v3_1/appBeanConfig.cfm" to "/ADF/apps/pt_blog_v3_1/appBeanConfig.cfm.old".
 
−
# Downloaded the PT Blog v3.2 and exported into the "/ADF/apps/pt_blog/" directory.
 
  
−
== App Configuration Page ==
+
== ADF Application Code Review ==
−
After the new ''blogConfigurationURL'' field has been added to the PTBlog2 Configuration element and the new App files are in place a Blog Configuration Page will be used to manage the ptBlog2 Configuration custom element.
+
This is only for reviewing the code that is in the "/ADF/apps/" directory, not at the site level.
−
# Create a new page called 'Configuration Manager' in the ''/webadmin/blogs/'' subsite from the webadmin template.
 
−
# In the main content of the page, add a Custom Script element.
 
−
# Enter the explicit module path for:
 
−
#* ''/ADF/apps/pt_blog/customcf/manage_configuration_header.cfm''
 
−
# Publish the page.
 
  
−
=== App Configuration Update ===
+
# Download the application from the Community project page.
−
After the new App Configuration page has been created:
+
# Unzip the application zip folder.
−
# Go to the Blog App Configuration Manager and click the '''"Edit Configuration"''' button.  
+
# Analyze the updated app code compared to the current app code on your server.
−
# When the configuration form opens, go to the '''Blog Configuration''' tab, then update the following field with the new value:
+
## Identify any customizations that you have made to the application code to make sure these are not overwritten by the app update. 
−
## Blog Configuration URL:: ''{browse to your newly created Blog App Configuration page}''
+
## 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.
−
# Then click "Submit".
+
# Once this is complete, then move your app customizations into the new app code package.
−
# When the configuration page reloads click the '''"Reset ADF / App Configuration"''' button.
 
  
−
== Reset the ADF ==
+
== Application Code ==
−
[[Reset ADF|Reset the ADF]] for the server and site.
+
# 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/pt_blog/" directory, not in the ADF directory.
+
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 45: 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

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.

  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/appBeanConfig.cfm.old".
  3. Move the PT Calendar v3.2 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.

Retrieved from "http://community.paperthin.com/adf-docs/index.php?title=PT_Calendar_Version_3.2_Upgrade&oldid=7127"