PT Comments Upgrade v2.1 - Revision history

Gcronkright: /* Application Configuration */

2016-05-05T17:46:18Z

‎Application Configuration

Gcronkright at 17:43, 5 May 2016

2016-05-05T17:43:08Z

Gcronkright: /* Overview */

2016-05-05T17:42:37Z

‎Overview

Gcronkright at 17:33, 5 May 2016

2016-05-05T17:33:52Z

Gcronkright: Gcronkright moved page PT Comments Upgrade v2 to PT Comments Upgrade v2.1

2016-05-05T17:32:15Z

Gcronkright moved page PT Comments Upgrade v2 to PT Comments Upgrade v2.1

Gcronkright: Created page with "== Overview == This guide is to upgrade the [http://community.paperthin.com/projects/pt_comments/ PT Comments] v1.0 to v2.1. For v2.1, the primary change that occurred was a ..."

2016-05-05T17:31:20Z

Created page with "== Overview == This guide is to upgrade the [http://community.paperthin.com/projects/pt_comments/ PT Comments] v1.0 to v2.1. For v2.1, the primary change that occurred was a ..."

New page

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

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.

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

← Older revision		Revision as of 17:46, 5 May 2016
Line 32:		Line 32:


−	== ~~Application~~ Configuration ==	+	== App Configuration ==
	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.		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.

@@ Line 31: / Line 31: @@
 # Once completed, Reset the ADF.
 == Application Configuration ==
 If you added the following code to your site's .HEAD file:

← Older revision		Revision as of 17:33, 5 May 2016
Line 1:		Line 1:
		+	Back to [[PT_Comments\|PT Comments]]
		+
	== Overview ==		== Overview ==
	This guide is to upgrade the [http://community.paperthin.com/projects/pt_comments/ PT Comments] v1.0 to v2.1.		This guide is to upgrade the [http://community.paperthin.com/projects/pt_comments/ PT Comments] v1.0 to v2.1.

@@ Line 3: / Line 3: @@
 == Overview ==
 This guide is to upgrade the [http://community.paperthin.com/projects/pt_comments/ PT Comments] v1.0 to v2.1.
 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.
 If you added the following code to your site's .HEAD file:
-       <cfset request.params.comments.contentDataPageID = request.page.id>
+ <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>
+ <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

← Older revision	Revision as of 17:32, 5 May 2016
(No difference)