X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/9672f012a4051928000ca8c6ad47e7b577f7d965..2f3a4f689948a9f51699efed4d8c6b9fdc167100:/doc/patchqueue/calendar_--_archive_browsing_via_a_calendar_frontend.mdwn diff --git a/doc/patchqueue/calendar_--_archive_browsing_via_a_calendar_frontend.mdwn b/doc/patchqueue/calendar_--_archive_browsing_via_a_calendar_frontend.mdwn index 0abe2c901..fe0dba1aa 100644 --- a/doc/patchqueue/calendar_--_archive_browsing_via_a_calendar_frontend.mdwn +++ b/doc/patchqueue/calendar_--_archive_browsing_via_a_calendar_frontend.mdwn @@ -119,8 +119,8 @@ annual and monthly indices, for example, by using something like this sample from my I (warning: line split for readability): - [[meta title="Archives for 2006/01"]] - [[inline rootpage="blog" atom="no" rss="no" show="0" + \[[meta title="Archives for 2006/01"]] + \[[inline rootpage="blog" atom="no" rss="no" show="0" pages="blog/* and !*/Discussion and creation_year(2006) and creation_month(01)" ]] @@ -593,16 +593,16 @@ I've been looking over the calendar plugin. Some items: that emitting the whole calendar in the preprocess hook would simplify things and you'd not need to save state about calendars. -> A) I am scared of the html scrubber, and have never turned it on, +> I am scared of the html scrubber, and have never turned it on, > and did not look too deeply into what would be scrubbed out --ManojSrivastava >> Unless you're using javascript, a few annoyances link , or inline >> css, it's unlikly to object to any html you might write. The list of >> allowed tags and attributes is easy to find near the top of the plugin. -> B) In case the option that gets the ctime of the pages from the -> SCM itself, %IkiWiki::pagectime is not populated that early, -> is it? So I waited until the last possible moment to look at -> the time information. +> In case the option that gets the ctime of the pages from the +> SCM itself, %IkiWiki::pagectime is not populated that early, +> is it? So I waited until the last possible moment to look at +> the time information. > >> Actually, since my big rewrite of the rendering path a few months ago, >> ikiwiki scans and populates almost all page information before starting