sigh, still broken, different error message.

[git.ikiwiki.info.git] / doc / bugs / template_creation_error.mdwn

diff --git a/doc/bugs/template_creation_error.mdwn b/doc/bugs/template_creation_error.mdwn
index d3c0bcca5c9fcdbe2539c86e164faa9da7875ebc..9d6915b09d4a6b81674303d6f801c838bd8efa67 100644 (file)
--- a/doc/bugs/template_creation_error.mdwn
+++ b/doc/bugs/template_creation_error.mdwn
@@ -234,6 +234,15 @@ same logic as IkiWiki itself. I don't think that's serious. --[[smcv]]
 >>> drop the contents of `%scanned` and rely on a single boolean
 >>> flag instead.
 >>>
 >>> drop the contents of `%scanned` and rely on a single boolean
 >>> flag instead.
 >>>

+>>>> This is not actually good enough for the templatebody
+>>>> directive, which does in fact need to scan certain pages
+>>>> during the render phase, namely when a page that is rendered
+>>>> due to dependencies uses a template that no other page being
+>>>> rendered in this pass was using. I've reverted this optimization,
+>>>> to fix [[wrong rendering of templatebody]], and applied a more
+>>>> limited version which only optimizes rebuilds (the worst case
+>>>> of this memory consumption). --[[smcv]]
+>>>

 >>> `%scanned` is likely to be no larger than `%rendered`, which
 >>> we already track, and whose useful lifetime does not overlap
 >>> with `%scanned` now. I was tempted to merge them both and call
 >>> `%scanned` is likely to be no larger than `%rendered`, which
 >>> we already track, and whose useful lifetime does not overlap
 >>> with `%scanned` now. I was tempted to merge them both and call


@@ -261,4 +270,17 @@ same logic as IkiWiki itself. I don't think that's serious. --[[smcv]]
 >>>> an error to invoke scan in the render phase; that would mean that
 >>>> `readtemplate` needs to check whether it's invoked as a scan or not to
 >>>> decide whether to scan the template page, but would be generally more
 >>>> an error to invoke scan in the render phase; that would mean that
 >>>> `readtemplate` needs to check whether it's invoked as a scan or not to
 >>>> decide whether to scan the template page, but would be generally more

->>>> robust for future plugin writing. --[[chrysn]]
+>>>> robust for future plugin writing.
+>>>>
+>>>>> At the moment templatebody really does need to re-scan templates in
+>>>>> the render phase, unfortunately. Not scanning in the render phase
+>>>>> seems to be precisely how [[wrong rendering of templatebody]]
+>>>>> happened. --s
+>>>>
+>>>> **addendum**: if the new phase state is used to create warnings/errors
+>>>> about improper ikiwiki api use of plugins (which is something i'd
+>>>> advocate), that should likewise warn if `add_link` actually adds a link in
+>>>> the render phase.  such a warning would have helped spotting the
+>>>> link-related [[template evaluation oddities]] earlier. --[[chrysn]]
+
+>>>>> [[Merged|done]] --[[smcv]]