comment on the difficulty of trails
authorhttp://kerravonsen.dreamwidth.org/ <http://kerravonsen.dreamwidth.org/@web>
Fri, 4 Nov 2011 02:50:00 +0000 (22:50 -0400)
committeradmin <admin@branchable.com>
Fri, 4 Nov 2011 02:50:00 +0000 (22:50 -0400)
doc/todo/Pagination_next_prev_links.mdwn

index 8b31143407df935959f7aa628e033f2cc874d14b..f1c12d33ffc17b48fbaed2ba60fad4cbca85d867 100644 (file)
@@ -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]]