summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorhttp://schmonz.livejournal.com/ <http://schmonz.livejournal.com/@web>2008-09-17 14:52:50 -0400
committerJoey Hess <joey@kitenet.net>2008-09-17 14:52:50 -0400
commit0205a78dba9cb74a614142deae27a1a5e9561cc6 (patch)
tree463b5f0fe70b0415956ec898fe18bbaca15790f3
parentda7c6eb1b40de8ca02a2d36dff3da24e43977490 (diff)
response to response
-rw-r--r--doc/plugins/aggregate/discussion.mdwn9
1 files changed, 3 insertions, 6 deletions
diff --git a/doc/plugins/aggregate/discussion.mdwn b/doc/plugins/aggregate/discussion.mdwn
index 3b3d1ea3b..62db5c816 100644
--- a/doc/plugins/aggregate/discussion.mdwn
+++ b/doc/plugins/aggregate/discussion.mdwn
@@ -26,12 +26,7 @@ I'm trying to set up a [planet of my users' blogs](http://help.schmonz.com/plane
Two things aren't working as I'd expect:
1. `expirecount` doesn't take effect on the first run, but on the second. (This is minor, just a bit confusing at first.)
-
->
-
-2. Where are the article bodies for e.g. David's and Nathan's blogs? The bodies aren't showing up in the `._aggregated` files for those feeds, but the bodies for my own blog do, which explains the planet problem, but I don't understand the underlying aggregation problem. (Those feeds include article bodies, and show up normally in my usual feed reader rss2email.) How can I debug this further?
-
---[[schmonz]]
+2. Where are the article bodies for e.g. David's and Nathan's blogs? The bodies aren't showing up in the `._aggregated` files for those feeds, but the bodies for my own blog do, which explains the planet problem, but I don't understand the underlying aggregation problem. (Those feeds include article bodies, and show up normally in my usual feed reader rss2email.) How can I debug this further? --[[schmonz]]
> I only looked at David's, but its rss feed is not escaping the html
> inside the rss `description` tags, which is illegal for rss 2.0. These
@@ -43,3 +38,5 @@ Two things aren't working as I'd expect:
> It's sorta unfortunate that [[cpan XML::Feed]] doesn't just assume the
> un-esxaped html is part of the description field. Probably other feed
> parsers are more lenient. --[[Joey]]
+
+>> Thanks for the quick response (and the `expirecount` fix); I've forwarded it to David so he can fix his feed. Nathan's Atom feed validates -- it's generated by the same CMS as mine -- so I'm still at a loss on that one. --[[schmonz]]