Verint | Telligent Community
Verint | Telligent Community
  • Site
  • User
  • Site
  • Search
  • User
Telligent Community 10.x
  • Verint Community
  • More
Telligent Community 10.x
Legacy User Documentation Configuration File (communityserver.config) Core Attributes
  • Ask the Community
  • User Documentation
  • API Documentation
  • Manager Training
  • Developer Training
  • Tags
  • More
  • Cancel
  • New
  • Telligent Community 10.0
  • -All platform topics
    • +Achievements
    • +Activity Story Stream
    • +Authentication
    • +Blogs
    • +Business Rules
    • Calendar
    • +Chat
    • +Content tools
    • Document Preview
    • +Email
    • Featured content
    • +Forums
    • +Friends
    • Gamification
    • +Groups
    • Hashtags
    • Ideas
    • +Job Service
    • +License
    • Likes
    • +Localization
    • +Media galleries
    • +Members
    • Mentions
    • +Mobile
    • +Moderation, spam and abuse
    • +Notifications & messages
    • Our quality assurance testing strategy
    • +Page Editing
    • +Permissions
    • +Profile & sign-in
    • Quick Post
    • Ratings
    • Responsive design
    • +Roles
    • Rule Automation
    • +Scores
    • +Search
    • +Security
    • +SEO
    • +Site admin
    • -Site configuration
      • Basic site configuration
      • -Configuration File (communityserver.config) Core Attributes
        • How to use override files
      • Configure Telligent Community to use a proxy server
      • Enable secure links to RSS content
      • Internet Information Services (IIS) Configuration
      • SiteURLs
      • Starter Kit community setup process
      • Syndication options
      • Windows Server configuration check-list
    • Social basics guide
    • Social Twitter feed
    • +Status messages
    • Tags
    • +Telligent Community Troubleshooting Guide
    • Terminology Guide
    • +Themes
    • Tour Tips
    • +Tuning & performance
    • +User accounts
    • +User reputation score
    • Video Transcoding
    • +Widgets
    • +Wikis
  • Customization
  • Development
  • Getting started
  • System Requirements
  • +How Do I Install Telligent Community
  • +Upgrade Telligent Community
  • Release Notes

Configuration File (communityserver.config) Core Attributes

Table of Contents

  • Override Files
    • Add new attribute
    • Edit existing attribute
  • Core attributes
    • defaultTheme
    • defaultGroupTheme
    • defaultLanguage
    • requestEncoding
    • responseEncoding
    • disableEmail
    • disableIndexing
    • disableThreading
    • smtpServerConnectionLimit
    • enableLatestVersionCheck
    • backwardsCompatiblePasswords
    • ssl
    • wwwStatus
    • overrideWebPort
      • overrideBaseUrl
    • xFrameOptions
    • unlockUserAfterMinutes
    • enableUsersOnline (System.Boolean)
    • announcementRssUrl (System.String)
    • ??siteFilesQuota (System.Int64)
    • ??siteFilesMaxSize (System.Int32)
    • ??siteFileStorageExtensions (System.String)
    • ??enableSiteFileStorage (System.Boolean)
    • enableLatestVersionCheck(System.Boolean)
    • applicationOverride(System.String)
    • wwwStatus (CommunityServer.Components.WWWStatus)
    • ssl (CommunityServer.ComponentsSSLSettings)
    • ??proxyHost (System.String)
    • ??proxyPort (System.Int32)
    • ??proxyUsername (System.String)
    • ??proxyPassword (System.String)
    • ??proxyBypassOnLocal (System.Boolean)
    • lookupUsersByEmail (System.Boolean)
    • unlockUserAfterMinutes (System.Int32)
    • defaultRoles (System.String[])
    • ??authorizationCookieName (System.String)

The Core node in communityserver.config contains settings which affect the core of Telligent Community Server. If you need to make a change to a value in the communityserver.config file, you should do so through an external communityserver_override.config file, which we provide an example of here.

Override Files

Override files allow you to make changes to core configuration files through a separate file. This ensures that your changes are not lost when you apply an update to Community Server which includes a new communityserver.config file.

The following are example overrides for changing core attributes through a communityserver_override.config file.

Add new attribute

If the attribute does not exist in communityserver.config, you can use the following override to add the attribute.

<Override xpath="/CommunityServer/Core" 
mode="new" name="overrideBaseUrl"
value="https://your-community-url.com">
</override>

Edit existing attribute

If the attribute you want to change already exists on the Core node of communityserver.config, the following override shows you how to change the default language to French (fr-FR):

<Override xpath="/CommunityServer/Core"
mode="change"
name="defaultLanguage"
value="fr-FR" />

 Core attributes

You can specify the following list of attributes directly on the CommunityServer\Core node in the communityserver.config file. You can specify other attributes, but they will be ignored.

defaultTheme 

Default: It should be 3fc3f82483d14ec485ef92e206116d49 (Social)

Specifies the default theme. This setting is only used if a Site Theme has NOT been saved using the Theme Configuration page.

defaultGroupTheme 

Default: It should be 3fc3f82483d14ec485ef92e206116d49 (Social)

Specifies the default theme used by groups. This setting is only used if a default Group Theme has NOT been set through the Group Administration Theme Options page.

defaultLanguage

Default: en-US

Specifies the default language used throughout Community Server. It will be used as the language for anonymous users and as the default language for any newly registered users. If you have installed multiple language packs, registered users can change the language they see on their site by changing the language setting in their profile.

requestEncoding

Default: web.config globalization settings

The precedence of values is as follows: Pulls value from the Core element of the communityserver.config file. When not present, gets value from Request.ContentEncoding. If HttpContext is null, defaults to Encoding.UTF8.

responseEncoding 

Default: default = web.config globalization settings

The precedence of values is as follows:Pulls value from the Core element of the communityserver.config file. When not present, gets value from Response.ContentEncoding. If HttpContext is null, defaults to Encoding.UTF8.

disableEmail

Default: False

Setting this to True will disable the Email processing on this server. Works together with the Control Panel setting. Values from both settings are used to enable email. This is primarily used on clustered servers to allow only certain machines to process email. Having all clustered web servers attempting to process the email queue could result in duplicate emails being sent on high-traffic websites. This setting allows you to control which servers queue and send the emails in a load-balanced environment.

This setting overrides the SiteSettings option for sending emails, if the sitesettings has emails set to True. Otherwise, nothing changes and no web server sends email.

disableIndexing

Default: False

Setting this to True will disable .NET indexing of cached data (language files, site settings, forums information, etc). Setting this to True will also degrade the system and the forum's performance.

disableThreading

Default: False

Setting this to True will disable .NET background threading of system processing (emails, stats, etc). Setting this to True will also degrade the system's and the forum performance.

smtpServerConnectionLimit

Default: -1

Limits or throttles the number of concurrent connections that can be sent to an SMTP server when sending email. Some ISPs limit the number of concurrent connections from a single account. If there is a large email queue, Telligent can quickly exhaust the number of connections to the ISP's SMTP server. In other situations, you may not have this restriction and can just leave it at the default, which will send the email as fast as it can and not worry about the number of connections used by a single account.

enableLatestVersionCheck

Default: true

Option to control whether the admin page attempts to contact the forums site to check for the latest version. Turn this option to false to turn this capability off.

backwardsCompatiblePasswords

Default: false

Wheher CS should attempt to upgrade an account after a failed login attempt. MemberRoles stored password hashes slightly differently from Forums 2.0. If backwardsCompatiblePasswords is set to true, after a failed login attempt, CS will attempt to upgrade the account. If you are working on a clean install of CS, you should leave this at false.

ssl

Default: Ignore

Three options:

  1. Ignore - CS will use SSL or non-SSL.
  2. Password - CS will require (and redirect) to any page which has the user's password.
  3. All - CS will require all pages (and redirects) use SSL.

wwwStatus

Default: Remove

Three supported values: Require, Remove, or Ignore

Require validates the current Url uses www. (i.e., http://www.Telligent.Evolution.org). Remove validates that the current Url does not contain www. Ignore does not validate the request.

overrideWebPort

This is for overriding the port used if Community Server is used behind a load balancer and the web servers are set to ports that the eventual destination does not have access to. This does not directly affect the value in SiteUrl (Configuration class).

overrideBaseUrl

This can be used for overriding the base URL used to create fully qualified URLs for accessing this site. If not specified, the requesting URL will be used as the base.

xFrameOptions

Default: SAMEORIGIN

This sets the X-FRAME-OPTIONS response header. If it is empty, then the X-FRAME-OPTIONS header will not be added to the response. Possible values are DENY or SAMEORIGIN. The header determines if the site can be viewed within an iFrame.

unlockUserAfterMinutes

Default: 5

This sets how many minutes a user should remain locked out of logging in once a lock has been put on the user by aspnet membership. Use -1 to never automatically unlock an account. See web.config membership section's maxInvalidPasswordAttempts and passwordAttemptWindow to set how many failed attempts the user can make at logging in and in how short of a time, respectively.

enableUsersOnline (System.Boolean)

Default: true

announcementRssUrl (System.String)

Default: http://telligent.com/r.ashx?43

Determines the URL of the RSS feed the Announcements box in the Control Panel pulls announcements from.

??siteFilesQuota (System.Int64)

Default 0

Specifies the maximum size (in MB) of all uploaded site files. If this value is set to 0, then there is no limit. If a Site File is uploaded that pushes the total storage space used by Site Files over this limit, then a CSException of type CSExceptionType.SiteFileQuotaExceeded is returned.

??siteFilesMaxSize (System.Int32)

Default: 4096

Specifies the maximum size (in MB) of a single uploaded site file. If this value is set to 0, then there is no limit. If a site file is uploaded that goes over this limit, a CSException of type CSExceptionType.SiteFileQuotaExceeded is returned.

??siteFileStorageExtensions (System.String)

 Default: "123,aac,ai,aiff,art,asf,asx,avi,bmp,csd,db,db,dmg,doc,docx,drw,eml,flac,flv,gif,gz,ics,jpeg,jpg,log,m4a,m4p,m4v,mdb,mdbx,mid,midi,mmv,mov,mp3,mp4,mpg,msg,ogg,pdf,png,pps,ppt,pptx,ps,psd,qt,ram,rar,rm,rtf,sit,sitx,sql,swf,tif,tiff,txt,vcf,vcs,wav,wma,wmv,wpd,wps,xls,xlsx,xml,zip"

Specifies a comma-separated list of file extensions which can uploaded to site files. If users have the Site - Bypass Validation permission, then they may upload any file. If a file that does not have a permitted extension is uploaded, then a CSException of type CSExceptionType.FileTypeNotValid is returned.

??enableSiteFileStorage (System.Boolean)

Default: true

Specifies whether the site files feature is enabled.

enableLatestVersionCheck(System.Boolean)

Default: true

If true, the site will contact Telligent to check if a new version is available.

applicationOverride(System.String)

Default: null

Explicitly sets the site Url. If left as null, it will be determined from automatically.

wwwStatus (CommunityServer.Components.WWWStatus)

Default: Remove

 Specifies what to do with any www. in your URLs throughout Community Server. Valid options are:

  • Remove (default) - Ensures all requests made to Community Server DO NOT have the www prefix.
  • Require - Ensures that all requests to Community Server DO have the www prefix.
  • Ignore (not recommended) - Community Server will ignore the inclusion or absence of the www. prefix in a URL.

ssl (CommunityServer.ComponentsSSLSettings)

Default: Ignore

Specifies how SSL should be used throughout Community Server. Valid options are:

  • Ignore (default) - If a page is requested over SSL, Community Server will respond over SSL. If the page isn't requested over SSL, Community Server will not respond over SSL.
  • All - All responses for requests made to Community Server will be made over SSL.
  • Password - All requests made to pages involving passwords are made over SSL. This includes pages with the following controls on:
    • Change Password
    • Create User
    • Login 
    • OpenID Login Form
    • Any control calling CSControlUtility.Instance().EnsureSecureConnection(System.Web.HttpContext context)
    • Any widget calling $core_v2_page.EnsureSecureConnection("%{IsAuthenticatingUser="true"}")

??proxyHost (System.String)

Default: String.Empty

Specifies the hostname for the proxy server to use when making outbound requests. Situations in which outbound requests may be made include:

  • Blog mirroring
  • Trackbacks
  • Pingbacks
  • Remote attachments

??proxyPort (System.Int32)

Default: 80

Specifies the port number for the proxy server to use when making outbound requests. Situations in which outbound requests may be made include:

  • Blog mirroring
  • Trackbacks
  • Pingbacks
  • Remote attachments

??proxyUsername (System.String)

Default: String.Empty

Specifies the username to use when connecting to the proxy server for outbound requests. Situations in which outbound requests may be made include:

  • Blog mirroring
  • Trackbacks
  • Pingbacks
  • Remote attachments

??proxyPassword (System.String)

Default: String.Empty

Specifies the password to use when connecting to the proxy server for outbound requests. Situations in which outbound requests may be made include:

  • Blog mirroring
  • Trackbacks
  • Pingbacks
  • Remote attachments

??proxyBypassOnLocal (System.Boolean)

Default: true

Specifies whether the proxy server should be bypassed when making outbound requests to the local server.  Situations in which outbound requests may be made include:

  • Blog mirroring
  • Trackbacks
  • Pingbacks
  • Remote attachments

lookupUsersByEmail (System.Boolean)

Default: false for Social.

Allow users to be searched and found by their email address.

unlockUserAfterMinutes (System.Int32)

Default: 5.

This sets how many minutes a user should remain locked out of logging in once a lock has been put on the user by aspnet membership.
Use -1 to never automatically unlock an account.

See web.config membership section's maxInvalidPasswordAttempts and passwordAttemptWindow to set how many failed attempts the user
can make at logging in and in how short of a time respectively.

defaultRoles (System.String[])

Default: "Everyone;Registered Users"

Specifies the roles that should be added to new users when they are created. Each role should be separated by a semicolon.

??authorizationCookieName (System.String)

Default: "AuthorizationCookie"

Specify the cookie name used for authorization.

  • configuration
  • Share
  • History
  • More
  • Cancel
Related
Recommended
  • Telligent
  • Professional Services
  • Submit a Support Ticket
  • Become a Partner
  • Request a Demo
  • Contact Us

About
Privacy Policy
Terms of use
Copyright 2021 Verint, Inc.
Powered by Verint Community