-
- 24,544 Posts
[quote author=jrotering link=topic=49368.msg288158#msg288158 date=1273866140]
[[to customize the header, save your custom div structure in a chunk and pass the chunk name as the value of &customHeaderChunk]]
This will work now. When MODx doesn’t find the snippet, it will eat the tag (at the cost of a little processing time).
I do like your idea since it would be faster if MODx knew to just eat tags with a certain token.
-
- 24,544 Posts
Quote from: jrotering at May 14, 2010, 07:42 PM
[[to customize the header, save your custom div structure in a chunk and pass the chunk name as the value of &customHeaderChunk]]
This will work now. When MODx doesn’t find the snippet, it will eat the tag (at the cost of a little processing time).
I do like your idea since it would be faster if MODx knew to just eat tags with a certain token.
Funny, I didn’t think of that! But yeah, if it were made formal and wouldn’t tax processing time, that would be even better.
-
- 101 Posts
two thumbs up, way up. great suggestion but maybe a way to let some pass through if necessary.
[[# This comment should never show up in html and is the default style of comment]]
[[#comment? &displayInHtml=`false`: This comment should also NOT show up in html!]]
[[#comment? &displayInHtml=`true`: This comment should show up in the rendered html]]
or some easier and less ’comment’ intrusive convention, but still allow them to pass through if needed....
....I sometimes mark templates with comments for customers.
-
- 26 Posts
I’m not sure I’ve fully understood the issue....anyway, to comment portions of code in tpl I use the straight Php comment tag {* this is commented out *} and it works with no problem.
-
- 8 Posts
I was looking for making comments in Chunck too.
For now I use the [[ ]] trick, but I agree a official comment tag would be great!