March 2007 - Posts
While looking into some mirrored blog issues, I noticed that the blog comment flags were not functioning properly. I have currently discovered that the EnableCommentsDefault property has been erroneously used in several places where the EnableCommentsOverride property should have been used. In fact, several of the Default properties appear to have been erroneously used where Override properties should have been used.
It looks like the RssComments and others may also be affected, but I am not familiar with those sections and how they are supposed to work, so I didn't make any changes in those areas. Here are the changes I made:
Location #1
On or around line 658 of CommunityServerBlogs(20)\Components\Weblog.cs either comment out or remove the following 2 lines:
if(!EnableCommentsDefault)
return false;
Location #2
On or around line 233 of CommunityServerBlogs(20)\Controls\AggregateBlogControls\AggregateList.cs change:
Comments.Text = String.Format(ResourceManager.GetString("Weblog_EntryList_Comments"), (!post.Weblog.EnableCommentsOverride || !post.Weblog.EnableCommentsDefault || post.IsLocked) ? "0" : post.Replies.ToString());
to:
Comments.Text = String.Format(ResourceManager.GetString("Weblog_EntryList_Comments"), (!post.Weblog.EnableCommentsOverride || post.IsLocked) ? "0" : post.Replies.ToString());
Location #3
On or around line 247 of CommunityServerBlogs(20)\Controls\AggregateBlogControls\AggregateList.cs change:
CommentCount.Text = (!post.Weblog.EnableCommentsOverride || !post.Weblog.EnableCommentsDefault || post.IsLocked) ? "0" : post.Replies.ToString();
to:
CommentCount.Text = (!post.Weblog.EnableCommentsOverride || post.IsLocked) ? "0" : post.Replies.ToString();
Location #4
On or around line 241 of CommunityServerBlogs(20)\Controls\EntryList.cs change:
if((CurrentWeblog.EnableCommentsDefault && !entry.IsLocked) || entry.Replies > 0)
to:
if((CurrentWeblog.EnableCommentsOverride && !entry.IsLocked) || entry.Replies > 0)
Location #5
On or around line 403 of CommunityServerBlogs(20)\Controls\EntryList.cs change:
if ((CurrentWeblog.EnableCommentsDefault && !weblogPost.IsLocked) || weblogPost.Replies > 0)
to:
if ((CurrentWeblog.EnableCommentsOverride && !weblogPost.IsLocked) || weblogPost.Replies > 0)
Location #6 - This is an XML comment error only
On or around line 624 of CommunityServerComponentss(20)\Components\Post.cs change:
Whether or not this post allows replies
to:
Whether or not this post has been read by poster
Location #7
On or around line 50 of CommunityServerWeb(20)\ControlPanel\Blogs\SyndicationOptions.aspx.cs change:
if (CurrentWeblog.EnableCommentsDefault == false)
to:
if (CurrentWeblog.EnableCommentsOverride == false)
Location #8
On or around line 81 of CommunityServerWeb(20)\ControlPanel\Blogs\SyndicationOptions.aspx.cs change:
if (CurrentWeblog.EnableCommentsDefault == false)
to:
if (CurrentWeblog.EnableCommentsOverride == false)
And here is a partial list of possible locations for the second issue:
CommunityServerBlogs(20)\Components\Syndication\RssCommentHandler.cs - (47, 15) : if (!blog.EnableCommentsDefault)
CommunityServerBlogs(20)\Components\Syndication\WeblogCategoryRssWriter.cs - (41, 60) : return base.AllowComments && CurrentWeblog.EnableCommentsDefault;
CommunityServerBlogs(20)\Components\Syndication\WeblogRssWriter.cs - (63, 60) : return base.AllowComments && CurrentWeblog.EnableCommentsDefault;
CommunityServerBlogs(20)\Components\Syndication\WeblogRssWriter.cs - (80, 22) : if (CurrentWeblog.EnableCommentsDefault && CurrentWeblog.EnableRssCommentsDefault)
There may be other places as well, but these are the ones that I have found and am sure about.
I will be changing the URL for this blog to represent its new name, "CS Nuggets". I've had a couple users think that this was an official Community Server site, so I'm making some changes to prevent others from making the same mistake. The name has been changed to "CS Nuggets" and the URL will be changing sometime after midnight tonight, so that everyone will at least get this notice. The new URL will be:
RSS: http://www.opensourcec.org/blogs/csnuggets/rss.aspx
ATOM: http://www.opensourcec.org/blogs/csnuggets/atom.aspx
Note: The new aggregate mirror will automatically be updated.
Hey All,
I've been wanting to create an aggregate blog that contains the posts from my Community Server blog (CS Nuggets) and my user blog, but didn't really know how to do it until now. I found a funky bug if you use the same application pool for multiple CS sites, so I had to create separate application pools for each site. But I finally did get it working. Here is the new blog info:
Name: Bill Bosacker & CS Nuggets
URL: http://www.opensourcec.org/blogs/billcs/
RSS: http://www.opensourcec.org/blogs/billcs/rss.aspx
If you are currently just using the Community Server blog (changed to CS Nuggets), you may want to switch over to this new blog as I intended to start posting in my user blog. The post about Visual Studio Service Pack 1 should have been in my user blog, but I didn't know how to do this until now. Since I know Dave Burke is reading this, maybe he'll write up something nifty to make it easy. 
Take it easy, and enjoy...
Well, Jose Lema posted the blog entry "CS Bug: Read Status" about what we have been working on and why its taking some time to get it right, so I thought I may as well roll out the current changes. These changes are only compatible with CS 2.x and CS 2007 BETA 1. They are not compatible with later versions of CS 2007 as the code base has changed, but the functionality should be incorporated into these builds.
Due to some concerns of Jose's, I decided to post 2 different patches in the "BUG FIX: Read/Unread Flags 1.1" download named current and proposed. The current version is the version that is currently running on the communityserver.org site and the proposed version is the version that I am running on my sites. I will try to keep a list of differences between the two.
I encourage everyone to use the current version and only try the proposed version if you have any issues on the list of differences or if you have an issue that isn't on the list, but you think that it may have been fixed in the proposed version. Please post your comments here, especially if you are using the proposed version. I would like to know why you used the proposed version and whether or not it fixed the issue that you are having.
Thanks,
Bill
NOTE: MAKE SURE YOU READ AND FULLY UNDERSTAND ALL OF THE DOWNLOAD INFORMATION BEFORE INSTALLING
After working with Jose Lema today in getting this bug fix incorporated into CS 2007, I have updated the download to incorporate the current changes. This update should be friendly to very large databases and is the current code that was just checked in for CS 2007. It has only been tested on CS 2.1 SP1 and CS 2007, but should be compatible with any CS 2.x release version. As with any bug fix, please make sure you perform a backup and have a roleback plan before implementing it in case something should go wrong.
Click here to get the download