[Snippet] Replix 1.7.5 (upd 19-06)

Snippet tags can take two forms, [[SnippetName]] or [!SnippetName!].

The first form is a normal snippet call; if the page is cached, the snippet’s output will also be cached. Usually this will not be a problem. Sometimes, however, it is important that the snippet’s output not be cached. For example, the Login snippet needs to determine if the user has logged in, and if not, display the login form, and if so, display the logout link. If the page is cached, the snippet is not run, and the display would not change. The second form, using exclamation marks, causes the snippet to be run even if the page has been cached. For a menu, however, that probably isn’t necessary.

TinyButStrong Error in field [{post.name...}] : item ’name’ is not an existing key in the array. This message can be cancelled using parameter ’noerr’.

TinyButStrong Error in field [{post.subject...}] : item ’subject’ is not an existing key in the array. This message can be cancelled using parameter ’noerr’.

TinyButStrong Error in field [{post.message...}] : item ’message’ is not an existing key in the array. This message can be cancelled using parameter ’noerr’.

[!Replix?customfields=`name,subject,message` &makefolder=`1` &captcha=`2` &sortorder=`0` &tplComment=`kommentar_tpl` &folder=`59` &tplForm=`kommentarform_tpl` &pagination=`10`  &customname=`name`!]

−
	<replix createdon="1158740575">
−
	<comment id="449527cb4e3afbdef05d59233c36db1a" createdon="1158740588" uid="" ip="127.0.0.1">
<subject>tester</subject>
<message>ewrer</message>
<name>test</name>
</comment>
</replix>

Yes, the successor will be included in 0.9.5.