What's New in CSK 1.1

• Bug Fixes
• Modified Functionality
• New Functionality
• New Feature Details
  • Private Messages
  • Multi-Level Section Menu
  • Custom Redirects
  • Integrated FreeTextBox
• Known bugs

Bug Fixes

• Discussion Reply Subject Fix: Allows user supplied subject in Discussion reply posts to be correctly saved to the database. Previously the parent item's subject was always used regardless of the user supplied value.
   
• Links in content item body text will now correctly open in a new window. The CSK will also recognize links even if they contain additional HTML attributes other than just HREF.
   
• Comment Email Notification Mod: email notifications for new comments to an item will contain a URL for the comment's parent item instead of directly linking to the comment itself.
   
• Database Ownership fix: Due to SQL Syntax for calls to stored procs and functions from within other stored procs and functions, the owner of all procs and functions must be named in the call. Since the DBO is the only consistent user in every SQL database, all objects should belong to the DBO. The CSK installer sets up the database so that DBO owns all objects, but the actual scripts executed against the database do not specify the owner explicitly. If you use DTS as a different user, the objects would belong to the user that performed the transfer in the target database. This fix alters the stored proc and function definitions so that DBO is explicitly named as their owner. This should prevent problems encountered when using DTS to transfer CSK databases from one server to another.
   
• Discussion reply notification emails now contain a valid URL. This URL will link to the parent thread item of the reply. Previously the URL sent was always invalid. 
   
• Web Boxes with content from Disabled Sections: Disabling a section with content will no longer break a web box that would normally have shown content from that section.
   
• Hyperlinks in Event Section now display correctly.
   
• Thumbnails in photogallery now align correctly. Previously you may have 3 items on one row, then 4 on the next, then 3 on the last. The same number of items will now appear on each row in the gallery.
   
• Date Posted sort order in content lists now works correctly.
   
• Bread Crumb component now uses the Menu Title instead of the Section Name as defined in the Edit/Add section admin tool..
   
• Images uploaded to a photogallery from non IE browsers will now correctly display their thumbnails. Previously, uploading jpg or jpeg images from non-IE browsers would cause the thumbnails to not display for any browser.
   
• The unused Community_AdminAddDefaultSection stored procedure was removed.
   
• Output cache for Web Boxes has been removed. This was causing all web boxes on a page to show identical content. A new output cache parameter could be used, however it appears to cause unusual behavior with the random display modes (e.g. - Randomly Display X Web Boxes). 
     
• Bottom section menu skin fixed in default theme so that any theme that fails over to the default theme for it's bottom section menu will no longer fail to load. 
   
• Email link in profile page has been fixed to correctly attempt to open the default mail program.
   
• Download count in Download content pages no longer shows view count, it shows the download count. 
   
• Database connections are now properly closed in all data operations preventing connection leaks.  This was a minor problem with some of the data readers not being closed, thus holding their connection objects open as well.
   
• Comment list Separators fixed.
   
• CSK stored procedures had performance issues that caused page loads times to go up drastically when there is more than 1000 content items. This has been fixed.
   
• Search now shows items in sections even if security isn't set to everyone or authenticated users and handles properly the access rights.
   
• Search does not break with content in disabled sections.
   
• Users with edit access to a section can no longer move content items to other sections where they do not have rights. 

Modified Functionality

• Numbered Image Validation. Adds validation to the admin tools that will prevent uploading an image where the file name contains only numbers. This prevents name collisions with PhotoGallery images which are automatically given a numeric file name.
   
• Uniform Transformations: Changes the behavior of the CSK's transformation engine so that content will be transformed regardless of the HTML Editor's settings in the Section Admin tool. The original CSK could not correctly apply the same transformation to sections where HTML Editing was disabled.
   
• Color Blind Friendly Images for the Content "read" and "not read" images, and for the Discussion board. New images combine the color scheme and icons from the original CSK with additional graphics that will indicate to the color blind person the state of the items.
   
• Parent Sections Mod: All section types in the CSK can now be parents to other sections. The original CSK only allows the "Parent Section" section type to contain child sections.
  
  If you wish to eliminate one or more types of section (PageTypes) from being able to contain child sections, simply modify the Community_PageTypes table and set the pagetype_isParent column value to 0 for that type of section. When creating new PageTypes in the CSK, set this column to 1 if you want the new section type to be a potential parent to other sections.
   
• The built-in HTML Editor has been replaced with a new component based on the FreeTextBox source code. The FreeTextBox source code has been directly integrated into the CSK namespaces. The component replaces the HtmlTextBox class which defined the CSK's original editor. The FreeTextBox integrations is described in more detail in the section titled: Integrated FreeTextBox below.
   
• Move content option has been restored to the content pages (It does not appear in the content lists screens).  
   
• Login page now provides an option to persist the login between sessions so users do not have to login each time they visit the site. Warning! If this feature is used, the last login time for the user will not be updated unless they manually logout and back in again. See the known bugs section for more information.
   
• Vote Polls now support several CSS classes including: .VoteItemClass .VoteQuestionClass .VoteButtonClass .VoteTableClass .VoteResultClass
   
• When a section is set to inherit web boxes or web service boxes, it will now inherit the display mode also (e.g. - Display All Selected Web Boxes vs. Randomly Display X Web Boxes).
  
• Web service box refreshing behavior has been re-designed. The new behavior includes the following changes:
   
  • A failure to fetch data from the RSS feed or remote CSK section will no longer reset the last refreshed date in the database.
     
  • A failure to fetch data from the remote server will cause the CSK to re-try the attempt periodically. The frequency of re-trys is now shorter than the configured refresh rate. For every hour configured for the standard refresh rate, the CSK will now wait 15 minutes before it retries a failed fetch. For example, if refresh rate is every 1 hour, it will now re-try a failed fetch every 15 minutes (15 * 1). If the refresh rate is every 8 hours, it will re-try a failure every 2 hours (15 * 8) . If the refresh is successful, the next refresh will occur according to the refresh rate normally.
     
  • Failed CSK web service feed refreshes will enter a slightly different event in the activity log from RSS feed or general exceptions.
     
  • Web services that failed to refresh will not display an empty web service box on the page.
     
  • ASP.NET recycles and application restarts will now refresh the service on the next user request regardless of the refresh rate and last recorded refresh date.
     
  • The values for last refreshed date are now supplied from the web server in UTC format. 
     
• DatePicker control now supports two new properties that allow you to control the valid time-rage for the control. This allows you to support dates in the far future or far past if the default date range is too small. The new properties are: YearsBefore and YearsAfter. Events_AddEvent.ascx and Events_EditEvent.ascx in the default theme demonstrate the use of these properties.
   

New Functionality

• Fail-Over Theme Mod: Allows you to specify a theme to use in the event the primary theme does not contain a skin file for a particular item. If the fail-over theme also does not have the skin file, the default theme's skin file will be used.
   
  The primary use for this mod is to allow you to create a second theme very similar to another theme without requiring that both versions contain duplicates of the same control. As an Example: image you have a theme called "Toast" that has a side-bar for showing web boxes. You want to create a similar theme that does not have the side-bar for use on pages where you want to maximize the screen area for the content. To accomplish this, you only need to create the second theme and make a Page Skin for it. You can use the fail-over theme feature so that all of the other controls will use the "Toast" theme's other skin components.  
   
• Multi-Level Section Menu: A new control to replace the standard Section Menu in page skins. Configurable to show child sections for the selected section only, or for all child sections. You can also restrict the number of levels that will show, and control highlighting behavior for the selected section. More information on this feature can be found in the section titled: Multi-Level Section Menu .
   
• Private Message Mod: Provides a mechanism for users to send emails to other users via a web form. Includes controls that can be placed in content items and content lists to provide a quick image link to the send PM form. Provides a link in the Show Profile page to send a user private messages, and also adds a new option in the User Registration (and admin) forms to enable or disable private messages for the user. More information can be found in the section titled: Private Messages .
   
• Custom Redirects Mod: A new admin tool that allows you to specify URLs that should be redirected to other locations. You can control if the redirect should affect requests to a particular path, or only a specific page. More information can be found in the section titled: Custom Redirects .
   
• Server Time Zone Offset Mod: Allows you to specify, in Web.config, that the server should use a different time zone than the one configured in the server's operating system settings. This is good if your server physically resides in a different time zone from your users or your organization. If no time zone offset is configured in web.config, then it will use the server's local time zone normally. The web.config file included in this distribution contains a commented out example of how and where to configure the Time Zone Offsets. The GmtTimeOffset should be relative to Greenwich Mean Time (GMT).

New Feature Details

Private Messages

This mod adds private email message functionality to the CSK. Private Messages (or PMs) allow users of the CSK to send emails to another CSK user's private email addresses without disclosing the private email addresses to either user.

Features:

• New option in user profile registration and admin edit user tool to enable or disable private messages for the user.
   
• New option in display profile that will show a link to the send private message page if that user's profile has private messages enabled.
     
• New Message in Admin Messages tool called Private Message that provides a template for the email message. This template has custom placeholder options described later.
     
• New Send Private Message named page. This form provides an interface by which any registered user can send private messages to any other registered user. Both sender and recipient must have enabled private messages. Includes an *option* where the sender can send their own private email address to the recipient for direct replies. Also includes message preview, validation, and error logging (email send failures only). 
   
• Follows the existing design patterns for CSK development.
   
• Send Private Message form can be directly linked from any path in the CSK. Query string parameters for recipient name and subject are optional, but supported. If no recipient is supplied in the URL, the form's drop-down list can be used to select any available recipient.

• Includes custom web controls for adding an image link in content lists and content items. This is described in more detail below.

The core idea of this mod is to allow users to send email to the private email address of other users via a web form. This will prevent either party from knowing the other user's real private email address, thus protecting their privacy.

To accomplish this, this mod changes the User Registration form, which is used in the Admin Edit user tool, the New user Registration, and the Edit Profile features of the CSK. A new option for enabling private messages is added to this form. The value for this option is stored in the Community_Users table.

The Show profile pages will now include an indication of the user's private message option, and if the user enabled private messages, a "Send Private Message" link will appear on the bottom of the page.

There are three new web controls that can be dropped into various skin files. These web controls place an image hyperlink in the page that, when clicked, will take the user to the send private message page directly. In this case, the private message form will be pre-populated with the recipient's user name and the subject will reflect the content item the user clicked the link from. Though these controls are included in this distribution, none of the pre-defined themes use them. 
 
How to use the inline image controls:  

• In content skin files such as Articles_Article.ascx, insert this tag beside the <community:author> tag:
   
  <community:SendPmImage runat="server" ID="SendPmImage1" />
   
• In content list files such as Articles_ArticleSection.ascx, insert this tag beside the <community:ItemAuthor> tag in the item template.
   
  <community:ItemSendPmImage runat="server" ID="SendPmImage1" />
   
• For discussion sections, you can use the ItemSendPmImage control near the ItemAuthor control same as for any content list page. But a special control is included in this distribution just for adding an image link to the "Last Post By" person's name. Near the <community:ItemDiscussLastCommentUsername> tag, place this control:
   
  <community:ItemDiscussLastCommentSendPmImage runat="server" ID="SendPmImage1" /> 

The Send Private Message form itself is a rather simple user control. It validates that the sender and recipient both enabled private messages. It also validates that the sender is logged into the site, and that the recipient is a valid user. The recipient, and sometimes the subject, can be pre-populated from query string parameters (recipient=xxx&subject=yyyy). The recipient names appear in a drop-down list of users. If the form is invoked via a direct link without the recipient= query string parameter, the user will have to manually choose a valid recipient. This list only shows the users that have private messages enabled, and the list is cached until a new user registers, or an existing user's profile is updated.

The send Private Message form performs the same validation during postbacks as it does during initial load to protect against form-post hacks.

The initial form has a clear form and preview message button. Clear form does the obvious. Preview message will show the user the exact message that will be sent (merging the user supplied subject and body with the Private Message email template). The preview mode has buttons that will either send the message or take the user back to edit mode. When send message is sent, the user will be shown a success message, or a failure message. Failures will place an error in the Admin Activity log.

The send private message form also provides the user an option to send their own private email address with the mail. This will disclose their private address to the recipient, but does allow the recipient to reply directly from their mail client rather than using the site's private message form. When this option is enabled, the message will use the sender's private mail as the email's From: line. Otherwise, the From: line will contain notify@PrimaryDomain where PrimaryDomain is the PrimaryDomain specified in ISPAdmin for this community.

The Private Message Email Template:

The email sent for a private message combines the contents of the Private Message email template, with the Message body typed by the sender. These templates are available in the Edit Messages Admin tool. The default template included with this mod makes use of all available placeholders as an example. The idea here is that the admin can make sure that all private messages include links to disable the PM feature if the recipient no longer wants to receive them, and other static information.

The template supports the same placeholders as any other Message, plus these unique ones:

• <SenderUserName> = the user name of the sender.
• <RecipientFullName> = the full name of the recipient.
• <RecipientUsername> = the user name of the recipient.
• <EditProfileLink> = the URL for the Edit Profile page.
• <ContentSubject> = the subject supplied by the user in the Send PM form.
• <ReplyLink> = the URL that the recipient can use to reply to the message.
• <BodyText> = The body text typed by the sender.
• <CommunityName> = The name of the community as specified in ISPAdmin.

Multi-Level Section Menu Component

The Multi-Level Section Menu is a modification of the built-in SectionMenu component of the CSK. The purpose of this new component is to supply a navigation control that provides the user with a tree style menu showing parent and child sections in a visually intuitive way. The built-in component only shows the top-level sections.

In this release, the Arc theme has been modified to use the new Multi-Level Section Menu components as an example.

Features:

• Multi-level tree navigation of sections and child sections.
   
• Indication of which section the user is currently visiting (optional)
   
• Ability to expand only the current branch, or the entire menu
   
• Ability to control the depth of the displayed branches.
   
• Output is pure HTML. No client side scripting.

The Mult-iLevel Section Menu only works well in vertical navigation menus where the menu items appear in a side-bar on the page (the Default Lunar theme and Arc themes use this style of menu). This control isn't easily adaptable to a horizontal menu layout where menu items appear side by side, but careful use of the repeater layout may be able to achieve a workable effect. 

When allowing deep navigation with this control it may become necessary to limit the number of levels that can be expanded (support for this is provided). Each nested level of section displayed will indent 10 pixels to the right. When you have a large number of sections nested under each other, the menu could begin to take up too much horizontal space for your site's side bar to contain without disrupting your overall layout. Pay particular attention to the design of your page skin's to ensure that the deepest levels of your menu don't distort the page's visual appearance. About 3 or 4 levels is the practical limit even when using brief or abbreviated section titles; however, it is widely considered poor design for a site to have navigation structures deeper than 3 or 4 levels anyway.

Properties: 

The Multi-Level Section Menu component supports 3 new properties that you can specify when you place the tag into a skin file. The SubSectionMenu component is supplied these same properties automatically.

• ExpandLevels: This determines how many levels deep the menu will show. If not specified, The default is ExpandLevels="0", which will show ALL sections and sub-section levels in the menu.
   
• ExpandAll: this determines the behavior of the menu's displaying of sub-menu items. If not specified, the default is ExpandAll= "false".If set true, the menu will expand all branches no matter which branch is active. If false, it only expands the selected branch. How many levels deep the expansion goes is controlled by the ExpandLevels property. If setting ExpandAll to true, it is recommended that you limit the ExpandLevels to 1 or 2.
   
• ShowSelection: This determines if an alternate style will be applied to the menu or sub-menu item that matches the current page the user is viewing. The default for this is true. If true, the style name of the Multi-Level Section Menu control plus "_SelectedMenuItem" will be set as the CSS classname of the hyperlink element for the menu item that matches the page the user is viewing. The default style of the Multi-Level Section Menu element  is "SectionMenu" so the name of the style that will be applied to the selected menu item is "SectionMenu_SelectedMenuItem".

Custom Redirects Admin Tool

In this release, there is a new admin tool in the admin section where you can define URL redirections. Each redirection includes a source URL and destination URL. Any browser request for the source URL will be redirected (using Response .Redirect()) to the destination URL. You can redirect requests for specific pages, or requests for any resource in a specific CSK section.

This mod is designed for situations where a CSK section or page was moved or deleted, but you still want links from search engines or other sites point to a valid URL rather than the 404 fun-house.

Note: If you are redirecting a section, then requests for resources in that section will be redirected to the specified destination URL or path. However, sub-sections under the redirected section will NOT be redirected. If you are moving a parent section, you will need separate redirect entries for the all of its child sections.

How the Mod works:

When a request is made to a CSK application from a browser, the CommunitiesModule class is responsible for parsing the requested URL and determining what resource is being requested. This mod plugs into this class and adds a check to see if the requested URL matches one of the redirect entries in the database. If so, it will redirect the browser to the new URL.

There are two kinds of redirects that this mod deals with. Requests made for a specific page and requests made to a section. If you defined a redirect for a specific page, then your destination URL must also be a specific URL. But if your source URL is a section redirection, you have two choices:

1. Redirect to a specific URL. This means that any request made to a resource in the source section's path will be directed to this exact page.
    
2. Redirect to a section path. This means that any request made to a resource in the source section's path will be redirected to the same filename in the new path.

The admin utility has pretty good validation to prevent invalid redirects from being entered, but it isn't perfect. The things to keep in mind when defining a redirect in the admin tools are:

• Source URLs must be resources in the CSK site.
   
• Source URLs are ALWAYS relative to the application root (leave off the "http://" part of the URL)
   
• Source URLs that are redirecting a section must NOT specify a page name and must end with the "/" character.
     
• Source URLs that are redirecting a specific page must specify the exact page name at the end of the URL and should not end with a "/" character.
   
• Destination URLs follow the same formatting rules as source URLs with one important distinction. They can specify an external resource on another site. This works with both Specific page destinations and path (section) destinations. In other words, you can redirect a request for a page or section on your CSK site to another web site completely.

Example Redirections:

You move a specific content page from one section to another:

Source: myParent/mySection/123.aspx
Source Type: Exact Url
Destination: myNewParent/myNewSection/123.aspx
Dest Type: Exact Url

You renamed a section in the Edit section admin tool:

Source: myParent/mySection/
Source Type: Section Url
Destination: myNewParent/myNewSection/
Dest Type: Path Url

You deleted a section and want to point requests back to the CSK's home

Source: myParent/mySection/
Source Type: Section Url
Destination: default.aspx
Dest Type: Exact Url

You deleted a section and want to point requests to a similar area of another site.

Source: myParent/mySection/
Source Type: Section Url
Destination: http://www.newsite.com/similarSection/default.html
Dest Type: Exact Url

You moved a section to another site that has the exact same page names

Source: myParent/mySection/
Source Type: Section Url
Destination: http://www.newsite.com/newSection/
Dest Type: Path Url

Integrated FreeTextBox

This release replaces the CSK's graphical HTML editor with a new version based on FreeTextBox 1.6.2. The FreeTextBox source code has been fully integrated into the CSK using the standard CSK namespace and class names. The means there are no external DLLs to include and no need to configure references or compile two sets of source code.

Additionally, the FreeTextBox source has been altered to support the CSK's standard HTML Editor functionality and security including: Support for the CSK Section's HTML Editor Modes (full, limited, none); Supporting the Insert Emote Icon and paste code block functionality; and supporting the CSK's text transformations.

The FreeTextBox source has been renamed to the same as the CSK's original Editor (HtmlTextBox) and supports all of the same properties that the original editor did. The new component does support all of the properties of the FreeTextBox, and these can be included in skin files as properties of the <community:HtmlTextBox> component to control the FreeTextBox's appearance and functionality. In addition, it also supports all of the properties of the original HTML Editor. 

The FreeTextBox also includes VisualStudio.NET designers so you can configure many of the settings for the freetext box in VS.NET's graphical designer via the properties window. This functionality is supported in the CSK version, and any skin with an HtmlTextBox control supports this designer automatically.

The Editor.css file

One interesting challenge with the HTML editor is that text entered into the editor should appear just like it would when the content is displayed in the CSK. However, unless you specify exact font name, style, and size in the editor, the text you enter into the Editor will not have explicit formatting. The CSK would apply a standard CSS style to that content when displaying the text, but the entered text would not reflect this.

So that the editor's default formatting matches what the CSK's theme would apply, this distribution adds support for a special CSS file to be used with the new Editor.

In the default theme's style folder at: /Communities/Common/Themes/Default/Styles/Editor/ you will find a new file called Editor.css. This file contains the default text style (in the body element) and the default code block style (in the pre element). The styles in this file are applied to the editor so that text will have the theme's standard text formatting already applied when you are viewing text in the editor.

Different themes though, may use different styles for standard text. To support this, you can make a new Editor.css file for any theme. Simply create the /Styles/Editor/ folder in your theme's folder, and add your own Editor.css file to it. When creating an Editor.css file for a theme, you should probably base the styles off of that theme's Article_FullDescription class, and the pre style in the theme's regular CSS file. Note that only one style can be applied to the editor in any one theme, so avoid radically different font formatting in different types of content pages in your themes.

When the Editor loads up, it first checks to see if there is an Editor.css file for the section's current theme. If there is not one, it will apply the styles from the default theme's Editor.css.

Note: Admin tools do not have a section theme, and will always load the default theme's Editor.css file.

The HtmlTextBox control in many skins supplies a CssClass property. Though supported by the new editor, this CssClass will generally not do anything and can't be used to control the default formatting of text entered into the editor. The property is supported for backwards compatibility with CSK 1.0 themes only.

Properties of the new HtmlTextBox control:

With the exceptions noted below, the CSK's HtmlTextBox control will support all of the same properties of the original CSK's editor, plus the new properties supported by the FreeTextBox control. The FreeTextBox's documentation is included in this distribution for reference, but be aware that in the CSK, the FreeTextBox has been renamed to HtmlTextBox (for compatibility with the CSK's original Editor code) and the namespaces also differ.

• Image Gallery, General Info : The image gallery is not, by default, specific to any one community. It is a shared folder under /Communities/Common/Images/HtmlTextBoxUserImages/. Any images in this location will automatically be visible in the Image Gallery (sub-folders are supported) for all communities. If you wish to allow users to upload new images to the gallery, you will have to grant the ASP.NET Machine account write access to this folder through windows explorer. Otherwise the Image Gallery will only allow users to select existing images. All communities will share this same folder unless you specify a new path via the ImageGalleryPath property.
   
• The ImageGalleryPath property : You can specify this property (in each skin file where the HtmlTextBox control is declared). This property controls which folder the editor will use for the image gallery. You can set this property (use relative URLs) to specify a new folder for the Editor to use. The code was modified so that the CSK will automatically map the relative path to your CSK's root path. Using this property, you can manually separate different communities to use different image gallery folders.
   
  Example:
  <community:HtmlTextBox ImageGalleryPath= "Communities/Community1/Images/HtmlTextBoxUserImages">
     
• ToolbarLayout and AutoConfigure: By default, the HtmlTextBox will use a customized toolbar layout that enabled most of the features of the FreeTextBox editor (plus the new CSK specific features for Emote Icon and Paste Code Block). You can override the default toolbar layout by using the AutoConfigure property (set to "EnableAll", "Minimal", "Default", or "Alternate"). Specifying this setting will override the standard toolbar layout. You can also supply a custom list of items to define the toolbar via the ToolbarLayout property. The CSK's version of the toolbar supports all of the standard FreeTextBox toolbar items, plus the new "EmoteiconPicker" and "InsertCodeBlock" options.
   
  Refer to the FreeTextBox documentation for more info on these properties.
   
• HelperFilesPath: By default, the helper files (the aspx files that control the image gallery, color picker, and other pop-up windows) is set to /Engine/Framework/HtmlTextBox/ If you specify your own value for this property, the modified code will automatically map the path to the CSK's root. Use a relative path without leading "/" character.
   
• Columns and Rows properties: The CSK's original editor supported these properties for controlling how large the textbox will appear in downlevel browsers. In the new editor these properties are remapped to the FreeTextBox's DownlevelRows and DownlevelColumns properties. Either set of properties can be used.
   
• DownlevelMode: The FreeTextBox property called DownlevelMode has been disabled. There was a major bug in the FreeTextBox's "Basic Editor" that caused it to break under some versions of Netscape and Mozilla (probably others as well). In this release, this property has been hard coded to TextArea only to ensure downlevel compatibility.
   
• ButtonPath: This property was modified so that the default button path is: /Communities/Common/Images/HtmlTextBoxEditorImages/. If you specify a new value for this property, the CSK will automatically map the supplied relative URL to the CSK's root. All of the standard FreeTextBox button styles are included in this location.
   
• Height and Width properties: These are still supported, and the CSK supplies this value for most skins. However, you may find better appearance if you simply omit these properties from your skins and let the control size itself. By default it will attempt to size to 100% width and 400px height.
   
• Text property: The FreeTextBox's text property has been renamed to TextOld in this mod. Due to significant differences in the standard FreeTextBox output vs. the CSK's normal text output, it was necessary to change how the control outputs text. The new behavior causes the Text property to mimic the FreeTextBox's standard RawText property. This allows the CSK to continue using the same format for storing Editor created text and preserves the standard CSK text transformation functionality.
   
• ForceDownLevel property: This is a new property added to the control that causes the FreeTextBox to render in downlevel mode even on IE browsers when a section has its HTML Editor setting set to "none".

Known bugs

• Last login time for users using persistent login is not updated unless the user manually logs in and out again. Correcting this would require adding a check in CommunitiesModule to detect when an authenticated user hits the site with a new session ID then updating the last login time accordingly.  
     
• Date Picker bug ??? http://www.asp.net/Forums/ShowPost.aspx?tabindex=1&PostID=238214  
   
• Topic page lists items in sections where the user does not have appropriate access. 
   
• Currency field in books doesn't localize.
   
• GetTopLevelSections() in section menu component may not be caching items, though it checks for cached items (not verified).  
   
• Deleting a web service from the admin tools does not delete the references from the section tools.
   
• Two sections with the same name will cause the CSK to throw an exception.  
   
• Pager in photogallery may show more pages than there really are if items are deleted from photogallery. Problem may exist in other sections using the pager control as well.
   
• RSS may not work with the CSK depending on the version of RSS. unverified fix posted at: http://www.asp.net/Forums/ShowPost.aspx?tabindex=1&PostID=307440
   
• Get file stored procedure in downloads doesn't check communityID though it takes it as a parameter.
   
• Web boxes no longer cache content. The previous output cache declaration caused all web boxes on a page to show identical content. A new output cache declaration that seems to work was published to the CSK forums, however; that declaration still results in unusual behavior when sections are set to display a random number of selected web boxes. The only reliable solution would be to cache the data used by web boxes in the cache object instead of using output cache.
     
• The CSK stored content text differently in HTML Editor enabled fields depending of the HTML Editor settings of the section. If the section has the HTML Editor disabled, the text is stored in the database unencoded. If the Editor is enabled in limited or full mode, the text is HTML Encoded. The Transformation engine in CommunityGlobals is designed to correctly adapt and encode the text depending on those same HTML Editor settings for the relevant section. However, if you change the editor settings from none to limited or full, the text engine will then assume that all data was previously HTML Encoded... but since the section had editing disabled when the text was created, the raw HTML contents of the content will be output to the screen. Also, this behavior can be confusing in Web Services. For best effect, the HTML Encoding should be applied uniformly to all content when it is saved to the database, and the text engine should not have to bother HTMLEncoding on the display end.
   
• The Server TimeZone Offset mod, supported via configuration options in the web.config file does not correctly account for daylight savings time differences. This was a design oversight in the feature. Repairing the problem is rather problematic due to a lack of support in the .NET framework for converting timezones. A 3rd party timezone component, such as the "dotNetTimeZone" download from GotDotNet will be required to fully allow configurable time zone settings. 

Back to Documentation Index