Community Server 2008 includes a number of changes in the properties of form classes (derived from PreTemplatedWrappedFormBase and WrappedSubFormBase). The following list includes properties that were removed or renamed for Community Server 2008.
Community Server 2008 updated the spam rules to support dynamic configuration options so the dynamic configuration code is consistent across new features. For example, the same way you code for dynamic options in a content fragment (widget) is the same as in spam rules. These updates allow you to easily configure the spam rule dynamic options.
The siteurls.config file contains the data used for URL rewriting.
When you upgrade a site and have made changes to the siteurls.config file or a similar configuration file, you often need to merge your changes with the updated copy. To do this, you can create a SiteUrls_override.config file that sits in the same directory as your SiteUrls.config, and merge it with the SiteUrls.config file.
File viewers are .net classes that implement the CommunityServer.Components.IFileViewer interface and support viewing and resizing images, viewing uploaded and remote video files, viewing video from online video services, and playing uploaded and remote audio clips.
Community Server registers all file viewers in the <FileViewers> region of the communityserver.config file. Each file viewer requires an <add /> node, which supports three attributes: type, extensions, and urlPattern.
You can use the new configuration override functionality for a single-user blog.
By default, Community Server truncates (as well as remove the HTML) any post from the aggregate blog home page if it is over 250 characters.
Community Server uses default templates to send email notifications to community users about ongoing activity in Community Server, such as friendship requests and approvals, new accounts, password requests and changes, and so on.
The email templates are contained in the emails.xml file which is located in [Community Server root folder] / Languages /en-US /emails.
Community Server uses email text tokens as placeholders that will vary from one email to the next. A common email text token is username, which obviously will be different for every user that is referenced by the username value. Email text tokens are always enclosed in square brackets.