X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/64c3c474b2c6301b795bb1fe375955661c51f93f..a1d4e3ba47d962ca7455284b88fbfea1604b7cdd:/doc/tips/howto_avoid_flooding_aggregators.mdwn

diff --git a/doc/tips/howto_avoid_flooding_aggregators.mdwn b/doc/tips/howto_avoid_flooding_aggregators.mdwn
index d432464fc..570baa5cc 100644
--- a/doc/tips/howto_avoid_flooding_aggregators.mdwn
+++ b/doc/tips/howto_avoid_flooding_aggregators.mdwn
@@ -1,4 +1,4 @@
-If you have a [[blog]] that is aggregated, either on a site like Planet
+If you have a [[ikiwiki/blog]] that is aggregated, either on a site like Planet
 Debian, or just through user subscriptions, one common problem is that
 changes to the guids of items in the blog can "flood" the aggregator,
 causing all recent blog entries to be posted to the top of it. 
@@ -14,12 +14,12 @@ This can happen in a lot of situations:
 * Perhaps you've just moved stuff around in your wiki.
 
 To avoid annoying readers in these situations, it's a good idea to remove
-and existing items from your blog's news feed. That way only new items will
-show up in the aggregator. The best way to do this is currently to modify
-the [[PageSpec]] for your [[blog]] and add a condition such as:
+any existing items from your blog's news feed. That way only new items will
+show up in the aggregator. The best way to do this is to add a `feedpages`
+parameter to the `inline` directive for your blog, with a condition such as:
 
-	and created_after(blog/posts/old_post)
+	feedpages=created_after(blog/posts/old_post)
 
 Where "old_post" is the name of the last post you made to the blog before
-making the change. This will limit the feed to only newer posts (the older
-posts will still be available in the archives).
+making the change. This will limit the feed to only newer posts, while stil
+displaying the old posts in the blog page.