|
Notes |
|
|
(0005642)
|
|
Wanderer
|
2004-06-01 03:59
(edited on: 2004-06-01 04:03) |
|
It's not for direct browsing, it's URL, which can be added to any RSS-aggregator for reading news (and only news now :-( ) from site
Just for note - it works, and news really aggregated in reader
edited on: 06-01-04 04:03 |
|
|
|
|
|
I usually get to a page of XML when I click on RSS links, rather than a strange error. I'm not much of an RSS user, so I could be mistaken, but it seems odd for a hyperlink that shows up in the web browser to lead to an error like this. |
|
|
|
|
|
Hmmm, I'm getting the same error from my news aggregator, so this looks like a real error in the RSS feature to me. Can you reproduce this by adding a new subscription based on the current RSS link? |
|
|
|
|
|
|
|
|
|
I looked at your demo site, and yes, it looks okay. Is this issue unique to version 0.18.2? (My own installation isn't configured to use RSS, so I can't check there.) |
|
|
|
|
This issue is really biting me :( The problem is that the '&' in is invalid, and needs to be escaped as & in XML to work properly. Note that this is only showing up in messages like the change log. (ie. those containing )
I've tested this by substituting the following string:
with
and it works perfectly in a local copy of the current rss feed for this project. |
|
|
|
|
I think this is a bug in the RSS library that we are using. I would expect this library to escape the data before generating the XML file.
These are the options to fix this library:
- Add the escaping to the external library (or see if this issue is fixed in more recent versions).
- Move to a different library (that hopefully fixes this and uses GPL license.
- For now, escape the data before setting it into the RSS generator.
This bug will depend on the contents of the news, rather than a specific version of Mantis. |
|
|
|
|
|
I tested it now and it seems to be working. The official bugtracker is now using Mantis 1.0.0a1 which may have the fix for this problem. |
|
|
|
|
|
I didn't read the comments again before posting my last comment. The problem is probably not fixed yet. |
|