Should i use zend form

You could even use a loop that grabs the appropriate subform by key, or even an element by a key. I removed the default decorators so I could have complete control of printing within each element. Sean McSomething's first advice is the way to go for me.

This way, you won't have to worry about the order in which you defined your decorators. You just need them to be there, and you won't have to add those pesky, unintuitive HtmlTag decorators. I made a blog post about this. I'm not sure if Zend already has that feature but, a quick solution would be to extend the class , make it accept a html template. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Zend Form: How do I make it bend to my will? Ask Question. Asked 12 years, 9 months ago. Active 8 years, 9 months ago. Viewed 20k times. What happened to that egg? Add a comment. Active Oldest Votes. Darcy Hastings Darcy Hastings. This is a less than ideal solution. You lose all the functionality of the view helpers - i. You would be much better off to simply render each form element individually in the view from the form object.

Community Bot 1 1 1 silver badge. The ViewScript and ViewHelper decorators give you lots of power. How do you then get the validation messages back into your page if the input isn't valid? You can also use flashMessenger to handle error messages. I used it in the past. So I went about the following process: I had to create a customer view helper for each field type that I wanted to apply the "error" class to.

In it, I overrode the formXXX method, and add a check to see if the element had an error. Additionally, I added a setElement method that the decorator could call to set an instance of the element so my helper could check for errors.

In it, I accessed the view and instantiated the helper for the form element type and checked for the existence of the setElement method I created in my view helper, setting it if it existed. By doing this, I could extend some form element types and not others without busting the entire script.

I was looking at your answer for a solution for the element error class problem, but then afterwards realized it could also simply be done with a rather simple decorator. I made a decorator that should be added before the ViewHelper decorator. It calls getElement , checks hasErrors on it, and then, if necessary adds a class to it with setAttrib 'class', 'error'. But then of course checking for previous existing classes also.

Barrett Conrad Barrett Conrad 1, 14 14 silver badges 14 14 bronze badges. This seems to be a very common complaint with Zend Forms. Evan Evan A small number of specialized elements are provided for accomplishing application-centric tasks.

A Factory is provided to facilitate creation of elements, fieldsets, forms, and the related input filter. The default Form implementation is backed by a factory to facilitate extension and ease the process of form creation.

The code related to forms can often spread between a variety of concerns: a form definition, an input filter definition, a domain model class, and one or more hydrator implementations. As such, finding the various bits of code and how they relate can become tedious.

To simplify the situation, you can also annotate your domain model class, detailing the various input filter definitions, attributes, and hydrators that should all be used together. A Factory is provided to facilitate creation of elements, fieldsets, forms, and the related input filter. At the bare minimum, each element or fieldset requires a name. You will also typically provide some attributes to hint to the view layer how it might render the item.

Set options for an element. This element automatically adds a type attribute of value button. This element adds an InArray validator to its input filter specification in order to validate on the server if the checkbox contains either the checked value or the unchecked value.

This element automatically adds a "type" attribute of value "checkbox". When creating a checkbox element, setting an attribute of checked will result in the checkbox always being checked regardless of any data object which might subsequently be bound to the form.

The correct way to set the default value of a checkbox is to set the value attribute as for any other element. Set options for an element of type Checkbox. If set to true which is default , the view helper will generate a hidden element that contains the unchecked value. Therefore, when using custom unchecked value, this option have to be set to true. Set the value to use when the checkbox is unchecked. For more information about Collection, please refer to the Form Collections tutorial.

Set options for an element of type Collection. When the Collection element will be validated, the input filter will be retrieved from this target element and be used to validate each element in the collection.

If allowAdd is set to true which is the default , new elements added dynamically in the form using JavaScript, for instance will also be validated and retrieved. If allowRemove is set to true which is the default , new elements added dynamically in the form using JavaScript, for instance will be allowed to be removed. This non-semantic span element contains a single data-template HTML5 attribute whose value is the whole HTML to copy to create a new element in the form.

The template is indexed using the templatePlaceholder value. Protection is achieved by adding a hash element to a form and verifying it when the form is submitted. This element automatically adds a "type" attribute of value "hidden". Here is an example using the array notation:. This element automatically adds a "type" attribute of value "file". This element automatically adds a "type" attribute of value "image".

This element creates two select elements, where the first one is populated with months and the second is populated with years. By default, it sets years in the past for the year element, starting with the current year. Otherwise, the value should be an associative array with the month key for the month value, and with the year key for the year value.

This element adds an InArray validator to its input filter specification in order to validate on the server if the checkbox contains values from the multiple checkboxes. This element automatically adds a "type" attribute of value "checkbox" for every checkboxes. In order to set attributes or customize the option elements, an array can be used instead of a string. The following keys are supported:.