aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAmitai Schlair <schmonz-web-ikiwiki@schmonz.com>2013-09-14 22:43:36 -0400
committerAmitai Schlair <schmonz-web-ikiwiki@schmonz.com>2013-09-14 22:43:36 -0400
commit0cb014b9d26cdbc0693421a6577f74042f5591b6 (patch)
tree6a39ca8492186f6bb358d27c76207d7bcae7c36f
parentbe2dc11639a07ba6479569506f3e4d75d691ba86 (diff)
downloadikiwiki-0cb014b9d26cdbc0693421a6577f74042f5591b6.tar
ikiwiki-0cb014b9d26cdbc0693421a6577f74042f5591b6.tar.gz
template a red herring; toc vs. inline guilty
-rw-r--r--doc/plugins/toc/discussion.mdwn9
-rw-r--r--doc/todo/fancypodcast.mdwn6
2 files changed, 9 insertions, 6 deletions
diff --git a/doc/plugins/toc/discussion.mdwn b/doc/plugins/toc/discussion.mdwn
index a09ae5703..028437dba 100644
--- a/doc/plugins/toc/discussion.mdwn
+++ b/doc/plugins/toc/discussion.mdwn
@@ -8,3 +8,12 @@ rendered content. --[[JasonBlevins]]
Why doesn't the TOC appear in the edit page preview? It only appears when the page is finally rendered. This makes it somewhat difficult to organize headings, saving & re-editing all the time. My user page currently has a toc to play with: --[[sabr]]
> Fixed. --[[Joey]]
+
+Just ran into a side effect of `\[[!toc]]` being a NOP in pages
+which are inlined: pages with `\[[!template id=note text="\[[!toc]]"]]`
+wound up having the note rendered in feeds as "Use this template
+to insert a note into a page". Worked around this by making a local
+copy of the template and removing its `<TMPL_UNLESS text>...</TMPL_UNLESS>`
+section. Besides needing to generate guaranteed-unique anchor names,
+are there other reasons this directive couldn't be made to work on
+inlined pages? --[[schmonz]]
diff --git a/doc/todo/fancypodcast.mdwn b/doc/todo/fancypodcast.mdwn
index 7ffff6252..128017021 100644
--- a/doc/todo/fancypodcast.mdwn
+++ b/doc/todo/fancypodcast.mdwn
@@ -56,12 +56,6 @@ Episode enclosure |(./) |(./) |(./) |(./)
### Other ideas
-* Don't render template text (e.g., "Use this template to insert a
- note into a page") in feeds.
- * [[schmonz]] observes this in a dual-feed (one for enclosures,
- another for browsers) scenario, but not in the typical case.
- Remaining to be verified: that once migrated to fancypodcast,
- this stops being a problem.
* Optionally specify the enclosure's:
* MIME type, in case `File::MimeInfo` guesses wrong.
* Duration, in case `ffprobe` guesses wrong.