Telligent Evolution 5.x Developer Documentation

How to: Configure CFS File Store

Blake "Howdy" Smith — Tue, 31 Jan 2012 18:24:45 GMT

Current Revision posted to Telligent Evolution 5.x Developer Documentation by Blake "Howdy" Smith on 1/31/2012 12:24:45 PM

Creating a new [[CFS File Stores|CFS file store]] is as simple as adding a new <fileStore /> node to the <CentralizedFileStorage /> node of the communityserver.config file with a new name. When the <fileStore /> node exists, that file store can be used to add/delete/query files.

To add a new CFS File Store using a [[Override Files|communityserver_override.config]] file, the following [[Override Files|override]] can be used:

<Override xpath="/CommunityServer/CentralizedFileStorage" mode="add">
    <fileStore name="MyAssembly.MyCFSFileStore"
               type="CommunityServer.Components.FileSystemFileStorageProvider,
                     CommunityServer.Components"
               basePath="~\filestorage\\" />
</Override>

The existing file stores are named according to the full name of the class in that interacts with the file store. For example, post attachments are created/updated/deleted via the CommunityServer.Components.PostAttachments class in the API so the CFS file store used to store post attachment files is named CommunityServer.Components.PostAttachments. We suggest continuing this naming convention when you add file stores to the CFS.

Tags: cfs

Telligent Evolution Platform Software Development Kit

Jenny Jarrard — Fri, 20 Jan 2012 19:48:00 GMT

Current Revision posted to Telligent Evolution 5.x Developer Documentation by Jenny Jarrard on 1/20/2012 1:48:00 PM

The Telligent Evolution Platform Software Development Kit (SDK) gives you examples and guidance for creating powerful features that are custom-tailored to your own needs.

A new version of the platform SDK (version 5.6) is now available.

What can I do with the Telligent Evolution platform SDK?

The Telligent Evolution Platform SDK is a collection of examples, tools, and documentation designed to help you develop applications against the Telligent Evolution platform, the central platform supporting Telligent Enterprise and Telligent Community.

The following sections represent the cumulative information about the platform SDK throughout this release.

What is contained in the platform SDK 5.0?

The platform SDK contains the source code for sample applications:

Stand-alone applications:
- Bahbl - Reference application used to drive out v2 REST endpoints. Bahbl is a Twitter-like application that shows you how to use profiles, activity messages, authentication, and other key features of the Evolution REST infrastructure.
- New User Uploader Tool - Short, practical tool showing you how to create new users from a comma separated value (.csv) file.
Integration tests used to exercise and validate the Telligent Evolution Web services. These are the tests Telligent used during the development of v2 REST Web services. You’ll see exactly how you can implement very granular pieces of functionality, and you’ll see how Telligent approached testing.
Extensibility examples:
- Widgets:
  - Twitter widget controls - Creates controls to display Twitter on a page and send your Telligent Community or Telligent Enterprise status messages to Twitter.
- Modules:
  - New group avatar - Assigns a group a random avatar from the group selectable avatars store whenever a new hub is created.
  - New user random avatar - Assigns a new member a random avatar from the selectable avatars store when he/she first joins the community.
  - Notify on new user create - Sends an email to the specified email addresses when a new user joins the community.
  - Table of contents - Creates styled TOC for wikis.
- Spam rule sample:
  - Telligent.AkismetSpamRule - Integrates the Akismet spam service.

For more information, see the README file in each sample's folder.

What is contained in the platform SDK 5.5 Preview 1?

All that is included in the 5.0 version with the addition of:

Support for GETs for custom profile fields
New search API
ASP.NET MVC search site example – A reference application that provides example usage of the REST v2 search endpoint in an external application.
Track Term Search widgets
Update to the REST URLs to support .xml and .json extensions:
The recommended URL request format has been changed so that output will be specified using a .xml/.json extension, making it look more like a file extension.

REST v2 Web services continue to support old-style URLs for the time being. This support is scheduled for removal in the Telligent Evolution Platform 6.0 release (Telligent Community 6.0 / Telligent Enterprise 3.0) in favor of the new URL formatting.

Old-style URL:

http://mysite.com/api.ashx/v2/users/2100 - use default output formatting (XML)
http://mysite.com/api.ashx/v2/users/2100/xml - use XML output formatting
http://mysite.com/api.ashx/v2/users/2100/json - use JSON output formatting

New-style URL:

http://mysite.com/api.ashx/v2/users/2100.xml - use XML output formatting
http://mysite.com/api.ashx/v2/users/2100.json - use JSON output formatting

Notice that in the new platform SDK, there is no longer an option to use the default output formatter. You must explicitly identify whether the output is to be .xml or .json. The URL format has changed from using /xml to look more like a file extension with the use of .xml. We believe this change falls more in line with formats used by other popular REST web services.

As stated above, the old-style URL formatting will be honored for the time being - at least for existing endpoints. However, you should consider the old-style formatting to be deprecated because it will be removed in the Telligent Evolution Platform 6.0 release. For any current or future development, we recommend that you use the new-style URL format.

What is contained in the Platform SDK 5.5?

All that is included in the preview 1 version and:

What is contained in the Platform SDK 5.5.1?

All that is included in the 5.5 version plus:

New endpoints for blogs
New endpoints for conversations
Optional AfterDate property for getting activity messages or status messages
Verified and suggested answer counts for forum threads
Moderate forums
Approve and deny friend requests
Telligent Mobile Dashboard (Android) sample application
CommentService sample application

We have also made a few changes to the REST console:

The Endpoint URL field now defaults to the site you are accessing instead of localhost and you cannot change this URL from the current site.
We have added a drop-down list that contains all endpoint URLs. You can now select from the list and your endpoint text box is prefilled with the endpoint URL you select.
For discoverability, we have added support for displaying the types for each property in the response. You can include the types in the response by simply adding showtypes=true to the query string of the endpoint URL.

Example Info endpoint XML response without types

<?xml version="1.0" encoding="utf-8"?>

<Response>
    <InfoResult>
        <SiteName>Telligent</SiteName>
        <Product>Telligent Evolution Platform Developer Build</Product>
        <Platform>5.0.40917.7875</Platform>

        <Webservice>5.0.40917.7875</Webservice>
    </InfoResult>
</Response>

Example Info endpoint XML response with types

<?xml version="1.0" encoding="utf-8"?>

<Response>
    <InfoResult>
       <SiteName Type="string">Telligent</SiteName>
        <Product Type="string">Telligent Evolution Platform Developer Build</Product>

        <Platform Type="string">5.0.40917.7875</Platform>
        <Webservice Type="string">5.0.40917.7875</Webservice>
    </InfoResult>
</Response>

Example Info endpoint JSON response without types

{
    "InfoResult": {
        "SiteName": "Telligent",
        "Product": "Telligent Evolution Platform Developer Build",
        "Platform": "5.0.40917.7875",
        "Webservice": "5.0.40917.7875"

    }
}

Example Info endpoint JSON response without types

{
    "InfoResult": {
        "SiteName": {
            "value": "Telligent",
            "type": "string"

        },
        "Product": {
            "value": "Telligent Evolution Platform Developer Build",
            "type": "string"
        },
        "Platform": {
            "value": "5.0.40917.7875",
            "type": "string"

        },
        "Webservice": {
            "value": "5.0.40917.7875",
            "type": "string"
        }
    }
}

Download version 5.5.1 of the Telligent Evolution Platform SDK today.

Read the installation instructions.

What is contained in the Platform SDK 5.5.2?

All that is included in the 5.5.1 version plus:

Users, roles and permissions
- Delete users
- Pull current status message when retrieving user information
- Find users by email address
- Validate username/password combinations
- Create, update and delete user roles
- Add or remove users to roles
- Validate user permissions for applications and application content
Applications
- Retrieve comments for a specific file, wiki page
- Create, update or delete comments on a file, wiki page
- Retrieve, view, create, update or delete files
- Add and remove attachments when creating or updating blog posts, forum threads and forum replies
- Pull application descriptions by GroupID or AppKey
Groups
- Filter membership list by membership type (owner, manager, member, pending member)
- Pull group list by key (in addition to existing pull by GroupID)
- Pull group list for entire community
Activity stream
- Filter activities by type to view only or view all but particular activity types
- Pull site-wide and group-specific activity streams (in addition to existing user-specific activity stream)
- Include or exclude status messages from activity stream list
Site information: Pull timezone offset and serialized timezone

We've also introduced ISO date format support and made building and adding your own custom endpoints much easier with our complete end-to-end CustomEndpoint sample.

What is contained in the Platform SDK 5.6?

New APIs:

Forums
- View verified and suggested answer count and ratings for forum threads
- Moderate forums
- Add/remove attachments when creating or updating forum threads and/or replies
Blogs
- Read or write blog posts and comments
- Add/remove attachments when creating or updating blog posts
Wikis
- View comments for a specific file or wiki page
- Create, update or delete comments on a file or wiki page
Files
- View, create, update and delete files
Connections
- Start or contribute to conversations
- Approve and deny friend requests
Users
- Delete users
- Find users via email address
Activity streams
- Filter activity stream by type and included or exclude status messages
- View site-wide and group-specific activity streams (in addition to existing user-specific activity streams)
Groups
- View community-wide group list
- View group lists and application descriptions by GroupID or AppKey
- View group membership by type (owner, manager, pending member, etc.)
Site Information
- View time zone offset and serialized time zone
Roles and permissions
- Create, update and delete user roles
- Add or remove users to/from roles
- Validate user permissions for applications and content
- Validate username and password combinations

We have also included a sample widget that overlays our micro-blogging functionality on a map to visualize communications geographically.

Download the Telligent Evolution Platform SDK 5.6 today.

SDK Frequently Asked Questions

This section contains questions that are frequently asked by developers.

What is the developer license?

The developer license enables you to create a Telligent Enterprise or a Telligent Community site, against which you can then create applications or extensions. Install the license from the platform SDK to your development site.

How do I get a developer license?

Contact support to coordinate your license.

What does the developer license entitle me to do?

The developer license enables you to create a set of communities for development purposes only. You may not use the developer license to host live communities. Additionally, the developer license is limited to traffic on a local system and has a number of features restricted from use. See the table below for specifics.

Why doesn't Telligent's source code ship with the platform SDK?

No source code is included in the platform SDK because Telligent Evolution's extensibility points are through the Web services endpoints. Using the Web services will enable you to write the most feature-complete applications and customizations possible while ensuring you're protected from possibly breaking changes in internal APIs.

Are the sample applications open source software? What license are they covered under?

The samples aren't open source software. Telligent doesn't take contributions from the community back into the codebase. However, you're free to do whatever you want with the samples. All sample applications are released within the platform SDK under the MIT open source software license

Where can I find documentation for developing against Telligent Evolution?

We provide a Developer's Guide to help you develop against the Telligent Evolution platform.

Where can I discuss working with Telligent Evolution?

Join our Telligent Evolution community online, which also addresses development questions.

Related information

For information about the Platform SDK in Telligent Evolution release 6.0, see this article.

Tags: API

Getting Started: Development Environment

Alex Crome — Wed, 18 Jan 2012 11:31:16 GMT

Current Revision posted to Telligent Evolution 5.x Developer Documentation by Alex Crome on 1/18/2012 5:31:16 AM

The Telligent Evolution platform is built on top of ASP.Net 3.5. You will therefore require a version of Visual Studio 2008. If you don't already own a copy of Visual Studio 2008 you can download and install Visual Studio Web Developer Express 2008 SP1. If you have a copy of Visual Studio Web Developer Express 2005, or 2008 without SP1, you will need to upgrade to 2008 SP1. If you have a full copy of Visual Studio 2005 you need to upgrade to Visual Studio 2008. If you have Visual Studio 2008, you need to apply Service Pack 1.

If you don't have a copy of SQL Server, you will likely want to install it so you can run the Telligent Evolution platform on your computer. SQL Server Express 2005 or SQL Server Express 2008 will be suitable.

Create your project

Open Visual Studio.
Go to File> New Project and create a new "ASP.Net Web Application".
Add a class library project to your web application project. This will be where you write any custom controls and/or code for your website. Depending on what you're doing, you may prefer to make a number of class library projects to better separate your custom extensions.
Delete the existing files within the project.
Copy the contents of the /web/ folder (apart from the /bin/ folder) of the web Installer into your web project.
In Windows Explorer, open the location where you've created your two projects and add a new folder "References".
Into this References folder copy the contents of /web/bin/ in the Web Package download.
In the Visual Studio Solution Explorer, right-click the on References folder in the Web Project and select Add Reference.
In the Add References window that opens, select the Browse tab.
Navigate to the References folder and add references to all the files in this folder. You don't have to add them one by one, you can select all the files at one time and click OK.
In the Solution Explorer, expand the References folder in your Web Project, right click on System.Web.Routing > properties and set Copy Local to True.
Do the same for System.Web.Abstractions
Open the Add References Window again and click on the Projects tab.
Add a reference to the class library project(s) you created.

You have now completed setting up the project in which you can extend the Telligent Community/Evolution platform. You will now need to build your solution, set up your database, and install search.

At this point you may also want to consider checking your project into a Source Control system so you can track any changes.

Visual Studio Web Server

The Telligent Evolution Platform will run fine on the Visual Studio Web server, with the exception of any uploaded content (e.g. user avatars, media gallery posts). This is due to an incompatibility between the [[Centralized File System (CFS)]] and the Visual Studio Web Server. To work around this issue, you should do your testing on IIS where possible.

Disable Google Ping Module

The Google Ping Module will try to ping Google whenever a change is made to your site to alert Google that there's new content on your website to be indexed. This can cause timeouts when you are developing on the Telligent Evolution platform on a local machine or an internal network. Since it serves no purpose in such environments, you should remove the Module. However, remember to reinstate the module before you move your web site to a production environment.

The Google Ping Module is a [[CS Modules|CSModule]] and can be removed from the communityserver.config file by adding the following [[Override Files|override]] to a communityserver_override.config file.

<Override xpath="/CommunityServer/CSModules/add[@name='GooglePingModule']"
          mode="remove"/>

Tags: Getting Started

How to: Change the content editor

Stacy Randolph — Wed, 28 Dec 2011 22:44:41 GMT

Current Revision posted to Telligent Evolution 5.x Developer Documentation by Stacy Randolph on 12/28/2011 4:44:41 PM

name - Name of the editor.
type - Type of the implementation of ITextEditor that should be used for the editor.
resourceName - Name of a resource with a friendly name for the editor.
default (optional) - Boolean value specifying whether the editor is the default editor. If multiple editors have default set to true, then the first editor with isDefault set to true will be taken as the defalt Editor. If no editors have default set to true, then the first editor is deemed to be the default.
resourceFile (optional) - Resource file which contains the resource containing the friendly editor's name.

You can have different editor nodes using the same control type. For example you could provide two TinyMCE editors, one with a 'basic' mode which only supports bold, italics and underline, and one with an advanced mode which provides more options.

Editor Options

Each editor node can also have one or more <editorOption> nodes assosiated with it. An EditorOption node has two attributes

name - Name of the property being configured.
value - Value of the property being configured.

How these EditorOptions are used is up to the Editor Control. The DefaultTextEditor control ignores these EditorOptions, while the TinyMCE editor uses them to configure TinyMCE Configuration Options.

Overrides

When modifying or adding editors and editorOptions, you should make your modifications through a [[Override Files|communityserver_override.config]] file. Below are three sample overrides for manipulating editors and editorOptions.

Add an Editor

The following markup adds a new editor.

<Override xpath="/CommunityServer/Core/editors" mode="add">
    <editor name="myEditor"
            type="CommunityServer.Controls.DefaultTextEditor, CommunityServer.Controls"
            resourceName="MyEditor"
            default="false"
            resourceFile="customResources.xml"
            />
</Override>

Add an Editor Option

The following markup puts the standard TinyMCE editor into read only mode:

<Override xpath="/CommunityServer/Core/editors/editor[@name='Enhanced']"
          mode="add">
    <editorOption name="readonly" value="1" />
</Override>

Edit an Editor Option

The following markup disables resizing of the editor.

<Override path="/CommunityServer/Core/editors/editor[@name='Enhanced']/editorOption[@name='theme_advanced_resizing']"
          mode="change"
          name="value"
          value="false"
          />

Tags: editor

Search fields by type

Jenny Jarrard — Tue, 29 Nov 2011 20:15:02 GMT

Current Revision posted to Telligent Evolution 5.x Developer Documentation by Jenny Jarrard on 11/29/2011 2:15:02 PM

	Forum Posts	File Posts	Blog Posts	Wiki Articles	Blogs	Forums	Media Galleries	Wikis	Groups	Users	Content Pages
Type	forum	file	blog	wiki	blogapp	forumapp	fileapp	wikiapp	group	user	page
tag¹	x	x	x	x
tagkeyword²	x	x	x	x
title³	x	x	x	x	x	x	x	x	x	x	x
date⁴	x	x	x	x	x	x	x	x	x	x	x
username⁵	x	x	x	x						x
thread⁶	x
userdisplayname⁷										x
wiki⁸				x
section⁹	x	x	x		x	x	x
URL¹⁰	x	x	x	x	x	x	x	x	x	x	x
parentgroup¹¹									x
content¹²	x	x	x	x	x	x	x	x	x	x	x
rawcontent¹³	x	x	x	x	x	x	x	x	x	x	x
threadstatus¹⁴	x
grouptype¹⁵									x
attachmentname¹⁶	x	x	x
attachmenttext¹⁷	x	x	x
group¹⁸	x	x	x	x	x	x	x	x	x		x
user¹⁹	x	x	x	x	x		x			x
profile_*²⁰										x
contentid²¹	x	x	x	x	x	x	x	x	x	x	x
indexed_at²²	x	x	x	x	x	x	x	x	x	x	x

Notes

¹tag	Solr notes - Analyzed. Description/notes - Analyzed tags for the content.
²tagkeyword	Description/notes - Exact tags (lowercased) for the content. Filter on this field if you want content tagged by specific tag(s).
³title	Solr notes - Analyzed. Description/notes - Subject/title of the content.
⁴date	Description/notes - Publish date of the content.
⁵username	Description/notes - Username for the user/author.
⁶thread	Description/notes - Thread ID for the forum content.
⁷userdisplayname	Description/notes - Friendly display name for the user.
⁸wiki	Description/notes - ID of the wiki to which the content belongs.
⁹section	Description/notes - ID of the section to which the content belongs.
¹⁰URL
¹¹parentgroup	Description/notes - ID of the parentgroup.
¹²content	Description/notes - Filtered, analyzed content. Typically you want to search against this field.
¹³rawcontent	Description/notes - Unfiltered content. For posts, this is the formatted body.
¹⁴threadstatus	Possible values - NotAnswered, Answered, AnsweredNotVerified.
¹⁵grouptype	Possible values - PublicOpen, PrivateListed, Joinless, PrivateUnlisted, PublicClosed.
¹⁶attachmentname	Description/notes - Name of the post attachment.
¹⁷attachmenttext	Description/notes - Searchable text from the post attachment. This text is filtered and not intended to be displayed directly.
¹⁸group
¹⁹user	Description/notes - ID of the content author.
²⁰profile_*	Description/notes - Searchable profile fields. Only fields marked as searchable. Ex. profile_Gender.
²¹contentid	Description/notes - ID supplied by the application, ex. post ID, user ID, group ID. Not unique across documents.
²²indexed_at	Description/notes - Date (UTC) the content was indexed.

Search fields by type

Jenny Jarrard — Tue, 29 Nov 2011 20:09:42 GMT

Revision 7 posted to Telligent Evolution 5.x Developer Documentation by Jenny Jarrard on 11/29/2011 2:09:42 PM

	Forum Posts	File Posts	Blog Posts	Wiki Articles	Blogs	Forums	Media Galleries	Wikis	Groups	Users	Content Pages
Type	forum	file	blog	wiki	blogapp	forumapp	fileapp	wikiapp	group	user	page
tag¹	x	x	x	x
tagkeyword²	x	x	x	x
title³	x	x	x	x	x	x	x	x	x	x	x
date⁴	x	x	x	x	x	x	x	x	x	x	x
username⁵	x	x	x	x						x
thread⁶	x
userdisplayname⁷										x
wiki⁸				x
section⁹	x	x	x		x	x	x
URL¹⁰	x	x	x	x	x	x	x	x	x	x	x
parentgroup¹¹									x
content¹²	x	x	x	x	x	x	x	x	x	x	x
rawcontent¹³	x	x	x	x	x	x	x	x	x	x	x
threadstatus¹⁴	x
grouptype¹⁵									x
attachmentname¹⁶	x	x	x
attachmenttext¹⁷	x	x	x
group¹⁸	x	x	x	x	x	x	x	x	x		x
user¹⁹	x	x	x	x	x		x			x
profile_*²⁰										x
contentid²¹	x	x	x	x	x	x	x	x	x	x	x
indexed_at²²	x	x	x	x	x	x	x	x	x	x	x

Notes

¹tag	Solr notes - Analyzed. Description/notes - Analyzed tags for the content.
²tagkeyword	Description/notes - Exact tags (lowercased) for the content. Filter on this field if you want content tagged by specific tag(s).
³title	Solr notes - Analyzed. Description/notes - Subject/title of the content.
⁴date	Description/notes - Publish date of the content.
⁵username	Description/notes - Username for the user/author.
⁶thread	Description/notes - Thread ID for the forum content.
⁷userdisplayname	Description/notes - Friendly display name for the user.
⁸wiki	Description/notes - ID of the wiki to which the content belongs.
⁹section	Description/notes - ID of the section to which the content belongs.
¹⁰URL
¹¹parentgroup	Description/notes - ID of the parentgroup.
¹²content	Description/notes - Filtered, analyzed content. Typically you want to search against this field.
¹³rawcontent	Description/notes - Unfiltered content. For posts, this is the formatted body.
¹⁴threadstatus	Possible values - NotAnswered, Answered, AnsweredNotVerified.
¹⁵grouptype	Possible values - PublicOpen, PrivateListed, Joinless, PrivateUnlisted, PublicClosed.
¹⁶attachmentname	Description/notes - Name of the post attachment.
¹⁷attachmenttext	Description/notes - Searchable text from the post attachment. This text is filtered and not intended to be displayed directly.
¹⁸group
¹⁹user	Description/notes - ID of the content author.
²⁰profile_*	Description/notes - Searchable profile fields. Only fields marked as searchable. Ex. profile_Gender.
²¹contentid	Description/notes - ID supplied by the application, ex. post ID, user ID, group ID. Not unique across documents.
²²indexed_at	Description/notes - Date (UTC) the content was indexed.

Search fields by type

Jenny Jarrard — Tue, 29 Nov 2011 20:07:23 GMT

Revision 6 posted to Telligent Evolution 5.x Developer Documentation by Jenny Jarrard on 11/29/2011 2:07:23 PM

	Forum Posts	File Posts	Blog Posts	Wiki Articles	Blogs	Forums	Media Galleries	Wikis	Groups	Users	Content Pages
Type	forum	file	blog	wiki	blogapp	forumapp	fileapp	wikiapp	group	user	page
tag¹	x	x	x	x
tagkeyword²	x	x	x	x
title³	x	x	x	x	x	x	x	x	x	x	x
date⁴	x	x	x	x	x	x	x	x	x	x	x
username⁵	x	x	x	x						x
thread⁶	x
userdisplayname⁷										x
wiki⁸				x
section⁹	x	x	x		x	x	x
URL¹⁰	x	x	x	x	x	x	x	x	x	x	x
parentgroup¹¹									x
content¹²	x	x	x	x	x	x	x	x	x	x	x
rawcontent¹³	x	x	x	x	x	x	x	x	x	x	x
threadstatus¹⁴	x
grouptype¹⁵									x
attachmentname¹⁶	x	x	x
attachmenttext¹⁷	x	x	x
group¹⁸	x	x	x	x	x	x	x	x	x		x
user¹⁹	x	x	x	x	x		x			x
profile_*²⁰										x
contentid²¹	x	x	x	x	x	x	x	x	x	x	x
indexed_at²²	x	x	x	x	x	x	x	x	x	x	x

Notes

¹tag	Solr notes - Analyzed. Description/notes - Analyzed tags for the content.
²tagkeyword	Description/notes - Exact tags (lowercased) for the content. Filter on this field if you want content tagged by specific tag(s).
³title	Solr notes - Analyzed. Description/notes - Subject/title of the content.
⁴date	Description/notes - Publish date of the content.
⁵username	Description/notes - Username for the user/author.
⁶thread	Description/notes - Thread ID for the forum content.
⁷userdisplayname	Description/notes - Friendly display name for the user.
⁸wiki	Description/notes - ID of the wiki to which the content belongs.
⁹section	Description/notes - ID of the section to which the content belongs.
¹⁰URL
¹¹parentgroup	Description/notes - ID of the parentgroup.
¹²content	Description/notes - Filtered, analyzed content. Typically you want to search against this field.
¹³rawcontent	Description/notes - Unfiltered content. For posts, this is the formatted body.
¹⁴threadstatus	Possible values - NotAnswered, Answered, AnsweredNotVerified.
¹⁵grouptype	Possible values - PublicOpen, PrivateListed, Joinless, PrivateUnlisted, PublicClosed.
¹⁶attachmentname	Description/notes - Name of the post attachment.
¹⁷attachmenttext	Description/notes - Searchable text from the post attachment. This text is filtered and not intended to be displayed directly.
¹⁸group
¹⁹user	Description/notes - ID of the content author.
²⁰profile_*	Description/notes - Searchable profile fields. Only fields marked as searchable. Ex. profile_Gender.
²¹contentid	Description/notes - ID supplied by the application, ex. post ID, user ID, group ID. Not unique across documents.
²²indexed_at	Description/notes - Date (UTC) the content was indexed.

Search fields by type

Jenny Jarrard — Tue, 29 Nov 2011 20:05:16 GMT

Revision 5 posted to Telligent Evolution 5.x Developer Documentation by Jenny Jarrard on 11/29/2011 2:05:16 PM

	Forum Posts	File Posts	Blog Posts	Wiki Articles	Blogs	Forums	Media Galleries	Wikis	Groups	Users	Content Pages
Type	forum	file	blog	wiki	blogapp	forumapp	fileapp	wikiapp	group	user	page
tag¹	x	x	x	x
tagkeyword²	x	x	x	x
title³	x	x	x	x	x	x	x	x	x	x	x
date⁴	x	x	x	x	x	x	x	x	x	x	x
username⁵	x	x	x	x						x
thread⁶	x
userdisplayname⁷										x
wiki⁸				x
section⁹	x	x	x		x	x	x
URL¹⁰	x	x	x	x	x	x	x	x	x	x	x
parentgroup¹¹									x
content¹²	x	x	x	x	x	x	x	x	x	x	x
rawcontent¹³	x	x	x	x	x	x	x	x	x	x	x
threadstatus¹⁴	x
grouptype¹⁵									x
attachmentname¹⁶	x	x	x
attachmenttext¹⁷	x	x	x
group¹⁸	x	x	x	x	x	x	x	x	x		x
user¹⁹	x	x	x	x	x		x			x
profile_*²⁰										x
contentid²¹	x	x	x	x	x	x	x	x	x	x	x
indexed_at²²	x	x	x	x	x	x	x	x	x	x	x

Notes

¹tag	Solr notes - Analyzed. Description/notes - Analyzed tags for the content.
²tagkeyword	Description/notes - Exact tags (lowercased) for the content. Filter on this field if you want content tagged by specific tag(s).
³title	Solr notes - Analyzed. Description/notes - Subject/title of the content.
⁴date	Description/notes - Publish date of the content.
⁵username	Description/notes - Username for the user/author.
⁶thread	Description/notes - Thread ID for the forum content.
⁷userdisplayname	Description/notes - Friendly display name for the user.
⁸wiki	Description/notes - ID of the wiki to which the content belongs.
⁹section	Description/notes - ID of the section to which the content belongs.
¹⁰URL
¹¹parentgroup	Description/notes - ID of the parentgroup.
¹²content	Description/notes - Filtered, analyzed content. Typically you want to search against this field.
¹³rawcontent	Description/notes - Unfiltered content. For posts, this is the formatted body.
¹⁴threadstatus	Possible values - NotAnswered, Answered, AnsweredNotVerified.
¹⁵grouptype	Possible values - PublicOpen, PrivateListed, Joinless, PrivateUnlisted, PublicClosed.
¹⁶attachmentname	Description/notes - Name of the post attachment.
¹⁷attachmenttext	Description/notes - Searchable text from the post attachment. This text is filtered and not intended to be displayed directly.
¹⁸group
¹⁹user	Description/notes - ID of the content author.
²⁰profile_*	Description/notes - Searchable profile fields. Only fields marked as searchable. Ex. profile_Gender.
²¹contentid	Description/notes - ID supplied by the application, ex. post ID, user ID, group ID. Not unique across documents.
²²indexed_at	Description/notes - Date (UTC) the content was indexed.

Search fields by type

Jenny Jarrard — Tue, 29 Nov 2011 20:04:28 GMT

Revision 4 posted to Telligent Evolution 5.x Developer Documentation by Jenny Jarrard on 11/29/2011 2:04:28 PM

	Forum Posts	File Posts	Blog Posts	Wiki Articles	Blogs	Forums	Media Galleries	Wikis	Groups	Users	Content Pages
Type	forum	file	blog	wiki	blogapp	forumapp	fileapp	wikiapp	group	user	page
tag¹	x	x	x	x
tagkeyword²	x	x	x	x
title³	x	x	x	x	x	x	x	x	x	x	x
date⁴	x	x	x	x	x	x	x	x	x	x	x
username⁵	x	x	x	x						x
thread⁶	x
userdisplayname⁷										x
wiki⁸				x
section⁹	x	x	x		x	x	x
URL¹⁰	x	x	x	x	x	x	x	x	x	x	x
parentgroup¹¹									x
content¹²	x	x	x	x	x	x	x	x	x	x	x
rawcontent¹³	x	x	x	x	x	x	x	x	x	x	x
threadstatus¹⁴	x
grouptype¹⁵									x
attachmentname¹⁶	x	x	x
attachmenttext¹⁷	x	x	x
group¹⁸	x	x	x	x	x	x	x	x	x		x
user¹⁹	x	x	x	x	x		x			x
profile_*²⁰										x
contentid²¹	x	x	x	x	x	x	x	x	x	x	x
indexed_at²²	x	x	x	x	x	x	x	x	x	x	x

Notes

¹tag	Solr notes - Analyzed. Description/notes - Analyzed tags for the content.
²tagkeyword	Description/notes - Exact tags (lowercased) for the content. Filter on this field if you want content tagged by specific tag(s).
³title	Solr notes - Analyzed. Description/notes - Subject/title of the content.
⁴date	Description/notes - Publish date of the content.
⁵username	Description/notes - Username for the user/author.
⁶thread	Description/notes - Thread ID for the forum content.
⁷userdisplayname	Description/notes - Friendly display name for the user.
⁸wiki	Description/notes - ID of the wiki to which the content belongs.
⁹section	Description/notes - ID of the section to which the content belongs.
¹⁰URL
¹¹parentgroup	Description/notes - ID of the parentgroup.
¹²content	Description/notes - Filtered, analyzed content. Typically you want to search against this field.
¹³rawcontent	Description/notes - Unfiltered content. For posts, this is the formatted body.
¹⁴threadstatus	Possible values - NotAnswered, Answered, AnsweredNotVerified.
¹⁵grouptype	Possible values - PublicOpen, PrivateListed, Joinless, PrivateUnlisted, PublicClosed.
¹⁶attachmentname	Description/notes - Name of the post attachment.
¹⁷attachmenttext	Description/notes - Searchable text from the post attachment. This text is filtered and not intended to be displayed directly.
¹⁸group
¹⁹user	Description/notes - ID of the content author.
²⁰profile_*	Description/notes - Searchable profile fields. Only fields marked as searchable. Ex. profile_Gender.
²¹contentid	Description/notes - ID supplied by the application, ex. post ID, user ID, group ID. Not unique across documents.
²²indexed_at	Description/notes - Date (UTC) the content was indexed.

Supported Search Syntax

Jenny Jarrard — Tue, 29 Nov 2011 19:13:56 GMT

Current Revision posted to Telligent Evolution 5.x Developer Documentation by Jenny Jarrard on 11/29/2011 1:13:56 PM

The supported search syntax has changed from the previous version of Enterprise Search. Previous versions of Enterprise Search supported the majority of the Lucene syntax. When using the default search provider, Telligent Community/Enterprise search supports a simplified subset of the Lucene syntax:

+ - ex. +registration class
- - ex. registration -event
Quotes/Grouping - ex. "client API"
Field query - ex. "title:enrollment". When a field query is used, you can use Boolean operators. (View a list of fields used out of the box.)

Except when using field queries, Boolean operators are ignored. In other words, AND and OR are not processed as you might think.

The query processing in Solr is extremely configurable. Telligent Community/Enterprise uses Solr's DisMaxRequestHandler for any query that does not contain a colon (:). For queries that contain a colon, the StandardRequestHandler is used. The default behavior is for all clauses to match. When you search for the term "class enrollment", Solr (technically the DisMaxRequestHandler) will take responsibility for building a query based on the handler configuration and return documents that match the specified terms. The DisMaxRequestHandler configuration is the best place to start if you want to tune queries.

Tags: lucene

Supported Search Syntax

Jenny Jarrard — Mon, 07 Nov 2011 19:17:05 GMT

Revision 7 posted to Telligent Evolution 5.x Developer Documentation by Jenny Jarrard on 11/7/2011 1:17:05 PM

+ - ex. +registration class
- - ex. registration -event
Quotes/Grouping - ex. "client API"
Field query - ex. "title:enrollment". When a field query is used, you can use boolean operators. (View a list of fields used out of the box.)

Except when using field queries, boolean operators are ignored. In other words, AND and OR are not processed as you might think.

The query processing in Solr is extremely configurable. Telligent Community/Enterprise uses Solr's DisMaxRequestHandler for any query that does not contain a colon (:). For queries that contain a colon, the StandardRequestHandler is used. The default behavior is for all clauses to match. When you search for the terms "class enrollment", Solr (technically the DisMaxRequestHandler) will take resposiblity for building a query based on the handler configuration and return documents that match the specified terms. The DisMaxRequestHandler configuration is the best place to start if you want to tune queries.

Tags: search, syntax, solr, lucene

Implement the service provider

Jenny Jarrard — Wed, 21 Sep 2011 14:22:41 GMT

Current Revision posted to Telligent Evolution 5.x Developer Documentation by Jenny Jarrard on 9/21/2011 9:22:41 AM

The Telligent Evolution platform uses CommunityServer.Components.ISearchProvider when issuing search requests. CommunityServer.Components.ISearchProvider performs the following:

Handles (if possible and/or applicable) all properties defined on the SearchQuery class.
Should apply permissions/role checks when issuing queries. Services.Get<IRoleService>()GetAllRolesForUser(user) can be used to get a list of roles for a user.

When indexing native content (blogs, forum, etc), consider using the field names already being used within Telligent Evolution Platform. If you let the existing document mapping process behave as-is, then you will get this behavoir described in the CommunityServer.Components.Search.SearchFields class. If you plan to use the existing module (CSSearchModule) to keep content in sync, reusing existing fieldnames is very important because it has dependancies (for deletes) on data being indexed using the following field names:

SearchFields.ContentID
SearchFields.ThreadID
SearchFields.ContentType
SearchFields.UserID
SearchFields.GroupID

Method

The SearchResults Search(SearchQuery)is responsible for processing the criteria from SearchQuery and issuing a request to the search service. You should set BestMatch and BestMatchTitle on each SearchDocument in the SearchResults and highlight any query terms in these properties if highlighting is supported.

Properties

Property	Description
bool SupportsRangeQueries	Denotes whether or not the provider supports queries in which the criteria contains a range. For example, searching by a date range. Custom range queries can be implemented using the RangeFilters collection on the SearchQuery class.
bool SupportsCollapsedResults	Denotes whether or not the provider supports collapsed results. Collapsed results are when the provider can return one result for a set results. For example, returning one (most relevant) result for forum thread.
ISearchHighlightingConfiguration HighlightingConfiguration	Customizable highlighting configuration. In most situation you can use the existing implementation of CommunityServer.Components.Search.SearchConfiguration.

Implement a class

To create a class to implement the search provider interface:

Open a new class library project and create a new class that implements the ISearchProvider interface.
Implement the methods and properties for your provider and build the assembly.
Bind your search provider by:
1. Opening the \modules\SearchModule.config file for editing.
2. Updating the binding for CommunityServer.Components.ISearchProvider.
3. Specifying your new class and assembly in the "to" attribute value as shown in the following example:

<bind service="CommunityServer.Components.ISearchProvider, CommunityServer.Components"
 to="MyCustomSearch.Search.MyCustomSearchProvider, MyCustomSearch.Search"
 scope="singleton"/>

In the example above, MyCustomSearch.Search.MyCustomSearchProvider is the name of the class that implements CommunityServer.Components.ISearchProvider and MyCustomSearch.Search is the name of the assembly (without the .dll extension) that contains this class.

Touch the web.config file so the new settings take effect.

Sample: Group Sitemap Build

Jenny Jarrard — Wed, 21 Sep 2011 14:20:29 GMT

Current Revision posted to Telligent Evolution 5.x Developer Documentation by Jenny Jarrard on 9/21/2011 9:20:29 AM

The GroupSitemapBuild project. included in version 5.5 of the Telligent Evolution Platform SDK, was developed as a reference application for the Groups endpoint of the Platform APIs. It is a console application that builds an XML sitemap for a Telligent Evolution platform site showing the groups, subgroups and applications in groups (blogs, forums, galleries, and wikis). It is not meant to build a complete sitemap of every page in your site but only serve as sample code for working with the Groups endpoint.

Platform API Groups Endpoint

The Groups Sitemap Builder makes use of the Platform API Groups Endpoint. See the Groups endpoint documentation for details.

Platform API Search Endpoint

The Groups Sitemap Builder makes use of the REST v2 Search Endpoint. See the Search endpoint documentation for details.

GroupSitemapBuilder.Console Project

The GroupSitemapBuilder.Console sample is a console application that builds two versions of sitemap, based on your site's groups and applications (blogs, forums, galleries, wikis). One sitemap is a sitemap.xml file that uses the Sitemaps.org 0.9 schema for web site sitemaps, which is the format recommended by Google. The second sitemap, sitemap.html, is a simple HTML document that displays your site's groups hierarchy in an unnumbered list (<ul>) format.

The GroupSitemapBuilder consists of several thin layers: the console program itself, a Service layer, a Repository layer, and helper functionality like Mappers and extension methods.

The two classes in the Entities folder, Group and App, are lightweight objects that are local representations of the Telligent Evolution Platform's Group and application (Blog, Forum, Gallery, and Wiki) classes.

The RestRepository class makes requests to the proper REST endpoint and returns the resulting XML.

The Mappers class includes methods for mapping the API's returned XML to an entity, Group or App.

The RestService class performs the majority of the work of the application. It provides a simple interface for requesting a group or groups, calls to the RestRepository to get the returned XML from the API, converts the XML to entities using the Mapper functions and then returns the entities to the calling code.

SitemapExtensions.cs contains extension methods for the Group and App entities for formatting output.

Program.cs is the console application itself. It sets up the RestService passing in the site url, username, and API key to use for the API calls, gets the group hierarchy, and then prints the results to two files using the ToHtml() and ToSiteMap() extension methods for the Group entity.

Notes

To create a sitemap of your site:

Set your site Url, username (of a user with permission to access web services and impersonate other users), and the REST Token for that user in the Main method of the Program.cs file.
Build the GroupSitemapBuilder.Console project
Hit F5 to run the console app (or browse to the output .exe file and run it via the command line).
Two files will be created in your current folder (which is your /bin/Debug or /bin/Release folder in Visual Studio) a sitemap.xml file, your sitemap file, and a sitemap.html file which is a simple HTML document that shows your Group structure in a simple <ul> list format.

Additional Notes:

For this sample project to work properly your Telligent Evolution platform site must have the REST API enabled. You can enable the REST API via the control panel: Site Administration > Site Configuration > Manage REST API.
For this sample project to work properly the user that you specify in step one above must have permissions that allow them to access the REST API. The "Site - Access Web Services" and "Site - Impersonate Users" permissions must be assigned to a role that the user is assigned to. You can manage permissions via the control Panel: Membership Administration > Members and Roles > Manage Site Roles.
The accessing user, set in step #1 above must have an API Key created. You can create an API key by editing your Settings, clicking the Site Options tab, clicking on the Create and Edit Application Keys link at the bottom of the page, and adding an API Key if you do not already have one.
This sample application uses the admin user to impersonate the "Anonymous" user so that the sitemap that is created is what a non-logged in user (having the same permissions as the "Everyone" role) would see when accessing your site. The Anonymous user normally does not have permissions to access web services. You will have to temporarily assign the Anonymous user to a role that does have the "Site - Access Web Services" permission to run this sample application. We do not recommend that you do so for your live site. We recommend only running this sample application on a local or staging site. Should you decide to give the Anonymous user elevated privileges to run the sample application you should remember to remove those elevated privileges as soon as possible.

Tags: Sample

Telligent Evolution 5.x Developer Documentation

Alex Crome — Fri, 16 Sep 2011 15:01:04 GMT

Revision 21 posted to Telligent Evolution 5.x Developer Documentation by Alex Crome on 9/16/2011 10:01:04 AM

The Telligent Evolution Platform is the foundation for the Telligent Community and Telligent Enterprise applications.

Are you looking for user documentation? Please visit our end-user Telligent Evolution platform documentation.

Getting Started, How to, and Sample Articles

Getting Started - Articles in the Developer Documentation that help you get started with the Telligent Platform.
How To - Articles in the Developer Documentation that explain how to accomplish specific developer level extensions or problems within the Telligent Platform.
Samples - Samples that show, through code that you can download, how to accomplish specific tasks within the Telligent Platform.
Tips & Tricks - Tips and tricks for working with the Telligent platform.

Developer Documentation Topics

Platform APIs - The Platform APIs enable you to build on top of the Telligent Evolution platform to deliver new applications or integrate with existing applications. Applications that you build can also be shared in the Telligent Marketplace.
CSS / Style Markup Guide - Modifying the user experience, whether for Telligent Community or Telligent Enterprise, can be accomplished through CSS and other style changes. This documentation provide guidance on the CSS classes used within the platform.
Theme Customization - For extending the design of your community to better match the exact design specifications for your website or brand we've created some detailed Theme Customization guides.
Configuration & Tasks - Details the various configuration files, their associated settings, and how to work with override files. Details around Telligent's background processing architecture, Telligent Tasks, is covered here as well.
Widgets - Building widgets (simple, reusable UI components) enables you to create new functionality directly embedded into your Telligent application. Widgets can be as simple as embedding some JavaScript or richer widgets that integrate with other popular technologies like Salesforce.com.
Event based modules - With Telligent's event-based framework you can plug into various events to change behavior, format text, handle authentication, and numerous other tasks that extend out the base set of capabilities.
Localization and Internationalization - Store text strings in an external resource file, called a language pack. By creating a resource file for each language you're supporting, you can show each user text in their own language.
Extending Search - You can create your own search provider to get search results from a different source, or your own index provider to customize how files are indexed.
Centralized File System - All files uploaded to Telligent Evolution are stored using the Centralized File System (CFS). You can leverage the Centralized File System (CFS) to store your own files or manipulate existing files. Because the CFS is pluggable, this means you can store files in 3rd party document management systems such as Microsoft's SharePoint or in the cloud such as with Amazon.

Getting a status message

Dan Hounshell — Tue, 06 Sep 2011 20:54:51 GMT

Current Revision posted to Telligent Evolution 5.x Developer Documentation by Dan Hounshell on 9/6/2011 3:54:51 PM

New in Telligent Evolution platform SDK 5.5.2.

EndpointGETapi.ashx/v2/users/{username}/statuses/{messageid}.xml (or .json)

EndpointGETapi.ashx/v2/users/{userid}/statuses/{messageid}.xml (or .json)

RequestStatusMessageShowRequest

UserId	Optional	Either the UserId or Username is required.
Username	Optional	Either the UserId or Username is required.
MessageId	Optional	MessageId
Include	Optional	Only option is replies. Ex: include=replies

Example (C#)

var webClient = new WebClient();

// replace the "admin" and "Admin's API key" with your valid user and apikey!
// http://telligent.com/community/developers/w/wiki/how-to-generate-an-api-key.aspx
var adminKey = String.Format("{0}:{1}", "Admin's API Key", "admin");
var adminKeyBase64 = Convert.ToBase64String(Encoding.UTF8.GetBytes(adminKey));

webClient.Headers.Add("Rest-User-Token", adminKeyBase64);

var requestUrl = "http://mysite.com/api.ashx/v2/users/2100/statuses/846628AC-E23A-4F5B-A7E6-FF19120429E4.xml?include=replies"; // or .json
var xml = webClient.DownloadString(requestUrl);

Console.WriteLine(xml);

Example Response (XML)

<?xml version="1.0" encoding="utf-8"?>
<Response>
  <Info />
  <Warnings />
  <Errors />
  <StatusMessage>
    <Id>846628ac-e23a-4f5b-a7e6-ff19120429e4</Id>
    <Author>
      <Id>2100</Id>
      <AvatarUrl>http://mysite.com/utility/anonymous.gif</AvatarUrl>
      <DisplayName>sample-data98f58</DisplayName>
      <ProfileUrl>http://mysite.com/members/admin/default.aspx</ProfileUrl>
      <Username>admin</Username>
    </Author>
    <Body>sample-85535datad6a41</Body>
    <CreatedDate>2010-06-28T14:31:57.6</CreatedDate>
    <ReplyCount>0</ReplyCount>
    <HasReplies>false</HasReplies>
    <ReplyMessages>
        <ReplyMessage>
            <Id>a18a16a2-7dc1-4bb4-9405-8b3cc074ed50</Id>
            <Author>
                <Id>2100</Id>
                <AvatarUrl>http://mysite.com/cfs-file.ashx/__key/communityserver-components-selectableavatars/03b2c875-fbfb-4d26-8000-ef001b9f4728/avatar.png</AvatarUrl>
                <DisplayName>admin</DisplayName>
                <ProfileUrl>http://mysite.com/members/admin/default.aspx</ProfileUrl>
                <Username>admin</Username>
                <CurrentStatus />
            </Author>
            <Body>&lt;a href="http://localhost/cs/members/admin/default.aspx" class="internal-link view-user-profile"&gt;admin&lt;/a&gt;: sample reply 2</Body>
            <CreatedDate>2011-09-06T16:31:17.977</CreatedDate>
            <ParentId>846628ac-e23a-4f5b-a7e6-ff19120429e4</ParentId>
        </ReplyMessage>
    </ReplyMessages>
  </StatusMessage>
</Response>

Example Response (JSON)

{
  "StatusMessage": {
    "Author": {
      "AvatarUrl": "http://mysite.com/utility/anonymous.gif",
      "DisplayName": "sample-data98f58",
      "ProfileUrl": "http://mysite.com/members/admin/default.aspx",
      "Username": "admin",
      "Id": 2100
    },
    "Body": "sample-85535datad6a41",
    "CreatedDate": "\/Date(1277749917600-0400)\/",
    "ReplyCount": 0,
    "Group": null,
    "HasReplies": false,
    "Replies": [ {
        "Author": {
            "AvatarUrl": "http://mysite.com/cfs-file.ashx/__key/communityserver-components-selectableavatars/03b2c875-fbfb-4d26-8000-ef001b9f4728/avatar.png",
            "DisplayName": "admin",
            "ProfileUrl": "http://mysite.com/members/admin/default.aspx",
            "Username": "admin",
            "CurrentStatus": null,
            "Id": 2100 },
        "Body": "<a href=\"http://localhost/cs/members/admin/default.aspx\" class=\"internal-link view-user-profile\">admin</a>: sample reply 1", 
        "CreatedDate": "2011-09-06T16:31:11.873",
        "ParentId": "9fdaa0b1-695d-4b64-a7a7-923fb1064320",
        "Id": "846628ac-e23a-4f5b-a7e6-ff19120429e4" }
    ],
    "Id": "846628ac-e23a-4f5b-a7e6-ff19120429e4"
  },
  "Info": [],
  "Warnings": [],
  "Errors": []
}

Email Templates

Jenny Jarrard — Thu, 01 Sep 2011 19:58:25 GMT

Current Revision posted to Telligent Evolution 5.x Developer Documentation by Jenny Jarrard on 9/1/2011 2:58:25 PM

All the emails sent out by the Telligent Evolution platform can be customized, both how they look and what information they contain. In the email templates, tokens are used to specify information. When the email is sent, the tokens are replaced by the correct values they represent (i.e. $Subject -> "Subject of blog post"). Each template has a different set of tokens that are available to it, along with several global tokens that are available to all templates.

All templates are listed below along with the tokens available to the template.

This page applies only to Telligent Evolution 5.x/2.x.

How to change email templates:

Navigate to the email template folder, can be found in the Web/Languages/<your language>/emails folder.
Find the name of the template that you want to change/edit.
The templates are stored as .txt files. Thus to change the forumpost_threadmovenotification template open up forumpost_threadmovenotification.txt in any text editor.
The list of available tokens is given below (along with the Global Terms).

Global Terms

A list of terms that are available on all templates is available on the [[Global Term tokens|Global Terms]] page.

contactform

$appTitle - string - The name of the blog or group.
$body - string - The body of the message.
$email - string - The email address of the sender.
$link - string - The URL of the home page of the blog or group.
$name - string - The name of the sender.
$subject - string - The subject provided by the user.
$to - string - The email address of the owner of the blog or group.

contactform_usertouser

$post - [[Post token|Post]] - The message being sent.
$user - [[User token|User]] - The recipient of the message.

followers_notification

$follower - [[Follower token|Follower]] - The relationship of the follower.

forgottenpasswordwithtoken

$forgottenpasswordurl - string - The URL where the user can change their password.
$ip - string - The IP host address of the remote client.
$user - [[User token|User]] - The user who forgot their password.

forumpost_threadmovednotracking

$post - [[Post token|Post]] - The post to the forum being moved.
$user - [[User token|User]] - The user being notified of the thread move.

forumpost_threadmovenotification

$post - [[Post token|Post]] - The post to the forum being moved.
$user - [[User token|User]] - The user being notified of the thread move.

forumpost_messageapproved

$post - [[Post token|Post]] - The post to the forum being approved.
$user - [[User token|User]] - The author of the post.

forumpost_messagemoved

$post - [[Post token|Post]] - The post to the forum being moved.
$user - [[User token|User]] - The author of the post.

forumpost_messagemovedandapproved

$post - [[Post token|Post]] - The post to the forum being moved and approved.
$user - [[User token|User]] - The author of the post.

forumpost_messageremoved

$moderatedBy - [[User token|User]] - The moderator who removed the post.
$post - [[Post token|Post]] - The post to the forum being removed.
$reason - string - The reason for the removal provided by the moderator.
$user - [[User token|User]] - The author of the post.

forumpost_notifyforumdisabled

forumpost_notifymoderators

$user - [[User token|User]] - The moderator who is being notified.

forumpost_notifynopermission

$message - [[Message token|Message]] - The message sent to the disabled forum.
$section- [[Section token|Section]] - The mailing list the message was sent to ($section.Name should match the forum name.)
$group - [[Group Token|Group]] - The group containing the forum/mailing list.
$userIsMember - boolean - True if the user is a member of the group, false otherwise.

forumpost_notifythreadstarterofsuggestedanswer

$currentUser - [[User token|User]] - The user whoe verified the post as an answer.
$post - [[Post token|Post]] - The post which was verified as an answer.
$rejectAnswer - string - The URL to reject the answer.
$user - [[User token|User]] - The user who posted the thread starter question.
$verifyAnswer - string - The URL to verify the suggested answer.

forumpost_threadnotification

$post - [[Post token|Post]] - The post which started a new thread.
$user - [[User token|User]] - The user who subscribed to this thread.

friendship_approved

$friendship - [[Friendship token|Friendship]] - The relationship of the friendship.

friendship_requested

$friendship - [[Friendship token|Friendship]] - The relationship of the friendship.

friendship_requested_nomessage

$friendship - [[Friendship token|Friendship]] - The relationship of the friendship.

group_accessaccepted

$group - [[Group token|Group]] - The group access has been granted to.
$user - [[User token|User]] - The user being granted access.

group_accessrequest

$group - [[Group token|Group]] - The group the membership request is for.
$message - string - The message provided by the user requesting access to the group.
$owner - [[User token|User]] - The owner of the group.
$user - [[User token|User]] - The user making the request for membership.

group_accessrequestdenied

$group - [[Group token|Group]] - The group access has been denied to.
$user - [[User token|User]] - The user being denied access.

group_messages_also_replied

$message - [[Reply Message token|Reply Message]] - The reply to the message thread.
$parent - [[Message token|Message]] - The first message in the conversation (the group message).
$recipient - [[User token|User]] - The user that commented in the message thread.
$replies - [[Reply Message token|Reply Message]] - The list of all replies to the parent group message.

group_messages_reply

$message - [[Reply Message token|Reply Message]] - The reply to the parent group message.
$parent - [[Message token|Message]] - The first message in the conversation (the group message).
$recipient - [[User token|User]] - The user the message who posted the status message.
$replies - [[Reply Message token|Reply Message]] - The list of all replies to the parent group message.

group_useradded

$group - [[Group token|Group]] - The group user has been added to.
$user - [[User token|User]] - The user being added to the group.

mediagallerypost_commentnotification

$parentPost - [[Post token|Post]] - The media gallery post the comment is for.
$post - [[Post token|Post]] - The comment to the media gallery post.
$user - [[User token|User]] - The recipient of the comment notification.

mediagallerypost_newcomment

messages_also_replied

$message - [[Reply Message token|Reply Message]] - The reply to the message thread.
$parent - [[Message token|Message]] - The first message in the conversation (the status message).
$recipient - [[User token|User]] - The user that commented in the message thread.
$replies - [[Reply Message token|Reply Message]] - The list of all replies to the parent status message.

messages_newconversationmessage

$conversation - [[Conversation token|Conversation]] - The conversation between the various participants.
$message - [[Message token|Message]] - The message in the conversation directed to the recipient user.
$user - [[User token|User]] - The user the recipient of the message.

messages_newprofilecomment

$message - [[Profile Message token|Profile Message]] - The comment on the profile.
$user - [[User token|User]] - The user who received the comment (the profile's owner).

messages_reply

$message - [[Reply Message token|Reply Message]] - The reply to the parent status message.
$parent - [[Message token|Message]] - The first message in the conversation (the status message).
$recipient - [[User token|User]] - The user the message who posted the status message.
$replies - [[Reply Message token|Reply Message]] - The list of all replies to the parent status message.

newuser_accountcreated

$user - [[User token|User]] - The user who created an account.

newuser_approved

$user - [[User token|User]] - The user whose account was approved.

newuser_generatedpassword

$user - [[User token|User]] - The user created an account with a generated password.

newuser_pending

$user - [[User token|User]] - The user who has attempted to join the site and is awaiting approval.

newuser_rejected

$user - [[User token|User]] - The user whose account was rejected.

roleemail

$user - [[User token|User]] - The recipient of the message, a member of the role.
$post - [[Post token|Post]] - The post containing the message for the user.
$roleName - string - The name of the role the message was sent to.

user_changedpassword

$user - [[User token|User]] - The user who change their password.

user_forgottenpassword

$user - [[User token|User]] - The user who requested to be sent a new password.

userinvitation

$invitation - [[User Invitation token|User Invitation]] - The invitation to the new user.
$user - [[User token|User]] - The user who invited the recipient to the community.

userinvitation_withsection

$invitation - [[User Invitation token|User Invitation]] - The invitation to the new user.
$user - [[User token|User]] - The user who invited the recipient to the section/group.

weblog_feedbacknotification

$parent - [[Post token|Post]] - The blog post given the feedback.
$post - [[Post token|Post]] - The new blog feedback, which may need approval.
$user - [[User token|User]] - The user who subscribed to new comments.

weblog_moderationthreshold

$section - [[Blog token|Blog]] - The blog that needs moderation attention.
$user - [[User token|User]] - Blog owner who can moderate the blog.

weblog_newcomment

$post - [[[Post token|Post]] - The new blog comment.
$user - [[User token|User]] - The user who subscribed to new comments.

weblog_newpost

$post - [[Post token|Post]] - The new blog post.
$user - [[User token|User]] - The user who subscribed to new posts.

weblog_subscriptionconfirmation

$section - [[Blog token|Blog]] - The subscribed blog.
$user - [[User token|User]] - The user who has subscribed to the blog.

wikis_definitespam

$page - [[Wiki Page token|Wiki Page]] -The wiki page that has been flagged as possible spam.
$user - [[User token|User]] - The user with permission to delete the wiki page to send the email to.

wikis_pageupdated

$page - [[Wiki Page token|Wiki Page]] - The updated wiki page.
$revision - [[Wiki Page Revision token|Wiki Page Revision]] - The previous version of the wiki page.
$user - [[User token|User]] - The user who subscribed to updates to the wiki page.

wikis_possiblespam

$page - [[Wiki Page token|Wiki Page]] - The wiki page that has been flagged as possible spam.
$user - [[User token|User]] - The user with permission to delete the wiki page to send the email to.

Tags: email

Telligent Evolution Platform Software Development Kit

Jenny Jarrard — Wed, 31 Aug 2011 21:40:25 GMT

Revision 44 posted to Telligent Evolution 5.x Developer Documentation by Jenny Jarrard on 8/31/2011 4:40:25 PM

The Telligent Evolution Platform Software Development Kit (SDK) gives you examples and guidance for creating powerful features that are custom-tailored to your own needs.

A new version of the platform SDK (version 5.6) is now available.

What is contained in the platform SDK 5.0?
What is contained in the platform SDK 5.5 Preview 1?
What is contained in the Platform SDK 5.5?
What is contained in the Platform SDK 5.5.1?
What is contained in the Platform SDK 5.5.2?
What is contained in the Platform SDK 5.6?
What is the developer license?
How do I get a developer license?
What does the developer license entitle me to do?
Why doesn't Telligent's source code ship with the platform SDK?
Are the sample applications open source software? What license are they covered under?
Where can I find documentation for developing against Telligent Evolution?
Where can I discuss working with Telligent Evolution?

What can I do with the Telligent Evolution platform SDK?

What is contained in the platform SDK 5.0?

The platform SDK contains the source code for sample applications:

Stand-alone applications:
- Bahbl - Reference application used to drive out v2 REST endpoints. Bahbl is a Twitter-like application that shows you how to use profiles, activity messages, authentication, and other key features of the Evolution REST infrastructure.
- New User Uploader Tool - Short, practical tool showing you how to create new users from a comma separated value (.csv) file.
Integration tests used to exercise and validate the Telligent Evolution Web services. These are the tests Telligent used during the development of v2 REST Web services. You’ll see exactly how you can implement very granular pieces of functionality, and you’ll see how Telligent approached testing.
Extensibility examples:
- Widgets:
  - Twitter widget controls - Creates controls to display Twitter on a page and send your Telligent Community or Telligent Enterprise status messages to Twitter.
- Modules:
  - New group avatar - Assigns a group a random avatar from the group selectable avatars store whenever a new hub is created.
  - New user random avatar - Assigns a new member a random avatar from the selectable avatars store when he/she first joins the community.
  - Notify on new user create - Sends an email to the specified email addresses when a new user joins the community.
  - Table of contents - Creates styled TOC for wikis.
- Spam rule sample:
  - Telligent.AkismetSpamRule - Integrates the Akismet spam service.

For more information, see the README file in each sample's folder.

What is contained in the platform SDK 5.5 Preview 1?

All that is included in the 5.0 version with the addition of:

Support for GETs for custom profile fields
New search API
ASP.NET MVC search site example – A reference application that provides example usage of the REST v2 search endpoint in an external application.
Track Term Search widgets
Update to the REST URLs to support .xml and .json extensions:
The recommended URL request format has been changed so that output will be specified using a .xml/.json extension, making it look more like a file extension.

REST v2 Web services continue to support old-style URLs for the time being. This support is scheduled for removal in the Telligent Evolution Platform 6.0 release (Telligent Community 6.0 / Telligent Enterprise 3.0) in favor of the new URL formatting.

Old-style URL:

http://mysite.com/api.ashx/v2/users/2100 - use default output formatting (XML)
http://mysite.com/api.ashx/v2/users/2100/xml - use XML output formatting
http://mysite.com/api.ashx/v2/users/2100/json - use JSON output formatting

New-style URL:

http://mysite.com/api.ashx/v2/users/2100.xml - use XML output formatting
http://mysite.com/api.ashx/v2/users/2100.json - use JSON output formatting

Notice that in the new platform SDK, there is no longer an option to use the default output formatter. You must explicitly identify whether the output is to be .xml or .json. The URL format has changed from using /xml to look more like a file extension with the use of .xml. We believe this change falls more in line with formats used by other popular REST web services.

As stated above, the old-style URL formatting will be honored for the time being - at least for existing endpoints. However, you should consider the old-style formatting to be deprecated because it will be removed in the Telligent Evolution Platform 6.0 release. For any current or future development, we recommend that you use the new-style URL format.

What is contained in the Platform SDK 5.5?

All that is included in the preview 1 version and:

What is contained in the Platform SDK 5.5.1?

All that is included in the 5.5 version plus:

New endpoints for blogs
New endpoints for conversations
Optional AfterDate property for getting activity messages or status messages
Verified and suggested answer counts for forum threads
Moderate forums
Approve and deny friend requests
Telligent Mobile Dashboard (Android) sample application
CommentService sample application

We have also made a few changes to the REST console:

The Endpoint URL field now defaults to the site you are accessing instead of localhost and you cannot change this URL from the current site.
We have added a drop-down list that contains all endpoint URLs. You can now select from the list and your endpoint text box is prefilled with the endpoint URL you select.
For discoverability, we have added support for displaying the types for each property in the response. You can include the types in the response by simply adding showtypes=true to the query string of the endpoint URL.

Example Info endpoint XML response without types

<?xml version="1.0" encoding="utf-8"?>

<Response>
    <InfoResult>
        <SiteName>Telligent</SiteName>
        <Product>Telligent Evolution Platform Developer Build</Product>
        <Platform>5.0.40917.7875</Platform>

        <Webservice>5.0.40917.7875</Webservice>
    </InfoResult>
</Response>

Example Info endpoint XML response with types

<?xml version="1.0" encoding="utf-8"?>

<Response>
    <InfoResult>
       <SiteName Type="string">Telligent</SiteName>
        <Product Type="string">Telligent Evolution Platform Developer Build</Product>

        <Platform Type="string">5.0.40917.7875</Platform>
        <Webservice Type="string">5.0.40917.7875</Webservice>
    </InfoResult>
</Response>

Example Info endpoint JSON response without types

{
    "InfoResult": {
        "SiteName": "Telligent",
        "Product": "Telligent Evolution Platform Developer Build",
        "Platform": "5.0.40917.7875",
        "Webservice": "5.0.40917.7875"

    }
}

Example Info endpoint JSON response without types

{
    "InfoResult": {
        "SiteName": {
            "value": "Telligent",
            "type": "string"

        },
        "Product": {
            "value": "Telligent Evolution Platform Developer Build",
            "type": "string"
        },
        "Platform": {
            "value": "5.0.40917.7875",
            "type": "string"

        },
        "Webservice": {
            "value": "5.0.40917.7875",
            "type": "string"
        }
    }
}

Download version 5.5.1 of the Telligent Evolution Platform SDK today.

Read the installation instructions.

What is contained in the Platform SDK 5.5.2?

All that is included in the 5.5.1 version plus:

Users, roles and permissions
- Delete users
- Pull current status message when retrieving user information
- Find users by email address
- Validate username/password combinations
- Create, update and delete user roles
- Add or remove users to roles
- Validate user permissions for applications and application content
Applications
- Retrieve comments for a specific file, wiki page
- Create, update or delete comments on a file, wiki page
- Retrieve, view, create, update or delete files
- Add and remove attachments when creating or updating blog posts, forum threads and forum replies
- Pull application descriptions by GroupID or AppKey
Groups
- Filter membership list by membership type (owner, manager, member, pending member)
- Pull group list by key (in addition to existing pull by GroupID)
- Pull group list for entire community
Activity stream
- Filter activities by type to view only or view all but particular activity types
- Pull site-wide and group-specific activity streams (in addition to existing user-specific activity stream)
- Include or exclude status messages from activity stream list
Site information: Pull timezone offset and serialized timezone

We've also introduced ISO date format support and made building and adding your own custom endpoints much easier with our complete end-to-end CustomEndpoint sample.

What is contained in the Platform SDK 5.6?

New APIs:

Forums
- View verified and suggested answer count and ratings for forum threads
- Moderate forums
- Add/remove attachments when creating or updating forum threads and/or replies
Blogs
- Read or write blog posts and comments
- Add/remove attachments when creating or updating blog posts
Wikis
- View comments for a specific file or wiki page
- Create, update or delete comments on a file or wiki page
Files
- View, create, update and delete files
Connections
- Start or contribute to conversations
- Approve and deny friend requests
Users
- Delete users
- Find users via email address
Activity streams
- Filter activity stream by type and included or exclude status messages
- View site-wide and group-specific activity streams (in addition to existing user-specific activity streams)
Groups
- View community-wide group list
- View group lists and application descriptions by GroupID or AppKey
- View group membership by type (owner, manager, pending member, etc.)
Site Information
- View time zone offset and serialized time zone
Roles and permissions
- Create, update and delete user roles
- Add or remove users to/from roles
- Validate user permissions for applications and content
- Validate username and password combinations

We have also included a sample widget that overlays our micro-blogging functionality on a map to visualize communications geographically.

Download the Telligent Evolution Platform SDK 5.6 today.

What is the developer license?

How do I get a developer license?

Contact support to coordinate your license.

What does the developer license entitle me to do?

Why doesn't Telligent's source code ship with the platform SDK?

Are the sample applications open source software? What license are they covered under?

Where can I find documentation for developing against Telligent Evolution?

We provide a Developer's Guide to help you develop against the Telligent Evolution platform.

Where can I discuss working with Telligent Evolution?

Join our Telligent Evolution community online, which also addresses development questions.

Tags: developer, API, sdk

Platform API - Documentation

Jenny Jarrard — Wed, 31 Aug 2011 20:54:38 GMT

Current Revision posted to Telligent Evolution 5.x Developer Documentation by Jenny Jarrard on 8/31/2011 3:54:38 PM

The Telligent Evolution Platform APIs are implemented as RESTful services exposed by a custom-built REST engine. Routing is supported via Microsoft's new System.Web.Routing engine, which shipped with Microsoft's ASP.NET MVC project. Our Web services currently support data in POX (Plain Old XML) and JSON. Depending on customer demand, we may support other formats such as ATOM in the future.

PUT/DELETE method overloads

Because PUT/DELETE methods are disabled on some Web servers (such as IIS), you must specify a Rest-Method header with these values and an HTTP Method of POST.

Updating (PUT) a User resource:

/api.ashx/v2/users/1
Http Header contains: Rest-Method: PUT
Http Method: POST

Deleting (DELETE) a User resource:

/api.ashx/v2/users/1
Http Header contains: Rest-Method: DELETE
Http Method: POST

Data type specifications

By default, all data types are sent and received as XML. You can also use JSON instead of XML by specifying JSON in your URL: /api.ashx/v2/users/1.json [GET]. This request returns the User resource matching the ID in JSON format. When POSTing with JSON, the POST and the response are in the same format.

Standard date format

The standard date format for REST v2 requests and responses is the ISO format of:
yyyy-MM-ddTHH:mm:ss. When using .NET's DateTime.ToString() method there is a shortcut for this format: dateTime.ToString("o").

Currently, the dates in JSON responses are formatted by default using the following:
"\/Date(1273255122713-0400)\/" . Beginning with the 5.5.2 release, there is an option on all requests to format dates in the ISO format using the parameter of UseIsoDateFormat. Setting it to true will use the ISO date format. Setting it to false or not setting it will use the older style format. These defaults will remain in place through the 6.0 release. Following the 6.0 release, the default will be changed to use the ISO date format. This will align the standard date formats across Telligent Evolution platform REST v2 Web services.

The Telligent Evolution platform REST v2 Web services framework will parse any valid DateTime input format that the .NET framework DateTime.Parse() method recognizes (if sending data as XML then it has to be a format the XML Serializer recognizes as well). However, we recommend using the ISO date format standard of yyyy-mm-ddThh:mm:ss for consistency across requests and responses.

Available endpoints

The following endpoints (resources) are available in the Telligent Evolution platform API:

(n.b. additional endpoints are available through the [[Web Services V1 API|V1 API]])

API	HTTP Verbs	Description
[[Activity Messages]]	GET, POST	Retrieves a list of activity messages or creates a list of activity messages. This can include individual user updates, updates from within groups, and updates from external applications, e.g., document updates from Microsoft SharePoint.
[[Blog posts and comments]]	GET, POST	Gets blog post details or comments as well as creating and updating blog posts and comments, or delete a post or comment.
[[Content file storage]]	GET	Gets a file for content streaming.
[[Content search]]	GET, POST	Pulls content from the search index and pushes content into the index remotely, including custom fields.
[[Conversations]]	GET, POST	Gets or deletes conversation messages or entire conversations; creates a new conversation, or adds a message to an existing one.
[[Follower]]	GET, POST	Used to manage follow status between users. Following is different than Friendship. Friendship implies a mutual relationship, whereas Follow implies a 1-way relationship, i.e. you can follow a user without that user reciprocating a follow to you.
[[Forum]]	GET, POST	Creates, deletes, or retrieves forum replies and threads; retrieves active, moderated, unanswered, unread, or personal forum threads. Gets forum details or update a forum reply.
[[Friendships]]	GET, POST	Used for social networking aspects of the Telligent platform, the API can be used to retrieve a list of a users friends, create new connections, remove a relationship, or update it.
[[Groups]]	GET, POST	Returns the list of all groups to which a user belongs; retrieve all groups or a particular group; retrieve a group's members; get details about a particular group, or add and delete a group member.
[[Media galleries]]	GET, POST	Creates, deletes, or updates a media gallery comment; creates or deletes a media gallery post; retrieves a post or comments; gets details about the gallery
[[Roles and permissions]]	GET, POST	Returns permission information for the core applications supported within the Telligent platform (blogs, wikis, forums, etc.). Creates or deletes a role; retrieves a user's role permissions or permission for the role itself; gets a list of roles, and gets a user's list of roles.
[[Search]]	GET	Returns search results for a query term. Only available with Telligent Evolution 5.5
[[Site]]	GET	Retrieves site endpoints or information.
[[Status Messages]]	GET, POST	Publishing status messages into the Activity Stream. These can be short text statements that users contribute, e.g., "I love the new widgets in Telligent Evolution 5.5" and can also be used by applications to publish updates. Create a status message or reply, and get either single or all status messages.
[[User Presence]]	GET, POST	Retrieves one user's presence, all friends' presences, or all users' presences; updates a user's presence.
[[Users]]	GET, POST	Retrieves individual and lists of users and supports the ability to update a user. adds or deletes users; gets details about a user; gets all users; sets a user's profile fields with POST; updates a specific user or his/her preferred language, and validates a user's password. Access to custom profile fields via the ProfileFields node is available only with Telligent Evolution 5.5
[[Wiki]]	GET, POST	Creates or gets a wiki page; retrieves a wiki table of contents (document hierarchy); retrieves details about a wiki, and updates a wiki page.

Users

Jenny Jarrard — Wed, 31 Aug 2011 20:52:34 GMT

Current Revision posted to Telligent Evolution 5.x Developer Documentation by Jenny Jarrard on 8/31/2011 3:52:34 PM

Via the endpoints, you can:

Add a user
Remove a user
Retrieve the details for a user
Retrieve a list of users
Update a user's ProfileFields using HTTP POST
Update a user
Update a user's preferred language to another supported language
Create one or more user and update custom profile fields
Update a specific user and his/her profile fields
Retrieve a user by ID and his/her used profile field values
Retrieve a list of users in the site and a list of all used profile fields
Validate a user's password

Item	Get	Post
All users	All users
Specific user	A specific user	Add a new user account Set user's ProfileFields when using HTTP POST Validating a user's password Deleting a user Update a user account Updating a user's preferred language
Users with profile fields	[[Users with ProfileFields node]]	[[Users with ProfileFields node]] [[Users with ProfileFields node]]

Users

Jenny Jarrard — Wed, 31 Aug 2011 20:51:09 GMT

Revision 21 posted to Telligent Evolution 5.x Developer Documentation by Jenny Jarrard on 8/31/2011 3:51:09 PM

Via the endpoints, you can:

Add a user
Remove a user
Retrieve the details for a user
Retrieve a list of users
Update a user's ProfileFields using HTTP POST
Update a user
Update a user's preferred language to another supported language
Create one or more user and update custom profile fields
Update a specific user and his/her profile fields
Retrieve a user by ID and his/her used profile field values
Retrieve a list of users in the site and a list of all used profile fields
Validate a user's password

Item	Get	Post
All users	All users
Specific user	A specific user	Add a new user account Set user's ProfileFields when using HTTP POST Validating a user's password Deleting a user Update a user account Updating a user's preferred language
Users with profile fields	[[Users with ProfileFields node]]	[[Users with ProfileFields node]] [[Users with ProfileFields node]]

Telligent Evolution 5.x Developer Documentation

How to: Configure CFS File Store

Telligent Evolution Platform Software Development Kit

In this Article

What can I do with the Telligent Evolution platform SDK?

What is contained in the platform SDK 5.0?

What is contained in the platform SDK 5.5 Preview 1?

What is contained in the Platform SDK 5.5?

What is contained in the Platform SDK 5.5.1?

What is contained in the Platform SDK 5.5.2?

What is contained in the Platform SDK 5.6?

SDK Frequently Asked Questions

What is the developer license?

How do I get a developer license?

What does the developer license entitle me to do?

Why doesn't Telligent's source code ship with the platform SDK?

Are the sample applications open source software? What license are they covered under?

Where can I find documentation for developing against Telligent Evolution?

Where can I discuss working with Telligent Evolution?

Related information

Getting Started: Development Environment

In this Article

Create your project

Visual Studio Web Server

Disable Google Ping Module

How to: Change the content editor

In this Article

Editor Options

Overrides

Add an Editor

Add an Editor Option

Edit an Editor Option

Search fields by type

Notes

Search fields by type

Notes

Search fields by type

Notes

Search fields by type

Notes

Search fields by type

Notes

Supported Search Syntax

Supported Search Syntax

Implement the service provider

In this Article

Method

Properties

Implement a class

Sample: Group Sitemap Build

In this Article

Platform API Groups Endpoint

Platform API Search Endpoint

GroupSitemapBuilder.Console Project

Notes

Telligent Evolution 5.x Developer Documentation

Getting Started, How to, and Sample Articles

Developer Documentation Topics

Getting a status message

Email Templates

In this Article

How to change email templates:

Global Terms

contactform

contactform_usertouser

followers_notification

forgottenpasswordwithtoken

forumpost_threadmovednotracking

forumpost_threadmovenotification

forumpost_messageapproved

forumpost_messagemoved

forumpost_messagemovedandapproved

forumpost_messageremoved

forumpost_notifyforumdisabled

forumpost_notifymoderators

forumpost_notifynopermission

forumpost_notifythreadstarterofsuggestedanswer

forumpost_threadnotification

friendship_approved

friendship_requested