I have upgraded a project from 3.0 to the latest version, including the blog module and its widgets. Everything works great except a weird rendering of the RSS Feed. It appears to show the actual source code. If I look at e.g. www.silverstripe.org/blog/rss I will see the line of "This XML file does not appear to have any style information associated with it. The document tree is shown below." and then the content in XML tags. With my project however the first line is missing and alls quotes and specialchars are crooked (see attachment). Even if I remove the actual content from the template, to make sure it's not the German spechialchars that cause the problem, it is not recognized as an XML output. I had the same issue with 3.0 which was one of the reasons to upgrade.
Just to make sure if this is or isn't a bug/issue in the blogmodule, could you do a plain install of just SilverStripe plus Blogmodule and see if the problem persists? If not, it must be something else...
Edit: another thing to do would be to temporary change the locale for the site to en_US to see if that has an impact.
thanks für your reply. Changing the locale didn't change anything unfortunately . As I said, I have also tried to replace the rss template with a very basic XML file - no content from the datebase included - and it also didn't render the output correctly. On the other hand, if I take the original template (without any dynamic content in it) and save it as an .xml file on the server, it looks the way it should. I have the feeling something else must be happening. I am using diverse add-ons so reinstalling would be quite an effort. And the site is live and running - except for that issue.
Would it make sense to test on my local environment, or is it possibly something in connection with the server config?
I only tried Chrome before. Firefox looks fine and Safari does the weirdest thing. It will open a new Chrome-Window :-o and even start Chrome if it was shut down first. But the window then stays blank and Safari jumps back to the blog itself. Cross-Browser-Weirdness...
If I find the time I'll also try a clean install locally tomorrow. Thanks for your effort in any case!