The attached add-on files may be out of date. Please visit Devot-ee for the latest versions.
This extension makes it possible to add or change CSS attributes of the comment form HTML element.
The problem this extension solves is this: exp:comment:form tag is parsed after all other EE tags which start with “exp”. The result of this is that it is impossible to add or change any of CSS attributes of the HTML form element this tag outputs by wrapping exp:comment:form with some other tag, such as exp://replace or exp://replace_plus. That is, this will not work:
{exp:replace find="comment_form" replace="my_comment_form"}
{exp:comment:form}
{/exp:comment:form}
{/exp:replace}Using Comment Form Tag extension you can add or change any of CSS attributes of the HTML form element exp:comment:entries outputs by adding inside this tag one or more “comment_form_tag” variables. “comment_form_tag” variable supports following parameters:
1) parameter - required. Allows to specify name of CSS atribute of HTML form element.
2) value - required. Allows to specify value of CSS atribute of HTML form element.
EXAMPLE The code
{exp:comment:form entry_id="10" preview="site/comment_preview"}
{comment_form_tag parameter="id" value="comment_form_general"}
{comment_form_tag parameter="class" value="my_form"}
{/exp:comment:form}will output form tag having following CSS attributes:
<form id="comment_form_general" class="my_form">Hi,
This is EE 1.x extension. It uses comment_form_end extension hook.
These are analogous hooks:
edit_wiki_article_form_end forum_submission_form_end publish_form_end weblog_standalone_form_end
It is possible to attach extension’s method to any or to some of these hooks. It seems to me that there is sense to attach extension’s method to weblog_standalone_form_end hook; I don’t find any reasons to attach it to other aforementioned hooks.
How do you think?
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.