aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorfr33domlover <fr33domlover@web>2015-04-07 10:14:11 -0400
committeradmin <admin@branchable.com>2015-04-07 10:14:11 -0400
commit8dedc3cef1a76f0f12e3335fae578fdb205e88f8 (patch)
treecf469717828e162b0410273ea05ae6696f4699bb
parentddb44f16383f24f40419ab1d3afb86e71b29728e (diff)
downloadikiwiki-8dedc3cef1a76f0f12e3335fae578fdb205e88f8.tar
ikiwiki-8dedc3cef1a76f0f12e3335fae578fdb205e88f8.tar.gz
Comment on templatebody bug
-rw-r--r--doc/bugs/wrong_rendering_of_templatebody.mdwn17
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/bugs/wrong_rendering_of_templatebody.mdwn b/doc/bugs/wrong_rendering_of_templatebody.mdwn
index c4c04bee4..51cf58a8a 100644
--- a/doc/bugs/wrong_rendering_of_templatebody.mdwn
+++ b/doc/bugs/wrong_rendering_of_templatebody.mdwn
@@ -35,6 +35,23 @@ page gets rebuilt automatically after some git push, it renders the wrong way.
> early stage - I would suggest `getsetup()`, `refresh()` and `import()`
> respectively. --[[smcv]]
+>> Yes, I installed in `/usr/local`, but I also removed the deb package. So I
+>> only have 1 ikiwiki version now.
+>>
+>> I also noticed the following behavior. I created a set of pages, each of them
+>> containing several occurences of a certain template. Then I created another
+>> page, which inlines all of them. All good. Then, I edited that main page to do
+>> different sorting (using inline directive's sort option). After comitting the change,
+>> suddenly all the inlined pages have the templates inside them contain the
+>> template info instead of template body. How is that even related to the minor
+>> change I did - change the sorting? :-P
+>>
+>> I'll look at the templatebody.pm file and try debug prints. I hope I can see them in
+>> the git push output, because rendering the wiki from command line doesn't have this
+>> problem.
+>>
+>> Thanks for the pointers.
+
[[This|http://www.rel4tion.org/languages/haskell/]] is the page, and
[[this|http://www.rel4tion.org/templates/wikitag/]] is a template it uses. Right
now the template is rendered on that page exactly like the template page itself.