StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5320740
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2011-03-16T03:29:06.157
FavoriteCount
0
LastActivityDate
2011-03-16T03:29:06.157
LastEditDate
LastEditorUserId
0
OwnerUserId
462702
ParentId
5317935
PostTypeId
2
Score
10
ViewCount
0
LastEditorDisplayName
text
Body
Great question, and one which took me a long time to figure out the best way to solve. The CodeIgniter <a href="http://codeigniter.com/user_guide/libraries/form_validation.html">Form Validation library</a> is great, but can only be used with proper views and controllers, so it doesn't work out of the box when you are developing a front end tag. Normally, the preferred way of submitting a front-end form is to register an 'Action' in your upd.addon.php file (I'm guessing you have done this for your <code>submit_form()</code> function). This is then assigned a number, which you can post with the url <code>/index.php?ACT=37</code> or something similar. This is a good system, because it means we know the form submission came from our module. However, with input forms, this is a hindrance, because it means we can't repopulate input fields. You therefore need to configure the input form to post back to the current URL, and wait until the template engine tries to render your tag before handling the form submission. The easiest, and visually ugliest way to achieve this, is to use <code>$this->EE->output->show_user_error(FALSE, array_of_errors)</code>. You can actually use this from either an action, or within your module code. It displays the standard grey EE message page we have all grown to know and hate. With that sort of intro, you probably knew the solution wasn't going to be quite that simple, right? Here's a skeleton of a tag function which implements inline error checking: <pre><code>function my_form() { // load default tag variables $tag_vars = array(); $tag_vars[0] = array( 'first_name' => '', 'error:first_name' => '', 'last_name' => '', 'error:last_name' => '' ); // handle a form submission if ($this->EE->input->post('my_form_hidden') == '1')) { // load POST data into tag $tag_vars[0]['first_name'] = $this->EE->input->post('first_name', TRUE); $tag_vars[0]['last_name'] = $this->EE->input->post('last_name', TRUE); // use CI validation library to check submission $this->EE->load->helper('form'); $this->EE->load->library('form_validation'); $this->EE->form_validation->set_rules('first_name', 'lang:first_name', 'required'); $this->EE->form_validation->set_rules('last_name', 'lang:first_name', 'required'); $valid_form = $this->EE->form_validation->run(); if ($valid_form) { // probably save something to database, then redirect } else { $form_errors = array(); foreach (array('first_name', 'last_name') as $field_name) { $field_error = form_error($field_name); if ($field_error) { $form_errors[] = $field_error; $tag_vars[0]['error:'.$field_name] = $field_error; } } if ($this->EE->TMPL->fetch_param('error_handling') != 'inline') { // show default EE error page return $this->EE->output->show_user_error(FALSE, $form_errors); } } } // parse and output tagdata $out = $this->EE->functions->form_declaration(array( 'action' => $this->EE->functions->fetch_current_uri(), 'hidden_fields' => array('my_form_hidden'))); $out .= $this->EE->TMPL->parse_variables($tagdata, $tag_vars); return $out.'</form>'; } </code></pre> This way, the designer can specify <code>error_handling="inline"</code> in the tag if they want inline errors, otherwise they will just be redirected to the standard error form. If they do request inline error handling, they will simply need to make sure their inputs look like this: <pre><code><input type="text" name="first_name" value="{first_name}" /> {error:first_name} </code></pre> Note the hidden field we submit along with the form, this allows us to ensure we only handle submission of this form, and not any other forms on the page, such as a login form or something. If you have more than one instance of your form on a page (say inside a channel entries loop or something), you will need to implement some trickery to make sure that you only handle the form instance which was submitted, for example by submitting along entry_id as a hidden field too. Glad to get that all documented, hopefully this will be useful to other EE developers too!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to use ExpressionEngine form validation class in module to repopulate form in template?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAdrian Macneil
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to use ExpressionEngine form validation class in module to repopulate form in template?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.