StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8991456
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-01-24T17:41:03.267
FavoriteCount
0
LastActivityDate
2012-01-24T17:41:03.267
LastEditDate
LastEditorUserId
0
OwnerUserId
892493
ParentId
8991132
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
Here are a couple of thoughts... <ol> <li>Instead of calling isValid on every form element, you can validate your whole form with isValid, and then loop over your elements as you are in your question, but instead use <code>if ($element->hasErrors())</code> to determine if you need to add the error class to the element.</li> <li>You may want to extend from Zend_Form and add a helper method to your new Form class that does this for you. For example, add a method called <code>highlightErrorElements()</code> or something like that and if you have an unsuccessful call to <code>$form->isValid()</code>, you can then simply call <code>$form->highlightErrorElements()</code> which will loop over each form element and see if it has errors and apply the style if necessary.</li> </ol> Example: <pre><code><?php class Application_Form_Base extends Zend_Form { public function __construct() { // this is where i normally set up my decorators for the form and elements // additionally you can register prefix paths for custom validators, decorators, and elements parent::__construct(); // parent::__construct must be called last because it calls $form->init() // and anything after it is not executed } public function highlightErrorElements() { foreach($this->getElements() as $element) { if($element->hasErrors()) { $element->setAttrib('class', 'error'); } } } } </code></pre> Somewhere, in a controller... <pre><code>$form = new Application_Form_Register(); // this extends Application_Form_Base if ($form->isValid($this->getRequest()->getPost())) { // add user etc } else { $form->highlightErrorElements(); // other error logic } $this->view->form = $form; </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POZend_Form_Element: add class if it contains errors
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USdrew010
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POZend_Form_Element: add class if it contains errors
 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
1. This table or related slice is empty.

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.