Telligent Community

Forum Post: RE: Duplicate Emails

Billy — Fri, 10 Feb 2012 18:38:00 GMT

Emails are only in Job Scheduler.

-- The duplicate emails are very random also. It will not send duplicates out every time.

-- Am i correct assumeing that the service checks the DB email queue and if messages exist it sends them..

Sometimes for some reason the service does not believe it connected to the mail server and leaves the message in the queue and 2 minutes later on retry the message(s) are delivered for the second time.

Not sure if there is a place to allow for a longer time out before email message is considered failed or some other solution.

Thanks

Wiki: Telligent Community 6

Anonymous — Thu, 09 Feb 2012 22:22:00 GMT

Forum Post: User Banner Bug

bazqpr — Thu, 09 Feb 2012 17:51:00 GMT

Have noticed the very same bug on this site as well, click into your user profile pages, the user banner contains the link Update Profile, select any tab other than profile and the link remains, click on the link you know get the button to save profile without having any profile fields to edit, just the same user content you were viewing

Wiki Page: Install Telligent Community

Jenny Jarrard — Thu, 09 Feb 2012 16:22:00 GMT

Installation notes

If you open the Telligent Community zip file using Internet Explorer or Chrome, you may need to first right-click the.zip file and select Properties, then click Unblock if the option is available. Click OK to close Properties.
If installing Telligent Community into a sub-directory, settings may be inherited from your parent application's web.config which cause a web.config error when you run your community. In such cases, you will have to add <clear /> or <remove /> elements in your Community web.config file to remove the additions made in your parent web.config.
If you set up your database to be case sensitive, you may experience future issues with names matching in sign-in or places that use a name on the URL to identify the location (groups, users, or blogs). See this article.
The instructions for creating an application pool assume you're using IIS7. If you're using IIS6, see the Microsoft documentation.
.NET framework version 4.0 is required for Telligent Community 6.0.
If you are running Windows Server 2008 without SP2, you should install KB958854 to resolve some issues with .NET 4.0. Windows Server 2008 SP2 and Windows Server 2008 R2 are unaffected by this issue.
If you're using Windows XP for development purposes, your network service user is ASP.NET. If you're using Windows Server 2003, your network service user is NETWORK SERVICE. If you're using Windows Server 2008, your user is IIS APPPOOL\<application pool you create>.
Search is required for Telligent Community 6.0.
In Telligent Community 6.0, most tasks should be executed in their own Job Scheduler service.
Job Scheduler's default user is NETWORK SERVICE. If you're using Windows Server 2008, you'll need to assign NETWORK SERVICE the same folder and database appropriate permissions you assign the service user.
In Telligent Community 6.0, Job Scheduler's logging is turned on by default.

Obtain Telligent Community

Obtain the installation package from Telligent Support.
Extract the contents of the download to a temporary location on your hard drive (e.g., C:\inetpub\TempFolderUnzipBuild\ ).

Installation components

This installation procedure has been divided by installation area so that multiple administrators can install different aspects of a Telligent Community site.

Web server
Database server
Search server
Tasks server
Caching server

Web server

This procedure assumes you already have [[internet information services (iis) configuration|IIS installed]], and have configured the Database and Search servers.

Copy the files

Create a Web directory folder and copy the files there:

Create a path to hold the Telligent Community Web site (e.g., C:\inetpub\Telligent Evolution\). Note that the root folder path should be as short as possible to provide enough path space to the CFS.
In the extracted .zip file folder, copy all of the zip file's web folder contents and paste them into the server's directory folder, leaving the directory structure intact.

Create the Web site in IIS

If you are using Windows Server 2003 or Windows Server 2008, create a new application pool. (If using Windows XP for development purposes, skip this step.)
1. Open Internet Information Services (IIS) Manager.
2. If required, connect to your Web server.
3. In the Connections pane, expand your Web server.
4. Right-click Application Pools and select Add Application Pool.
5. Specify a name for your application pool.
6. Ensure that the [[supported software versions for servers, applications, and browsers|correct Net framework version]] is selected.
7. Click OK.
Create the IIS application.
1. In IIS's left pane, navigate to Internet Information Services > [computer name] > Web Sites > Default Web Site.
2. Right-click Default Web Site, select Add Application.
  
  The Add Application window appears.
3. Do the following:
  - Enter a name in the alias field (example: Telligent Evolution).
  - Select the application pool you created in Step 2.
  - Enter the path you created in Step 1 in the Physical path field (example: C:\inetpub\Telligent Evolution).
4. Click OK.
Determine your Web site service account. This account will be needed for granting permissions in the next step and in the Database section.
- If using Windows XP for development purposes, your service account is ASPNET.
- If using Windows Server 2003 or Window Server 2003 R2, your service account is NETWORK SERVICE.
- If using Windows Server 2008, Vista or higher, follow these steps to find the service account that your Web service is running under:
  1. Open IIS Manager and navigate to Application Pools.
  2. Use the value of the identity column to determine your Web site service account.
    - LocalService - NT AUTHORITY\LOCAL SERVICE
    - LocalSystem - NT AUTHORITY\SYSTEM
    - NetworkService - NT AUTHORITY\NETWORK SERVICE
    - ApplicationPoolIdentity - IIS APPPOOL\<app pool name>
    - OTHER - runs as the specified user

For further details on optimizing the performance of your Web server, see [[Web server configuration check-list|Web server and IIS configuration]].

Set file permissions

Add the network service user to the permission structure. Then grant the Web site service account required file and folder permissions: read permissions to the web directory (which is the main directory for IIS) and modify permissions for web/filestorage/ and its sub-folders.
1. Right-click the Telligent Community Web site folder and select Edit Permissions.
2. Click the Security tab. (If you are using Windows Server 2008 and above or Windows Vista and above, click Edit.)
3. Click Add.
4. In the Enter the object names text box, type the name of the service account determined above. Click OK.
5. Ensure that the service account is selected in the top pane, and view the bottom Permissions pane to ensure that only the read permission is granted.
6. Click OK.
7. Repeat the above instructions, but this time assign rights for the web/filestorage folder instead of the Telligent Community Web site folder. In addition to Read, grant the service account Modify, Read & execute, List folder contents, and Write permissions.

Configure the connectionstrings.config file

You can't configure the connectionstrings file until after you create the database.

Update connectionstrings.configin the Web site to point to the database on your database server.
For assistance with connection strings, you can refer to http://connectionstrings.com. (Telligent has no affiliation with the site.)
Open the connectionstrings.config file in your Web site, and update the SiteSqlServer entry to point to the database.
- If using [[Windows Authentication]] to connect to the database, the connection string should look something like:
```
<add name="SiteSqlServer"
  connectionString="server=SERVERNAME;database=DATABASENAME;Trusted_Connection=yes;" 
  />
```
- If using SQL authentication, the connection string should look something like:
```
<add name="SiteSqlServer" 
  connectionString="server=SERVERNAME;uid=USERNAME;pwd=PASSWORD;database=DATABASENAME;Trusted_Connection=no;"
  />
```
- If you're using SQL Express for development purposes, the SERVERNAME in the connection string may be (local)\SQLExpress as opposed to just (local).
```
<add name="SiteSqlServer"
  connectionString="server=(local)\SQLExpress;database=DATABASENAME;Trusted_Connection=yes;"
  />
<add name="SiteSqlServer"
  connectionString="server=(local)\SQLExpress;uid=USERNAME;pwd=PASSWORD;database=DATABASENAME;Trusted_Connection=yes;"
  />
```
Check that you can access your Telligent home page.
1. Open your Telligent URL.
2. Check that the home page successfully loads without error.
3. If an error occurs, check that you've followed the above steps correctly.
This should only be a quick test - any functionality that requires search will not work yet.
If you are hosting a site in a Web farm or if your Web application will be restarted frequently (such as under very strict and/or limiting memory requirements), add an entry for an explicit machine key to the web.config file under <system.web> in order to prevent viewstate decoding errors:
1. Navigate to http://aspnetresources.com/tools/machineKey. This site generates a unique machine key.
2. Place this entry within the <system.web> node of the web.config file.

Configure the search URL

Important: Solr should never be accessible to the public. Ensure that neither the Tomcat home page nor the Solr home page is publicly accessible. If this endpoint is accessible, work with your IT department or read [[Securing Solr on Tomcat]] for more details on blocking this endpoint from the public.

Ensure that all Web servers can access the Solr home page by opening to the Solr home page on each server ( e.g., http://<servername or localhost>:8080/solr/ ).
Configure Telligent Community to use your Solr URL:
1. Download the following communityserver_override.config file.
2. Place this file in the root of your Web site directory.
3. Find the following section in the communityserver_override.config file and replace PathToSolr with the URL to your Solr instance (e.g., http://localhost:8080/solr/).
```
<Override xpath="/CommunityServer/Search/Solr"  
          mode="change"
          name="host"
          value="http://yourserver:XXXX/PathToSolr"
          />
```
The Solr path URL is case-sensitive.

Search won't work until you have Job Scheduler set up.

Database server

Create the database

For further details on optimizing the performance of your database server, see Database Configuration and Database Maintenance.

Create a new database in SQL Server.

Open SQL Server Management Studio and connect to your database server with an account that has sysadmin or dbcreator fixed server privileges.
Right-click Databases and select New Database. The New Database window appears.
In the Database name field, enter a name for the database. (Example: Telligent Evolution.) If needed, see Microsoft's instructional documentation for help.
Click OK.

Create schema

Populate the database by executing the cs_CreateFullDatabase.sql script from the \SqlScripts\ folder of the install package.

In SQL Server Management Studio, navigate to File > Open > File. The Open File dialog window appears.
Navigate to the temporary location where you unzipped the installation package and within that folder, to SqlScripts.
Double-click cs_CreateFullDatabase.sql.
Select the database you created in step 1 of this Database section.
Execute the query against the database.

Create community

Create the community by executing the cs_System_CreateCommunity stored procedure.

In the SQL Server Management Studio toolbar, click New Query.

This will open a blank tab in the right pane.
Copy and paste the following script into the new query tab.
```
EXECUTE[dbo].[cs_system_CreateCommunity]
    @SiteUrl = N'localhost/telligent_evolution' 
  , @ApplicationName = N'telligent_evolution' 
  , @AdminEmail = N'notset@localhost.com' 
  , @AdminUserName = N'admin' 
  , @AdminPassword = N'pa$$word' 
  , @PasswordFormat = 0 
  , @CreateSamples = 0
```
where you specify the appropriate values for each parameter:
- SiteURL: The path to your site. This should be the same path you expect to access your community with (e.g., localhost/telligent_evolution as in the script above, or Telligent Evolution in the examples we've been using above).
- ApplicationName: Name of the application you created in IIS (e.g., N'Telligent Evolution as in the case of the examples we've been using above).
- AdminEmail: The email address of the administrator of the site. (optional)
- AdminUserName: Login username for the administrator. You can leave this blank if you are running the application on your local PC on a limited basis.
- AdminPassword: Default password for the administrator. You can set this to whatever you would like to use as the password for the administrative user (you can leave this blank if you are running the application on your local PC on a limited basis). We strongly recommend you do NOT use the default password in your live site. (optional)
- PasswordFormat: 0 to store the password in the database in clear text. This can be changed to encrypt the password after it is created. (optional)
- CreateSamples: 0 if you do NOT want sample content, 1 if you want sample content created in your community. (optional)
Select your database name from the database drop-down list on the toolbar.
Click Execute.

Once you have created your community, we recommend you create a new administrator account and delete the one you created when setting up your community. This is to ensure that your administrator account's password is encrypted in the database. (While it is possible to encrypt the administrator account's password when you create the community, you need to provide the hashed password for the @AdminPassword parameter, which starts getting more complicated than it's worth, given the easy workaround.)

Create login and grant permissions

If you have not already done so, create a login to your server.
1. In SQL Server's Object Explorer pane, expand your server and then expand the Security folder.
2. Right-click the folder and select New Login. The Login - New window appears.
3. Enter the name of your service.
4. Click OK.
Create a login for your database.
1. In SQL Server's Object Explorer pane, expand the database Security folder, then right-click Users and select New User. The Database User - New window appears.
2. If you want Telligent Community to connect to the database via Windows Authentication, select General and then specify the database login name as the username of the service account user determined above. If you want Telligent Community to connect to the database using SQL authentication, then specify any username in the Login name text box.
  We recommend using Windows Authentication. If you want to use SQL authentication, make sure your SQL server supports mixed-mode authentication.
3. Click OK.
Grant the database login access to the Telligent Community database. (This is shown in the bottom of the previous screen capture.)
1. In the bottom (Database role membership) pane, ensure only the following roles are checked:
  - aspnet_Membership_FullAccess
  - aspnet_Profile_FullAccess
  - db_datareader
  - db_datawriter
  - db_ddladmin
2. Click OK and close SQL Server Management Studio.

Set up maintenance

For this information, see [[Database maintenance]].

Search server

Install Java

Install Java on the search server. Remember that if you are using 64-bit Tomcat, you will need to use 64-bit Java.

Test whether Java is already installed by viewing http://java.com/en/download/help/testvm.xml on the search server. In Telligent Community, search requires at least version 6 update 13. If your installation meets this requirement, skip to the Install Tomcat step below.
- If you're using a 64-bit operating system, you must view this test page in a 64-bit browser (such as Internet Explorer 64-bit edition which comes pre-installed on all 64-bit versions of Windows).
Download the latest version of java from http://java.com/en/download/index.jsp .

Install Tomcat

Install Tomcat. Remember that if you are installing 64-bit Tomcat, you need to match it with 64-bit Java.

Download version 6 of the Tomcat Windows Service Installer (32-bit/64-bit Windows Service Installer, apache-tomcat-6.0.30.exe) from Apache. Take note of the following:
1. In the Choose Components window, ensure you have selected the the Tomcat > Service and Tomcat > Native options.
2. In the Choose Install Location window, make a note of the installation directory - this will be needed in the next step.
Update Tomcat to support UTF8 characters:
1. Open the /conf/server.xml file in the installation directory you selected in step b.B.
2. Find the 8080 <Connector /> element in the server.xml file, and add the attribute uriencoding="UTF-8"
```
<server>
 <service>
   <connector port="8080" uriencoding="UTF-8">
     ...
   </connector>
 </service>
</server>
```
Test that Tomcat is installed correctly by navigating to http://localhost:8080/.

Set up Solr

If you have any issues with search, see [[Troubleshoot search errors]].

Install Solr.
If you want to run multiple Telligent communities from the same search server, follow the instructions at [[Host multiple Telligent Community communities on multiple Solr instances]] instead.
1. Copy the Solr folder in the /Search/ directory of the Telligent Community install files to the root directory of Apache Tomcat (e.g., c:\Program Files\Apache Software Foundation\Tomcat 6.0).
2. Copy the solr.war file in this folder to the /webapps directory of Apache Tomcat.
3. Navigate to the Solr administration page (http://localhost:8080/solr/admin/) to verify that the installation was successful.

Solr runs very well as configured out of the box. But if you have a medium to large-sized community, you should increase the memory allocated to the Java virtual machine (JVM). The default allocated memory is 64MB. You should consider giving it 512MB or more.
To increase the memory for the JVM:

Right-click the Tomcat Manager in the system tray and select Configure.
Select the Java tab.
Set the Maximum memory pool size (in MB) that you want to allocate to the JVM.

Tasks server or Job Scheduler

Make sure the Web site is up and running before proceeding with this step.

Install the Job Scheduler

Review the contents of the Telligent Community Suite package that contained the platform files used in the primary platform installation. Inside the root of this archive should be a folder entitled (Tasks).
Create a destination folder for the Job Scheduler. We typically recommend C:\Program Files\Telligent\Job Scheduler\ (Program Files (x86) for 64-bit OSes).
Copy all files from the installation directory of the package (step 1) into the folder created in step 2.
Run install.bat as administrator (right-click the file and select Run as administrator) to install the Job Scheduler service.
Copy your connectionstrings.config file from the Telligent Community site over the connectionstrings.config file in the Job Scheduler directory, or simply update connectionstrings.config there to point to your database.

Copy your communityserver_override.config file from your Telligent Community site into the Job Scheduler directory. View the file and ensure that the filestorage location is correct. (If not, change the file to reflect the location.) If you do not have an override file, you need to create one from here and then update the location of the filestorage folder (value attribute below).

   <Override xpath="/CommunityServer/CentralizedFileStorage/fileStore[@name='Telligent.Evolution.Components.Attachments']"        mode="change"        name="basePath"        value="c:\path\to\your\filestorage"              />

 <Override xpath="/CommunityServer/CentralizedFileStorage/fileStore[@name='Telligent.Evolution.Components.Attachments.Temporary']"        mode="change"        name="basePath"        value="c:\path\to\your\filestorage"              />

 <Override xpath="/CommunityServer/CentralizedFileStorage/fileStore[@name='CommunityServer.Components.MultipleUploadFileManager']"        mode="change"        name="basePath"        value="c:\path\to\your\filestorage"              />

Note: Paths for CFS file stores should be updated to be absolute (i.e., full path and not using the ~/ prefix).

If you are using Windows Server 2008, you need to add the NETWORK SERVICE user to the web and filestorage folders with the same permissions and create a user for it in the server and database. (It may already exist in the server.)
Open services (services.msc at the command prompt) and start the Telligent Job Scheduler service. The service should start automatically after the initial run. One way to verify that Job Scheduler is working is to confirm that search is indexing (by adding some content to the site and trying to search for a term it it, then receiving the correct response). If it is not working, refer to this article.

Optional installations

Install [[Install the Mail Gateway|Mail Gateway]].
Set up a Caching Server
If you plan to use Telligent Analytics, perform the following steps. If you do not do so, you will not be gathering Web Analytics data.

In your Telligent Community site's web.config file, locate the <modules> section in <system.webServer>. Uncomment the JavascriptAnalyticsHttpModule line.

Locate the <handlers> section, and uncomment the analytics and analyticsUrls handlers.

Optional: If your Telligent Community site is running on a Web farm, ensure that steps 1 and 2 occur on all Web servers.

If you have trouble...

Please refer to the Telligent Community Troubleshooting Guide.

Wiki Page: Database configuration

Jenny Jarrard — Thu, 09 Feb 2012 16:18:00 GMT

SQL Server 2008 64-bit

SQL Server is a robust DBMS on any hardware, but given that 64-bit architecture is reasonable and readily available, we recommend that you use 64-bit hardware and of course the 64-bit versions of SQL Server for installations. This goes for both SQL Server 2005 and 2008. We recommend that you use SQL Server 2008.

Database disk I/O management

The database file system configuration is much more important than the Web server file system in terms of design. A system administrator needs to be concerned about the integrity of their disks, plan for easily expandable growth, have a good balance between disk reads/writes, and plan for system failure and recovery.

See Telligent's recommended database disk configurations for optimal database I/O performance.

Database memory

After the installation, consider adjusting the memory for the SQL Server Service. If you right-click the server (with SQL Server Manager), choose Properties and select the Memory tab. You can set the Maximum Server memory (in MB) as shown in the following screen shot.

We recommend that you allocate 80-85% of server memory for SQL Server. The optimal hardware configuration for the database is dedicated hardware with 16GB+ of memory.

We recommend that your services be dedicated to their own hardware; however, if your environment dictates that you have IIS and SQL Server running on the same machine, you will need to adjust these values accordingly. For a baseline the server needs 15-20% of the system RAM. Then split the RAM so 60% is used for SQL Server and up to 40% for IIS.

Collation

Server collation is the sort order and the case sensitivity of the data within the databases. Setting the collation at the installation time for the default collation of the databases is the best time. This is so that all of the system databases (master, msdb, model and tempdb) are created with the same sort order that the user databases would use. This allows for better interoperability.

If you use a case sensitive database, there might be issues with names matching in sign-in or places that use a name on the URL to identify the location (groups, users, or blogs).

Initial database size

The initial size of the database is very important. Planning the size of your community is not a one-time event: it should be evaluated at least once every six months.

We recommend that you plan for one year's growth when setting the initial database size - not only for the community's sake, but also for your file system. Even for smaller communities it is better to use a much larger introductory data file. For a lightweight community you should start with a 1GB data file size and 64MB log file size. Fewer expansions of the data files means that there are fewer file fragments on the hard disk. This is important for consistency at a raw file level.

Database sizing formula

Use the table below to approximate the total amount of storage required when sizing the disk space needed for your SQL Server database:

Feature / Capability	Storage Required
Users ^{see note}	3.04 kb
Roles	1 kb
Blog posts	45 kb
Blog comment	3 kb
Forum thread	4 kb
Forum reply	1 kb
Media	1.2 kb
Media comment	3 kb
Wiki page ^{see note}	45 kb
Wiki comment	3 kb
Metadata factor	12%

The formula assumes the default set of user profile properties and on average one revision of a wiki document.

The metadata factor % is a value that adds a percentage of the core data to the total size.

Sizing formula = (Number of Items * Item Storage Required) * 112%

For example, assuming 100,000 users at 3.04kb per-user, you would plan for 296.88MB of storage with an additional 35.6MB of metadata for a total storage requirement of 332.5MB.

Each configuration is unique. Some installations will have more user storage with custom user properties whereas other installations will have multiple revisions of Wiki documents.

Autogrowth SQL settings

Use the sizing recommendations in database sizing formula when creating your data file. There are two directions to take regarding autogrowth on SQL Server data and log files:

If your environment is consistent with monitoring the size of the data in the SQL files and the physical size of the files themselves, then there should be no autogrowth at all. At a minimum, sizing should be checked at least once a quarter and adjusted as least once every six months. This is the preferred direction.
If your environment is more lenient you can continue to set AUTOGROWTH in terms of megabytes. Start with 128 MB. This is a small enough value that it can grow with hardly any contention and you shouldn't have issues with getting "out of space" errors.

Recommendations

If you are space-confined, set your maximum file size so that you do not exhaust all available space on your disk. We recommend that you have a minimum of 40% free space on the disk. Anything less than 40% free could jeopardize any substantial database grow that may occur in the future.

For the database log file, take the same considerations into account. Transactions in Telligent Community are generally not very large, so you could size your log file much smaller such as, 64 MB or 128 MB. Your autogrowth could be set to something much smaller as well, such as16MB or 32 MB. You will find discussions on tracking growth later in this guide.

Database maintenance

Maintenance is not always considered when deploying a database; however, we have found that maintenance can be a critical component to maintaining the health of a database. As a general rule all tables with clustered indexes should be reindexed on a schedule. We recommend that you do this once a week. However, depending on your community's activity, you may want to do this once a month.

Telligent Community includes a number of database maintenance scripts.

Database reindex

We include the cs_system_dbreindex stored procedure in the Telligent Community codebase.cs_system_dbreindex can be scheduled (via a SQL Job) to reindex clustered indexes.

Table statistics

Table statistics should be updated on days that reindexing does not occur. Again, there is a stored procedure included in the Telligent Community codebase called cs_system_updatestatistics that can be scheduled for this purpose.

Database growth

We have also found that people generally do not track physical database and log growth over time. Tracking table and index growth over time gives you an idea of how fast your community is growing and can give you an idea of what your disk space needs will be.

Tracking physical database growth can be done with the SQL Server stored procedure sp_spaceused on a table-by-table basis. Additionally, the number of rows per table is a good metric. The number of rows per table provides you with the averages of the growth of your data over time within your community.

Database backups

We recommend that you schedule a single full-database backup once a week, a differential backup each day (not on full backup days), and log backups for the maximum recovery time you are allotted for your site.

For more information about backup options refer to:

http://msdn.microsoft.com/en-us/library/ms187510.aspx

For additional data about backup schedules refer to

http://vyaskn.tripod.com/sql_server_administration_best_practices.htm

Even though older versions of SQL Server are specified, the processes are the same.

Database tracing

The most effective way to determine problems within the database (related to performance) is through SQL Profiler. An exhaustive review of SQL Profiler can be found here.

Forum Post: Select Tags

vlai — Wed, 08 Feb 2012 19:26:00 GMT

When writing a post, it seems that the max number of tags that "Select Tags" popup displays is 100. Is there a way to increase the number, or to choose which 100 tags to be displayed ourselves? We are using Telligent Community 5.6.

Forum Post: Mobile Version

ckuhlow — Wed, 08 Feb 2012 17:05:00 GMT

Does anyone have a mobile version of Telligent Community up and running that they could share? Besides the Telligent site that is. I'd be interested to see how others are using this module.

Forum Post: RE: Anti XSS implemented with $core_v2_page.GetFormValue

Alex Crome — Wed, 08 Feb 2012 16:51:00 GMT

Nope - it simply returns the raw form values..

Any validation for cross site scripting should be done before echoing user inputed data directly in the response (this can be done using the $core_v2_encoding.javascriptEncode(...) method)

Forum Post: RE: Migrating Forums from Drupal to Telligent

Patrick Mason — Wed, 08 Feb 2012 15:19:00 GMT

You should check with whatever medium is available support wise for Drupal on how to extract forum and user data from that system.

In terms of importing to Telligent Community the safest method is to take whatever medium you extracted to and import the data to your Telligent based community using the REST apis available.

http://telligent.com/community/developers/w/developer6/endpoint-documentation.aspx

Patrick Mason
Development Lead- Extensibility
o: 214.420.1329
telligent.com

From: Awais Kazimi [mailto:bounce-AwaisKazimi@communities.telligent.com]
Sent: Wednesday, February 08, 2012 9:14 AM
To: bugsandissues@communities.telligent.com
Subject: [Bugs and Issues - Telligent Community] Migrating Forums from Drupal to Telligent

Hi,

We are trying to migrate Drupal forums to Telligent platform. Surely, the database structure (and how information is stored) is different in the two platforms.

Is there any way to export drupal forums with users and taxonomies (and taxonomy access restrictions to users) to Telligent platform, so that our forum may be imported "as it is" to Telligent

Thanks

Forum Post: RE: Change archived posts 'RSS Post Excerpt Size'

Patrick Mason — Wed, 08 Feb 2012 14:13:00 GMT

All hotfixes should be obtained via support

Patrick Mason
Development Lead- Extensibility
o: 214.420.1329
telligent.com

From: Leo [mailto:bounce-LeoNel@communities.telligent.com]
Sent: Tuesday, February 07, 2012 9:53 PM
To: bugsandissues@communities.telligent.com
Subject: RE: [Bugs and Issues - Telligent Community] Change archived posts 'RSS Post Excerpt Size'

Anyone have the download for May, 2011 Hot Fix Release?

Forum Post: RE: 6.0 Installation.

Praful Memane — Wed, 08 Feb 2012 08:37:00 GMT

There was a similar problem reported and a reason provided by Alex Crome telligent.com/.../1355083.aspx

Forum Post: RE: Link to a theme stylesheet for a modal popup that uses a velocity macro for the modal content source

Michael Monteleone — Tue, 07 Feb 2012 21:46:00 GMT

For this scenario, I would recommend instead to use

$core_v2_page.RenderThemeHeaders("%{ IsModal = true/false }") within your <head> tag in your modal dialog velocity callback.

This will render theme-defined CSS, Javascript, and other headers along with any headers registered through $core_v2_page (AddLink, AddMeta, SetTitle, etc) and common javascript (jQuery, jQuery validate, GLOW, and Evolution jQuery plugins). It specifically includes stylesheets defined by the theme for use in modals.

Hope this helps.

Forum Post: RE: Link to my profile in main navigation

larisa kraus — Tue, 07 Feb 2012 15:34:00 GMT

AdminConnect did it this answer the question?

Forum Post: RE: Hotfix for the Telligent Community 6.0 ie7 Modal Bug?

Brian — Mon, 06 Feb 2012 19:50:00 GMT

Thanks Brian.

Forum Post: RE: How to include custom jQuery plugin on a theme level

Alex Crome — Mon, 06 Feb 2012 19:13:00 GMT

Personally I'd recommend you upload the Javascript file into the Javascript files of your Site Theme configuration.

An alternative approach is to create a custom widget which you add to the site wide header/footer which you use to reference your javascript file.

Forum Post: RE: Cannot run local install of Telligent Community in Visual Studio

Alex Crome — Mon, 06 Feb 2012 12:24:00 GMT

Telligent Community is incompatible with the Visual Studio Web Development server - the urls used by the CFS don't work in Cassani.

You will either need to install VS2010 SP1 and use IIS Express, or run your community in a full install of IIS.

Forum Post: RE: Bulk Edit/Delete Users Awaiting Approval

Bruce Cirrinone — Sun, 05 Feb 2012 17:01:00 GMT

Thanks, Rick! This led me to some more research. I found out that in my case, only two tables were affected: cs_Users and cs_UserProfile and I was able to compose two delete queries that removed all member/applicants except the 46 my client had really approved. Once again, I appreciate your assistance!!!

Forum Post: RE: TC 5.5 - Media Gallery REST API Endpoint returns 404 error

Patrick Mason — Fri, 03 Feb 2012 22:35:00 GMT

It will include instructions. There are a few different things you will need to apply. I believe in it will be a folder called REST updates if I remember correctly

Patrick Mason
Development Lead- Extensibility
o: 214.420.1329
telligent.com

From: lucasrd [mailto:bounce-lucasrd@communities.telligent.com]
Sent: Friday, February 03, 2012 4:23 PM
To: bugsandissues@communities.telligent.com
Subject: RE: [Bugs and Issues - Telligent Community] TC 5.5 - Media Gallery REST API Endpoint returns 404 error

Are there specific files or assemblies we could just drop in to make it work if I got that version of the platform code?

Wiki Page: Working with contextual URLs in Sitecore

Jenny Jarrard — Fri, 03 Feb 2012 19:16:00 GMT

Contextual URLs defined

Several widgets in Telligent rely on a specific context or contextual data in order to display their contents properly. A widget used out of context either does not render at all or can result in errors. Telligent uses several techniques to determine context, but if you follow all of the paths to get contextual data, the root source of information is usually in the URL.

Types of contextual data

Contextual data is simply an object for which the content of the widget is based. For example, if you read a blog post, the contextual object is a specific blog post. Without it, the widget does not know what post in which blog you want to display. Some widgets function using contextual data but can also be set to a specific item. For example, the Blog - Post List widget is smart enough to determine whether it is in the context of a blog or a group, and will list blog posts depending on which is available. However, via widget configuration you can also set the blog or group specifically, bypassing the contextual data.

Contextual data currently supported

Group
Blog
Blog
User
Forum
Forum Thread
Forum Reply
Media Gallery
Media File

These items can all be determined from a URL, or determined based on a child item that is currently in context (such as a blog from a contextual blog post).

How context is retrieved in Sitecore

Telligent Connect for Sitecore uses the concept of wildcard items to define dynamic pieces of data in a URL. When rendering pages, the tree path usually determines your URL, matching the names of items specifically in the tree hierarchy. If you add a wildcard instead of a proper name for an item (which is done by giving the item a name * instead of a proper name), it will use this item to match any value at that place in the hierarchy that is not already specifically defined. For example, a path of /item1/subitem1/* will match /item1/subitem1/something.aspx or /item1/subitem1/12345.aspx.

Mappings, tokens and routes

The first part of understanding how to use wildcards with Telligent Connect for Sitecore is to understand some of the components. Most of the information explained here is set up for you. If you are starting a new community, you can leave the defaults in place.

Tokens (master: /sitecore/system/modules/TelligentEvolution/Urls/Tokens)

Tokens represent placeholders. They are used to replace the wildcard characters behind the scenes with an identifiable value. For example, a wildcard path like so /item/item2/*/* has no way of deciphering the first wildcard from the second. These values will be replaced by token values so that they can be easily identified as the data they represent, like a group ID or application key. You should never have to alter the values of tokens.

Position mappings (master: /sitecore/system/modules/TelligentEvolution/Urls/Position Mappings)

Position mappings define which wildcards in an item path will be replaced by what token value so they can later be extracted. A mapping is a collection of positions that define the wildcard's numeric position, or occurrence in the path, and the token to use to replace it. Consider our previous URL of /item/item2/*/*. A mapping you could create for this would have two positions: one for each wildcard and a token assigned to each position. The number of positions defined in the mapping are the minimum number of wildcards required in the path. The example below shows the default mapping for a blog post. It has three positions: GroupID, BlogKey, and Post Key. This means when we define a path for a blog post, we expect it to contain at least three wildcards (i.e., one for each position). We also then replace the position with the defined token so it is easier to extract the value in that position later.

Routes (master: /sitecore/system/modules/TelligentEvolution/Urls/Routes)

Routes are what tie tokens and mappings together. They are the one piece that requires some configuration. Routes determine which mapping to use based on the contextual item. A route combines a collection of items with a specific rule and action to extract data from the wildcards in the URL. A route can have multiple items and then a rule. The rule consists of a condition, which is usually checking that the item path has wildcards, and action to execute if true, which is the process of extracting the data based on the defined mapping you specify in the action. The example below defines a blog post route example. It has one target item so when that item URL is accessed, the condition checks for the presence of wildcards and extracts the values from those positions defined in the mapping. A route can have multiple items provided that every item can satisfy the same mapping.

Defining a route

Now let's focus on using the information to create a route. We are going to create a route for a blog post. We will utilize the the default route that is already defined and its mappings; we are simply going to add our item path. The goal is a resulting URL that you can display the blog post widget on.

Step 1: Review the mapping

By default there, is a BlogPostMapping already defined that utilizes the group ID, the blog application key, and the post slug or key. These are the minimum pieces of data needed to reliably retrieve a blog post when not using any of the post's IDs. Because we have three positions, our target item we will use for our URL needs to have a minimum of three wildcards in its path. With this mapping, the first wildcard will be the group ID; the second the blog's application key, and the last the post's slug or key.

Step 2: Create your item path

From this we can set up our item path. So we are going to create the following path (/sitecore/content/home/community/*/b/*/* ) which has our three wildcards. The resulting URL should be: http://mysite.com/en/community/{groupid}/b/{blogKey}/{postSlug}.aspx, given the mapping we discussed earlier.

We can clean this image up a bit by changing the display names to show you how the mapping is going to extract values:

You should be able to navigate to the URL you are trying to create and adding ?sc_mode=edit for the page editor to open. We do it this way rather than through the content manager to ensure all of the data in our wildcards exists. The content editor opens the item by ID, which means we cannot see contextual data because the wildcards are not present. In our case, we are going to http://hostname/en/community/3/b/sample_weblog/expanding-your-community.aspx?sc_mode=edit. You can see we replaced our wildcards with valid data:

Group ID: 3
Blog application key: sample_weblog
Post slug/key: expanding-your-community

On the page, add the Sitecore Debug Widget via the Telligent Community widget rendering, which is designed to show you contextual data for troubleshooting and verification:

Once added to the page, you will see it does not recognize a contextual blog post and blog, and the contextual group is Site Root, which is the default. In our case, group ID 3 is a sample group. So we can tell there is no route set up.

Furthermore, if you add another Telligent component to the page and make it show the Blog Post widget, it will not render:

Step 3: Set up your route

To bring a blog post into context, we have to configure the route. The blog post route is already defined.

Edit the BlogPostRoute and select Edit rule on the right to bring up the rule editor.
For the condition, under Telligent select target item has wildcards.
For the action, select the replace wildcards as defined in specific position mappings item.
Click specific position mappings item.
Select BlogPostMapping.
Click OK.
Click Edit above items and select the target item, which in this case is the last wildcard in our item path. Click OK.
Save the route.

After saving, return to http://hostname/en/community/3/b/sample_weblog/expanding-your-community.aspx?sc_mode=edit and refresh the page. The post should now display. If you examine the debug widget a group, blog and post are now in context. You also see the tokens extracted from the URL.

Wiki Page: Telligent Connect for Sitecore 2.0

Jenny Jarrard — Fri, 03 Feb 2012 19:14:00 GMT

Purpose

Telligent Connect for Sitecore 2.0 enables you to seamlessly integrate content and social engagement from Telligent Community into an all-encompassing audience experience from Sitecore.

Capabilities in release 2.0

This release includes the following features:

Blog features

Viewing and commenting on a blog post.
Seeing all of a blog author's posts, and seeing all the blogs he/she shares information on.
Viewing full details of any post made by a blog author.

Forum features

Replying to a forum thread.
Viewing details of specific discussions or question/answer streams.
Suggesting or verifying a forum reply as an answer.
Seeing all discussions and question/answers posted in a forum or message board.
Seeing the different forums or message boards you can participate in.
Posing questions and starting discussions.

File gallery features

Commenting on files.
Seeing all available galleries, and all available files in a file gallery.
Viewing specific files in full mode.
Viewing gallery files in slideshow mode.
Uploading media gallery files.

For more detail about features, see the Included widgets page. Also be sure to view the [[Working with contextual URLs in Sitecore|Working with contextual URLs]] article since several widgets in Telligent Community rely on specific content or contextual data in order to display their contents properly within Sitecore.

Guides included in this documentation

[[Telligent Connect for Sitecore 2.0 installation and configuration]]
[[Telligent Connect for Sitecore 2.0 release notes]]
[[Telligent Connect for Sitecore 2.0 user guide]]
[[Telligent Connect for Sitecore 2.0 widgets]]
[[Uninstalling Telligent Connect for Sitecore]]

Telligent Community

Forum Post: RE: Duplicate Emails

Wiki: Telligent Community 6

Forum Post: User Banner Bug

Wiki Page: Install Telligent Community

In this Article

Installation notes

Obtain Telligent Community

Installation components

Web server

Copy the files

Create the Web site in IIS

Set file permissions

Configure the connectionstrings.config file

Configure the search URL

Database server

Create the database

Create schema

Create community

Create login and grant permissions

Set up maintenance

Search server

Install Java

Install Tomcat

Set up Solr

Tasks server or Job Scheduler

Install the Job Scheduler

Optional installations

If you have trouble...

Wiki Page: Database configuration

In this Article

SQL Server 2008 64-bit

Database disk I/O management

Database memory

Collation

Initial database size

Database sizing formula

Autogrowth SQL settings

Recommendations

Database maintenance

Database reindex

Table statistics

Database growth

Database backups

Database tracing

Forum Post: Select Tags

Forum Post: Mobile Version

Forum Post: RE: Anti XSS implemented with $core_v2_page.GetFormValue

Forum Post: RE: Migrating Forums from Drupal to Telligent

Forum Post: RE: Change archived posts 'RSS Post Excerpt Size'

Forum Post: RE: 6.0 Installation.

Forum Post: RE: Link to a theme stylesheet for a modal popup that uses a velocity macro for the modal content source

Forum Post: RE: Link to my profile in main navigation

Forum Post: RE: Hotfix for the Telligent Community 6.0 ie7 Modal Bug?

Forum Post: RE: How to include custom jQuery plugin on a theme level

Forum Post: RE: Cannot run local install of Telligent Community in Visual Studio

Forum Post: RE: Bulk Edit/Delete Users Awaiting Approval

Forum Post: RE: TC 5.5 - Media Gallery REST API Endpoint returns 404 error

Wiki Page: Working with contextual URLs in Sitecore

In this Article

Contextual URLs defined

Types of contextual data

Contextual data currently supported

How context is retrieved in Sitecore

Mappings, tokens and routes

Defining a route

Step 1: Review the mapping

Step 2: Create your item path

Step 3: Set up your route

Wiki Page: Telligent Connect for Sitecore 2.0

In this Article

Purpose

Capabilities in release 2.0

Blog features

Forum features

File gallery features

Guides included in this documentation