I have found that I encounter the same problem in CS2007 as I did in 2.1. The tag cloud url encoding converts spaces to the + character. When IIS on my Vista box processes the request, it produces a 404 error. If a %20 combination is used instead, the url is valid.
I have checked out the CS2007 source to look at the TagCloud control that is responsible for the rendering of this part of the page. The code winds its way right down to the UrlEncodePathComponent method in the WebHelper class in Telligent.Components.dll. The method simply contains the following:
public static string UrlEncodePathComponent(string text)
{
return UrlEncode(text, _pathComponentTextToEscape, '+', '_');
}This is where the + character is specified as the replacement for spaces in urls. But is this a problem? Well, no. A + character is a valid space character to use. So is it a problem with IIS on Vista, or a problem with how Community Server is rewriting the url?
I have noticed that spaces in tag names on the Community Server site doesn't cause a problem. I wonder which OS they are hosted on.
Tags: