Community Server 2008 Form Breaking Changes
I've been charged recently with the task of upgrading several custom Community Server 2007.1 sites to CS 2008. Most of these upgrades are quick-and-dirty, without all of the effort necessary to fully re-theme these applications. During the upgrades, one problem that I encountered frequently was the issue of changed properties in form classes (classes derived from PreTemplatedWrappedFormBase and WrappedSubFormBase). Most of these forms have properties containing the ID's of controls in the form. What I found was that from 2007.1 to 2008, several forms had these ID properties removed or renamed, which causes pages that reference them to not function properly.
So, this post is an attempt to list all of the breaking changes in these ID properties between CS 2007.1 and 2008. I'm not including properties that were added between 2007.1 and 2008, just those that were renamed or removed. If you find any changes that I missed, please let me know and I'll update the list:
Oh, and I didn't include anything from the Control Panel, since it's been radically changed between versions.
CommunityServer.Blogs.Controls.CreateEditWeblogPostForm
CommunityServer.Controls.SearchForm
CommunityServer.Controls.EditUserForm
-
SignatureTextBoxId - this was replaced by the SignatureEditorId, which expects to point to an Editor rather than a simple TextBox.
-
BioTextBoxId - this was replaced by the BioEditorId, which expects to point to an Editor rather than a simple TextBox.
-
EnableInkCheckBoxId - this was eliminated in 2008.
-
ThemeDropDownListId - this was eliminated in 2008.
CommunityServer.Discussions.Controls.CreateEditForumPostForm
-
RecipientsTextId - this was eliminated in 2008. This text box was only used when creating Private Messages, which became Conversations in CS 2008. If you didn't have the create/edit post page customized, then you can go ahead and ignore this one.
CommunityServer.Discussions.Controls.ForumPostTreeForm
-
PostTreeViewId - this property was replaced by PostTreeId, which expects a Telligent.Glow.Tree rather than a ComponentArt.Web.UI.TreeView. If you don't fix this then the threaded view of a thread will not work at all.
-
PostTreeContextMenuId - this property was replaced by PostTreePopupMenuId, which expects a Telligent.Glow.PopupMenu rather than a ComponentArt.Web.UI.Menu. Again, fix this or your threaded view will raise an error.
That's all I was able to find. Again, let me know if there is anything missing.