PT Calendar Version 3.2 Upgrade - Revision history

Gcronkright at 17:39, 5 May 2016

2016-05-05T17:39:15Z

WikiSysop at 06:48, 12 April 2014

2014-04-12T06:48:14Z

Gcronkright: Blanked the page

2013-12-20T22:41:16Z

Blanked the page

Gcronkright: /* App Configuration Update */

2013-12-20T20:52:30Z

‎App Configuration Update

Gcronkright: /* App Configuration Updates */

2013-12-20T20:51:57Z

‎App Configuration Updates

Gcronkright: /* App Configuration Updates */

2013-12-20T20:51:00Z

‎App Configuration Updates

Gcronkright: /* Application Code */

2013-12-20T20:31:11Z

‎Application Code

Gcronkright at 20:09, 20 December 2013

2013-12-20T20:09:14Z

Gcronkright: /* Overview */

2013-12-20T20:03:44Z

‎Overview

Gcronkright: /* Overview */

2013-12-20T20:03:23Z

‎Overview

@@ Line 6: / Line 6: @@
 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 ==
+<!-- == Custom Element Updates == -->
 == ADF Application Code Review ==

← Older revision	Revision as of 06:48, 12 April 2014
Line 1:	Line 1:
	+	Back to [[PT_Calendar\|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 [[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 ==
	+	# 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 ADF\|Reset the ADF]] for the server and site.

← Older revision		Revision as of 22:41, 20 December 2013
Line 1:		Line 1:
−	~~== Overview ==~~
−	~~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 ==~~
−
−	~~=== PTBlog2 Configuration ===~~
−	~~Add the following field to the '''Blog Configuration''' tab of the ptBlog2 Configuration element:~~
−	~~#a Blog Configuration URL CommonSpot Page URL field~~
−	~~##Field Name: blogConfigurationURL~~
−	~~##Field Label: Blog Configuration URL~~
−	~~##Type: CommonSpot Page URL~~
−	~~##Properties:~~
−	~~###None~~
−
−	~~== Application Code ==~~
−	~~# 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 ==~~
−	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.
−	~~# 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 ===~~
−	~~After the new App Configuration page has been created:~~
−	~~# Go to the Blog App Configuration Manager and click the '''"Edit Configuration"''' button.~~
−	~~# When the configuration form opens, go to the '''Blog Configuration''' tab, then update the following field with the new value:~~
−	~~## Blog Configuration URL:: ''{browse to your newly created Blog App Configuration page}''~~
−	~~# Then click "Submit".~~
−
−	~~== Reset the ADF ==~~
−	~~[[Reset ADF\|Reset the ADF]] for the server and site.~~
−
−	~~== 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.~~
−
−	~~# 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.~~

@@ Line 32: / Line 32: @@
 ## Blog Configuration URL:: ''{browse to your newly created Blog App Configuration page}''
 # Then click "Submit".
 == Reset the ADF ==

@@ Line 26: / Line 26: @@
 # Publish the page.
-=== App Configuration Updates ===
+=== App Configuration Update ===
 After the new App Configuration page has been created:
 # Go to the Blog App Configuration Manager and click the '''"Edit Configuration"''' button.

@@ Line 18: / Line 18: @@
 # Downloaded the PT Blog v3.2 and exported into the "/ADF/apps/pt_blog/" directory.
-== App Configuration Updates ==
+== App Configuration Page ==
 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.
 # Create a new page called 'Configuration Manager' in the ''/webadmin/blogs/'' subsite from the webadmin template.
@@ Line 25: / Line 25: @@
 #* ''/ADF/apps/pt_blog/customcf/manage_configuration_header.cfm''
 # Publish the page.
 == Reset the ADF ==

@@ Line 1: / Line 1: @@
 == Overview ==
 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.
 == Application Code ==