View source for PT Comments Upgrade v2.1

Back to [[PT_Comments|PT Comments]]

== Overview ==
This guide is to upgrade the [http://community.paperthin.com/projects/pt_comments/ PT Comments] v1.0 to v2.1.

<!-- == 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_comments" to "/ADF/apps/pt_comments_v1.0".
# Rename file "/ADF/apps/pt_comments_v1.0/appBeanConfig.cfm" to "/ADF/apps/pt_comments_v1.0/appBeanConfig.cfm.old".
# Move the PT Cimments v2.1 into the "/ADF/apps/pt_comments/" directory.
# Reset the ADF

== Site Level Customizations Review ==
This is only for reviewing the site level customizations in the "/_cs_apps/pt_comments/" 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.

For v2.1, the primary change that occurred was a bug fix requiring updates to potentially the .HEAD file and to a filter on pages where the Comment element exists.

== Application Configuration ==

If you added the following code to your site's .HEAD file:

 <cfset request.params.comments.contentDataPageID = request.page.id> 

you will need to modify the .HEAD and change the code to the following:

 <cfset request.comments.contentDataPageID = request.page.id>

Next, you will need to change the render mode filter on any page or template where the comments element is used:

# Update the render mode on the Comments element
## Select "Display existing element data (content reuse)"
## Select "Render results dynamically based on a filter, or display all records."
## click on filter
## select "Subset of records"
## in the dropdown select Comments.contentDataPageID
## Set the comparison to equals
## click the ... next to the value
## change request.params.comments.contentDataPageID to request.comments.contentDataPageID
## Sort Order: dateTimePosted ASCENDING
## click save
# submit your page