SharePoint Blogs / SharePoint University
SharePoint Blogs and SharePoint University - all in one place!
Need SharePoint Training? Attend a SharePoint Bootcamp!

Please delete cookies related to sharepointblogs.com and sharepointu.com to resolve login issues!

Apostrophes in Community Server

I noticed that the RSS feed for this blog had a screwed up blog title because of the apostrophe in it. It seems that community server is htmlencoding the blog title, and that is getting passed through to the RSS feed as "& # 3 9 ;". This was supposed to be fixed in a service pack, but doesn't seem to have made it in yet on this particular blog.

In the meantime, I found a workaround. Open your Windows Character Map, and choose the following character:

Select it, copy it, and paste it into the text box for your blog title. It's a good substitute, and doesn't get encoded. I'm not sure if the same problem exists for post titles, so this workaround may be applicable to those as well.


Posted 10-03-2007 4:15 PM by adamtoth

Comments

Dave Burke wrote Community Server Byte for October 13, 2007
on 10-13-2007 10:42 AM

blog bits A well-written and interesting narrative from Scott Vandehey on his frustrations with theming

Dave Burke's Community Server Bits wrote To preserve an apostrophe in his RSS feed title
on 10-13-2007 10:53 AM

Cool tip from Adam Toth on using Windows Character Map to preserve an apostrophe in his RSS feed title

Community Blogs wrote Community Server Byte for October 13, 2007
on 10-13-2007 11:00 AM

blog bits A well-written and interesting narrative from Scott Vandehey on his frustrations with theming

Matt wrote re: Apostrophes in Community Server
on 05-30-2008 1:26 PM

Thank you!!!!!!!!!!

Matt Williamson’s Blog wrote Apostrophe in Community Server Blog Title
on 05-30-2008 3:01 PM

Having an apostrophe in my blog title caused RSS users to receive a wacky title, "Matt Williamson&#39s

Add a Comment

(required)  
(optional)
(required)  
Remember Me?
Need SharePoint Training? Attend a SharePoint Bootcamp!
Posts (c) their respective authors. Everything else (c) 2009 SharePoint Experts, Inc.