aboutsummaryrefslogtreecommitdiff
path: root/IkiWiki/Plugin/trail.pm
Commit message (Collapse)AuthorAge
* trail: don't generate a costly dependency when forcing sort orderSimon McVittie2014-07-11
| | | | | | | | pagespec_match_list() makes the current page depend on the pagespec being matched, so if you use [[!trailoptions sort="..."]] to force a sort order, the trail ends up depending on internal(*) and is rebuilt whenever anything changes. Add a new sort_pages() and use that instead.
* trail: Avoid massive slowdown caused by pagetemplate hook when displaying ↵Joey Hess2013-01-24
| | | | | | | | | | | dynamic cgi pages, which cannot use trail anyway. This seemed to be due to the pagetemplate hook calling prerender. I've observed this making it take *minutes* for the signin page to be displayed. ltracing ikiwiki showed it was matching pagespecs a lot. It may be that this is still a speed pain point when rendering pages, not just for CGI. So more work may be needed here.
* trail: remove excess presence-dependenciesSimon McVittie2013-01-02
| | | | | | | | | | | | Since trail members are explicitly rebuilt if the information used for their prev/up/next boxes changes, they don't need another dependency on the trail itself. (If the trail disappears, it will disappear from the member's member_to_trails entry, causing a rebuild; so the add_depends is redundant.) Similarly, since trail members are explicitly rebuilt if their next or previous item, or its title, changes, the presence dependencies on the next and previous items are redundant.
* If the title of a trail or trail-member changes, rebuild affected pagesSimon McVittie2013-01-02
| | | | | | | | If the title of a trail changes, each member of that trail must be rebuilt, for its prev/up/next box to reflect the new title. If the title of a member changes, its next and previous items (if any) must be rebuilt, for their prev/up/next boxes to reflect the new title.
* trail: call prerender from build_affectedSimon McVittie2013-01-02
| | | | | | | | In the unlikely event that the ordered contents of a trail have changed without the TRAILS or TRAILLOOP template variables being evaluated (for instance, all trail directives are removed from a former trail that uses a custom pagetemplate that doesn't contain TRAILS), we might get here without having already called prerender.
* trail: Converted all dependencies to presence dependencies.Joey Hess2012-12-27
| | | | smcv please note this introduces another bug, which I've opened
* trail: delete the right stateSimon McVittie2012-04-09
| | | | | | | | | At some point I changed the storage of trail members' membership and forgot to update this use. (It turns out to be rather difficult to reach this code, possibly even impossible: it only applies if a member somehow ceases to match the trail's pagespec without either the trail or the member changing.)
* trail, inline: treat pagenames as a list of literal names, not linksSimon McVittie2012-04-06
|
* trail: fix inline documentationSimon McVittie2012-04-06
|
* remove pod documentationJoey Hess2012-03-19
| | | | | This caused the build system to make unwanted man pages. Using comments instead.
* Add a build_affected hook so trail doesn't have to injectSimon McVittie2012-03-18
| | | | | In principle, building any pages affected by links, backlinks etc. could work the same way.
* Replace [[!trailinline]] directive with [[!inline trail=yes]]Simon McVittie2012-03-18
|
* Split trail directive into trailitems, trailoptionsSimon McVittie2011-11-12
|
* trail: update documentation; drop docs for directives, which are now in the wikiSimon McVittie2011-11-12
|
* trail: improve and test sortingSimon McVittie2011-11-12
|
* trail: avoid collecting trail members twiceSimon McVittie2011-11-12
|
* trail: new plugin (3rd attempt)Simon McVittie2011-11-09