aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/can__39__t_mix_template_vars_inside_directives.mdwn14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/bugs/can__39__t_mix_template_vars_inside_directives.mdwn b/doc/bugs/can__39__t_mix_template_vars_inside_directives.mdwn
index 0fa85effb..462852ef8 100644
--- a/doc/bugs/can__39__t_mix_template_vars_inside_directives.mdwn
+++ b/doc/bugs/can__39__t_mix_template_vars_inside_directives.mdwn
@@ -31,3 +31,17 @@ The result, even with htmlscrubber disabled, is mangled, something like
</div>
Any suggestions gladly received. -- [[Jon]]
+
+> Well, you *should* be able to do things like this, and in my testing, I
+> *can*. I used your exact example above (removing the backslash escape)
+> and invoked it as:
+> \[[!template id=test href=himom.png size=100x]]
+>
+> And got just what you would expect.
+>
+> I don't know what went wrong for you, but I don't see a bug here.
+> My guess, at the moment, is that you didn't specify the required href
+> and size parameters when using the template. If I leave those off,
+> I of course reproduce what you reported, since the img directive gets
+> called with no filename, and so assumes the size parameter is the image
+> to display.. [[done]]? --[[Joey]]