Close
Next
Prev

 

    Loading...

Comments provide the perfect opportunity for you to gain valuable feedback directly from your customers on a particular product or item, or to encourage participation within the community. You gain additional insight into the importance and popularity of a particular post. For example, use Discovery to surface the most commented on articles, then use that information for planning future activity for your community.

Pluck CommentsComments

Every comment is tied back to the user’s persona, which provides invaluable demographic information, as well as the opportunity to award use and involvement in the community by rewarding frequency and/or quality of comments. Overall, comments provides your community members with a platform to engage and provides you with a wealth of information about your community.

Features

  • Integrated Mini-Personas
  • Ignore User
  • Threaded Comment Replies
  • Crowdsourced opinions
  • Social Bridging — Post comments to Facebook, Twitter, and LinkedIn in addition to the site.
  • Social Sharing — RSS feed and toolbar enable sharing with social bookmarking services.
  • Rich Sorting and Filtering Options
  • Pagination Features
  • Comment Permalinks
  • In-line Moderation Tools — Comment blocking and deleting allow moderators to manage comment streams directly from the site.
  • Advanced Moderation — pre/post moderation, automatic approval by user tier, word filtering, and community abuse reporting.

Works With

Mini-Personas
 — appears when you hover over the Comment author’s avatar
Discovery
 — Bubble up Recent Comments on a separate page to increase traffic
Syndicate
 — Let your users post their onsite comments directly to Facebook, Twitter, and LinkedIn, or through an RSS feed that can be posted to social bookmarking services
Gamification
 — Reward submitted & approved comments and encourage participation
Galleries
 — Creates a more active community experience combining photos, videos, and comments

Implementation Tips

Details

Designed for very high volume sites, Pluck Comments is a flexible application powering conversation on some of the world’s leading websites, giving voice to visitors who want to react to original web site content. For brands and retailers, Pluck Comments is a versatile application with uses far beyond the traditional. For publishers, Pluck Comments provide an especially valuable enhancement to core editorial content, proven to drive page views. Diverse organizations use Pluck Comments to create conversation around their core site content and experiences.

  • AbuseReportThreshold

    Description: Sets the threshold number of AbuseReports that can be on an item before it is automatically removed from storage search results.

    Default Value: 2147483647

    Applications: Blogs Comments Forums Reviews

    Preference Type: Global

    Import: YES

    Value Range: 1...2147483647

  • AbuseWeights

    Description: Defines what weight is given to each user tier when creating abuse reports. 'Higher-level' users tend to be weighted more since we 'trust' abuse reports from them more.

    Default Value:

    Applications: Comments Forums Persona Photos

    Preference Type: Global

    Import: YES

    Value Range: AbuseWeight

  • AbuseWeightsByUserTier

    Description: Defines what weight is given to each user tier when creating abuse reports. 'Higher-level' users tend to be weighted more since we 'trust' abuse reports from them more.

    Default Value:

    Applications: Comments Forums Persona Photos

    Preference Type: Global

    Import: YES

    Value Range:

  • ActionUIControl

    Description: A dictionary that defines what authentication type is required for each Action type. If nothing is defined for a particular ActionUIEnum, Weak authentication is assumed, i.e. the HD cookie must be present in order for the user to be allowed to perform the action.

    Default Value:

    Applications: Blogs Comments Forums Persona

    Preference Type: Global

    Import: YES

    Value Range: Serializable Dictionary

  • ApprovalRequiredMappings

    Description: A collection containing the definitions for the object type and UserTier combinations that should be wrapped in ApprovalEnvelopes when they are created by the various commands. If there is no mapping specified for a particular object type, the object will not be wrapped in an ApprovalEnvelope

    Default Value:

    Applications: Comments

    Preference Type: Global

    Import: YES

    Value Range: Pluck.SiteLife.Models.Prefs.ApprovalRequiredMapping

  • ApprovalsRequired

    Description: A collection containing the definitions for the object type and UserTier combinations that should be wrapped in ApprovalsRequired when they are created by the various commands. If there is no mapping specified for a particular object type, the object will not be wrapped in an ApprovalsRequired

    Default Value: none

    Applications: Comments

    Preference Type: Global

    Import: NO

    Value Range:

  • AutoLoginEnabled

    Description: Allows users to automatically login with their Facebook accounts.

    Default Value: false

    Applications: Comments

    Preference Type: SiteSpecific

    Import: PROMPT

    Value Range: true false

  • DefaultImageSizeP4Avatar

    Description: Default pluck4 avatar image size bounding box, used in mini persona/comments. This only affects newly uploaded files, not existing files already on the system.

    Default Value: 40

    Applications: Comments Persona Reviews

    Preference Type: Global

    Import: YES

    Value Range:

  • Direct_MinimumCommentAuthenticationLevel

    Description: Configures DAAPI to set the minimum authentication allowed to create comments.

    Default Value: Anonymous

    Applications: Comments

    Preference Type: Global

    Import: YES

    Value Range: Anonymous Weak Strong

  • ExternalUrlsOpenInNewWindow

    Description: Setting to True opens external links in new windows instead of in the same browser window, e.g. links in forums/blogs/comments

    Default Value: false

    Applications: Blogs Comments Forums

    Preference Type: SiteSpecific

    Import: YES

    Value Range:

  • FacebookAutoSyncDays

    Description: If a user logs in via facebook connect, we will update his profile information every n days.

    Default Value: 7

    Applications: Comments

    Preference Type: SiteSpecific

    Import: PROMPT

    Value Range: 1...365

  • ForgotPasswordUrl

    Description: This is the link that goes to the customer's registration system that allows users to reset their password.

    Default Value:

    Applications: Blogs Comments Forums Persona

    Preference Type: SiteSpecific

    Import: PROMPT

    Value Range:

  • LoginUrlRedirectQueryParamName

    Description: This is the query parameter that is appended when the login link is followed. It allows the customer's site to redirect back to the page where the user clicked the Login link.

    Default Value: plckRedirectUrl

    Applications: Blogs Comments Forums Persona

    Preference Type: SiteSpecific

    Import: YES

    Value Range: string

  • LogoutUrlRedirectQueryParamName

    Description: This is the query parameter that is appended when the logout link is followed. It allows the customer's site to redirect back to the page where the user clicked the Logout link.

    Default Value: plckRedirectUrl

    Applications: Blogs Comments Forums Persona

    Preference Type: SiteSpecific

    Import: YES

    Value Range: string

  • OriginalVideoUrlBasePath

    Description: Defines the path under the sitelife application at which we will mount the original videos virtual. This shouldn't need to change and this pref is only as a fail safe which we don't expect to be overriden generally.

    Default Value: Content/Videos/Store/Main

    Applications: Blogs Comments Forums

    Preference Type: SiteSpecific

    Import: YES

    Value Range:

  • ReactionsDisabled

    Description: Turns off reactions for customers that aren't purchasing.

    Default Value: false

    Applications: Comments Ratings Recommendations

    Preference Type: Global

    Import: NO

    Value Range: true false

  • RegisterUrl

    Description: This is the location of a register new user page on the customer's website, where users would go to sign up for an account. This link is surfaced when a user is not logged in. This preference must be defined. There is no default value.

    Default Value:

    Applications: Blogs Comments Forums Persona

    Preference Type: SiteSpecific

    Import: PROMPT

    Value Range: string

  • RegisterUrlRedirectQueryParamName

    Description: This is the query parameter that is appended when the register link is followed. It allows the customer's site to redirect back to the page where the user clicked the Register link.

    Default Value: plckRedirectUrl

    Applications: Blogs Comments Forums Persona

    Preference Type: SiteSpecific

    Import: YES

    Value Range: string

  • SpamTriggersAbuseReportThreshold

    Description: If true, any content flagged as spam will be treated as automatically exceeding the abuse report threshold.

    Default Value: false

    Applications: Blogs Comments Forums Reviews

    Preference Type: Global

    Import: NO

    Value Range: true false

  • StripHTMLFromComments

    Description: StripHTMLFromComments

    Default Value: true

    Applications: Comments

    Preference Type: Global

    Import: NO

    Value Range:

  • TiersThatCanTagComments

    Description: A list of user tiers that can tag comments

    Default Value:

    Applications: Comments

    Preference Type: Global

    Import: YES

    Value Range:

  • VidaVeeVideoPlaybackUrl

    Description: VidaVee video playback url.

    Default Value: http://prod.publish.vidavee.net:80/vidad/publish.vidavee.com/pluck/Pluck/

    Applications: Blogs Comments Forums

    Preference Type: SiteSpecific

    Import: YES

    Value Range:

To set up Pluck Comments using REST

  1. Before you can install Pluck applications on your pages, your Pluck Application Server environment must be set up and you must have some articles, other Pluck applications, or other Pluck widgets that generate content up on the page, too—such as Blogs or Photos—that users can comment on.

  2. Determine on what page(s) you want to add Comments to. This is usually an article template that your CMS (Content Management System) provides.

  3. Make sure any preferences are set, such as having a comment approval process. Your Pluck representative can help you determine if any preferences are relevant to your implementation and what settings should be made for Comments.

  4. Load the Pluck Libraries. Give your site access to the applications on the Pluck Application Server by including the following somewhere in the <head> tag:

    <script type="text/javascript" src="http://yourPluckServer.com/ver1.0/Content/ua/scripts/pluckApps.js"></script>

    where yourPluckServer is the domain of your Pluck server.

  5. Include the Pluck Applications CSS. In the <head> tag, link to the Pluck Application CSS:

    <link rel="stylesheet" type="text/css" href="http://yourPluckServer.com/ver1.0/Content/ua/css/pluckAll.css" />

    where yourPluckServer is the domain of your Pluck server.

  6. Make The REST Call. Call the Comments response with the appropriate URL:

    http://yourdomain.com/ver1.0/pluck/comments.app?plckCommentOnKeyType=article&plckCommentOnKey=pants&plckArticleUrl=YourURL&clientUrl=http%3A%2F%2Fwww.yourdomain.com%2Fpageyouareon%3Fquerystring

    where yourdomain is the domain of your website, and YourURL is the URL of the page making the REST call.

    Note:

    When installing REST applications, you must pass the SiteLifeHost and AT cookies in the REST call. The AT cookie is case sensitive and is lowercase by default. Depending on your environment setup you may be required to pass additional cookies. The clientUrl is also required and should be passed in as the current page being requested with the full querystring. URLencode the entire value when adding it to the above URL. Don’t URLdecode the requesting URL prior to encoding it or you can end up with invalid URLs. For more information, ask your Pluck Representative.

To set up Pluck Comments For Mobile

  1. Before you can install Pluck applications on your pages, your Pluck Application Server environment must be set up and you must have some articles, other Pluck applications, or other Pluck widgets that generate content up on the page, too—such as Blogs or Photos—that users can comment on.

  2. Determine on what page(s) you want to add Comments to. This is usually an article template that your CMS (Content Management System) provides.

  3. Make sure any preferences are set, such as having a comment approval process. Your Pluck representative can help you determine if any preferences are relevant to your implementation and what settings should be made for Comments.

  4. Load the Pluck Libraries. Give your site access to the applications on the Pluck Application Server by including the following somewhere in the <head> tag:

    <script type="text/javascript" src="http://yourPluckServer.com/ver1.0/Content/ua/scripts/pluckMobileApps.js"></script>

    where yourPluckServer is the domain of your Pluck server.

  5. Place the PAS JavaScript call for Comments on the page:

    
    		 pluckAppProxy.embedApp("mobile_comments", {
    		        plckCommentOnKeyType: "article",
    		        plckCommentOnKey: "myTestArticle.html"
    		    }, opts);
    			

    With the PAS JavaScript call, you can also set options (that’s the opts in the example above) that control how the application displays and loads. For more information, see Loading Pluck Applications.

Note:

ExternalResource (Article) keys uniquely identify the parent of a comment stream, reviews, recommendations, or other reactions throughout its lifetime and can not be changed. If your CMS changes the ID of an article, product, or other item you’ve placed a Pluck reaction on, you must create a mapping between the Pluck ExternalResource key and your new ID value.

Alternative Call Method

Using the JavaScript call to put Pluck application on the page is preferred, but in some circumstances you may need to use PAS tags. For more information, see PAS Tags.

Valid parameters for Comments for Mobile Application Call Tag

Valid parameters for Comments for Mobile are:

  • plckCommentOnKeyType* — The type of the parent object containing the comments.
  • plckCommentOnKey* — The key of the parent object containing the comments.
  • plckFindCommentKey — The key of a specific comment to be displayed on the page.
  • plckItemsPerPage — The number of comments to display per page.
  • plckOnPage — The current page number being display. This is a 1-based number.
  • plckSort — The current sort applied to the comments.
  • plckCommentSubmitDisabled — Indicates that new comments cannot be added.
  • plckCommentMaxLength — Determines the maximum length of the comment. Is limited to less than SiteLifePrefs.InternalPrefs.CommentLengthLimit.
  • plckFeaturedUserBadgeFamilyId — Badge family key used to identify a user as a “featured” reviewer by adding an indicator to the user’s avatar. Ignored if Points & Badging is disabled.
  • plckFeaturedUserBadgeId — Badge key used to identify a user as a “featured” reviewer by adding an indicator to the user’s avatar. Used in tandem with plckFeaturedUserBadgeFamilyId. Ignored if Points & Badging is disabled.
  • plckArticleTitle — The title of the parent article. If not specified, the title of the current page is used.
  • plckArticleUrl — The URL of the parent article. If not specified the URL of the current page is used.
  • plckDiscoveryCategories — A comma-separated list of discovery categories to apply to the parent article.
  • plckDiscoverySection — The discovery section to apply to the article.
  • *Required parameters

    Note:

    All of the parameters available from the call tag can also be set in comments.prefs. Doing so sets the default for that parameter within your implementation or theme. It makes more sense to set some of these in comments.prefs than others. For example, it can be useful to set plckSort in comments.prefs, but there’s no point in setting plckCommentOnKey there.

Drop Comments On a Page

  1. If you have not already done so, load the Pluck libraries. In the <head> tag, add:

    <script type="text/javascript" src="http://yourPluckServer.com/ver1.0/Content/ua/scripts/pluckApps.js"></script>

    where yourPluckServer is the domain of your Pluck server.

  2. Build the parameter string:

    The parameter string is a comma-delimited list of required and optional parameters meant to format the widget. For example:

    where commentKey is the key that identifies the parent object containing the comments.

  3. Place the PAS Comments JavaScript call on the page where you want the app to appear:

  4. Save and reload. The Pluck Comments application appears on the page where you put the PAS call.

    6.0.11 Release        © 2014 DemandMedia                                   Teacher’s Edition