summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJoey Hess <joey@kodama.kitenet.net>2008-06-24 23:46:40 -0400
committerJoey Hess <joey@kodama.kitenet.net>2008-06-24 23:46:40 -0400
commitfcf144aaeb150aa2520a66ac2ccf97e2a509f7f8 (patch)
tree163ff992e45edd278a907c93a78f000bc5378d8a /doc
parent22100642099595cb2f7393044aa4be511ef9721c (diff)
questions
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/Set_arbitrary_date_to_be_used_by_calendar_plugin.mdwn14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/todo/Set_arbitrary_date_to_be_used_by_calendar_plugin.mdwn b/doc/todo/Set_arbitrary_date_to_be_used_by_calendar_plugin.mdwn
index c14c54869..e4dd729e3 100644
--- a/doc/todo/Set_arbitrary_date_to_be_used_by_calendar_plugin.mdwn
+++ b/doc/todo/Set_arbitrary_date_to_be_used_by_calendar_plugin.mdwn
@@ -6,6 +6,20 @@ Here's a patch to the calendar plugin. If you specify an event preprocessor in a
That date will be used instead of the post creation time when displaying the calendar.
+> Thanks for coming up with a patch.. Let me make sure I understand its
+> rationalle.
+>
+> The meta plugin already allows modifying the page creation time,
+> which is what the calendar plugin uses.
+>
+> So, it seems to me that the use of this patch is for recording events in
+> the future. You'd not want a page for a future event to claim it was
+> created in the future. I suppose you could also use it for events in the
+> past, if you didn't want to change the creation time for some reason.
+> (Perhaps you're doing a calendar of historical events, for example.)
+>
+> Accurate? --[[Joey]]
+
--- calendar.pm.orig 2008-06-24 22:36:09.000000000 -0400
+++ calendar.pm 2008-06-24 22:51:11.000000000 -0400
@@ -23,6 +23,7 @@