``` does not work either (but works on non-file items)

Please give a complete example of your element and form creation/validation. Because errors are rendered and tested in the testbed and displayed in my browser.

I've created a very simple controller action that does only one thing, output a form with an error attached on File element.

Here is /application/controllers/IndexController.php:

<?php
require_once 'Zend/Controller/Action.php';

/**
 * Default controller, used for redirections only
 */
class IndexController extends Zend_Controller_Action
{
    /**
     * Show upload form
     */
    public function indexAction()
    {
        require_once 'Zend/Form.php';
        $form = new Zend_Form();
        $form->setAction('/file/upload')
                 ->setMethod('post');
        $attachment = $form->createElement('file', 'attachment')->setLabel('Upload a file')->addError('An error occured');
        $form->addElement($attachment);
        $this->view->form = $form;
    }
}

Here is /application/views/scripts/index/index.phtml:

<?php echo $this->form->render(); 

Actual Result:

I see... To describe this:

The file element is based on the file transfer adapter. So also the error is thrown from the adapter.

When you create a new error type with addError, this is not supported by files because the adapter would not know where he should attach it. Files themself do not have a error, they are working with validators.

Also, when you add a new errortype where should it be attached ...at the first validator ? What when you delete this validator ? ...at all validators ? Same error would be displayed multiple times ? ...and when this works, only displaying the attached error ? Or also the file errors ?

I would solve this different, at the time you validate / receive the file as shown in several examples.

Btw: renderErrors() works by me, but displays as described previously only file errors.

Changed type from bug to improvement. Will be reviewed internally.

If addError method is not used, it may be interesting for it to throw an exception. Thanks for the explanation anyway.

Integrated with r14233