aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/postsparkline_and_calendar_archive_do_not_respect_meta_directives.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/postsparkline_and_calendar_archive_do_not_respect_meta_directives.mdwn')
-rw-r--r--doc/bugs/postsparkline_and_calendar_archive_do_not_respect_meta_directives.mdwn13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/bugs/postsparkline_and_calendar_archive_do_not_respect_meta_directives.mdwn b/doc/bugs/postsparkline_and_calendar_archive_do_not_respect_meta_directives.mdwn
index 3bdcad6b9..f41f80220 100644
--- a/doc/bugs/postsparkline_and_calendar_archive_do_not_respect_meta_directives.mdwn
+++ b/doc/bugs/postsparkline_and_calendar_archive_do_not_respect_meta_directives.mdwn
@@ -17,3 +17,16 @@ Articles par mois:
</pre>
Is it possible the `meta(date)` directives are being ignored by those plugins? --[[anarcat]]
+
+> For background, each page has two dates: creation date (`ctime`, `meta(date)`)
+> and last modification date (`mtime`, `meta(updated)`). postsparkline
+> defaults to showing the ctime but can be configured to use the mtime
+> instead; calendar always uses ctime. So what you're doing *should* work
+> like you expect.
+>
+> The plugins don't get to choose whether they ignore meta(date);
+> the effect of a meta(date) directive in `$page` is to set `$pagectime{$page}`
+> during scanning (overriding whatever was found in the filesystem), and
+> that data structure is what the plugins read from. So the first thing to
+> investigate is whether the ctime
+> [[in your .ikiwiki/indexdb|tips/inside_dot_ikiwiki]] is correct. --[[smcv]]