aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorhttp://kerravonsen.dreamwidth.org/ <http://kerravonsen.dreamwidth.org/@web>2011-11-03 22:50:00 -0400
committeradmin <admin@branchable.com>2011-11-03 22:50:00 -0400
commitf6d66d46845534da1b7677922193f24363f44003 (patch)
treec6cea9bc66eb0e648b1da69218d9725a44daa8db
parent050a4f7669d614280d92764d0948585982718069 (diff)
downloadikiwiki-f6d66d46845534da1b7677922193f24363f44003.tar
ikiwiki-f6d66d46845534da1b7677922193f24363f44003.tar.gz
comment on the difficulty of trails
-rw-r--r--doc/todo/Pagination_next_prev_links.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/todo/Pagination_next_prev_links.mdwn b/doc/todo/Pagination_next_prev_links.mdwn
index 8b3114340..f1c12d33f 100644
--- a/doc/todo/Pagination_next_prev_links.mdwn
+++ b/doc/todo/Pagination_next_prev_links.mdwn
@@ -27,4 +27,7 @@ Thank you
> reduces the generic usefulness of typed links, though - in particular
> you can no longer use "is part of trail A" in a PageSpec. --[[smcv]]
+>>> Indeed, I know the problem; I ran into the same kind of thing with my [[plugins/contrib/report]] plugin and its `trail` concept.
+>>> I simply had to declare that one couldn't use "trail" and "maketrail" options within the same report. That way, "maketrail" will add links in the "scan" pass, and "trail" will test for links in the "build" pass. That usually works. --[[KathrynAndersen]]
+
>> Do you have an example? --[[hendry]]