Gary Oberbrunner wrote:
>>> XML Parsing Error: undefined entity
> ...>>
>>> It is choking on the undefined entity "…".
It seems the rss feed from my trac (trunk, up to date as of today) produces
bad description chunks like this:
<description><ul class="changes"><li><div
class="copy"></div>branches/dev_branch/sapphire/log.c</li><li>…</li></ul><p>
Merged <a class="changeset" href="http://www/trac/changeset/11781";
title="Logging facility ...">[11781]</a> (logging support) to trunk
</p>
</description>
which contains the invalid … entity, and also contains a lot more
unescaped HTML than I'd expect.
The main trac site's RSS feed, OTOH, produces description chunks for
changesets like this:
<description><p>
Markup branch: Renamed the <tt>pack</tt> function to <tt>group
</tt> and make it available to any template.
</p>
</description>
... which is fine (and expat says it's valid xml). So my question is what's
wrong with my setup? I'm running from today's trunk as far as I can tell, I
resynced my repository, and I'm not seeing any other errors.
Does the format of my description chunk above look familiar to anyone? As you
can see it includes the path of the first changed file with some html markup,
which the trac site's rss feed doesn't. I'm using identically structured
requests for both the rss pages (?changeset=on&max=50&daysback=90&format=rss)
but the returned xml looks really different.
Could it be a config option or something?
thx,
-- Gary
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
