Issue Type: Bug Created: 2009-10-23T11:27:42.000+0000 Last Updated: 2011-07-14T16:32:56.000+0000 Status: Resolved Fix version(s): - 1.10.8 (25/Aug/10)
Reporter: Cristian Bichis (avantis) Assignee: Thomas Weidner (thomas) Tags: - Zend_Form
Related issues: - ZF-11563
I noticed the Zend_Form_Element_File doesn't make use of $helper member and actually is using directly (on render method) the formFile name instead.
I think this is not a good idea, since sometime if we need to use other viewHelper than formFile we need to extend the entire Zend_Form_Element_File class, instead of just setting the $helper with the desired helper name, other than formFile...
Posted by Cristian Bichis (avantis) on 2009-10-23T11:29:27.000+0000
An error occurred in my problem description.
The Zend_Form_Decorator_File is not actually using the helper set on $helper on Zend_Form_Element_File and rather uses directly the helper formFile...
Posted by Cristian Bichis (avantis) on 2009-10-23T11:40:15.000+0000
So, basically to change the helper used instead of formFile we need to extend both Zend_Form_Element_File and Zend_Form_Decorator_File...
Posted by Thomas Weidner (thomas) on 2010-06-12T06:15:39.000+0000
Why would you want to use another helper?
Note that the file element would then no longer work... same applies for the decorator. There were already several issues being written because people did erase the decorator and the file element did not work anymore.
Posted by Cristian Bichis (avantis) on 2010-06-12T06:41:37.000+0000
The purpose if for adding advanced facilities for add/edit of uploaded files.
Let's suppose we have a form for adding/editing a product. I am not talking about advanced upload facilities, as for http://www.swfupload.org/ but for some basic ones into a normal situation.
Case 1: We are a new product. The user is adding one file for upload, but forgets to fill other field.
The current way: The user gets again the add form, with all the valid values filled in, but of course, he lost the uploaded file, he should re-upload again the file...
Normal behavior: the uploaded field has a link to the uploaded file (or a thumbnail of the image, if that's an image). If the user wants to upload a different file then he just pick other file.
Case 2: We are editing a product.
The current way: the user is invited to upload new file without to actually see if there are currently uploaded files and which files
The new way: use is able to see what files are uploaded and to decide if he wants to add more.
Of course, the problem can be extended to be able to "remove" existing uploaded files.
I just tried to how you that if we are limiting the File element to a standard behavior is very difficult for developers to put up some otherwise not quite unusual facilities...
In my case, i had to rework lot of files to get such behavior (File Element, Decorator, aso)...
Posted by Thomas Weidner (thomas) on 2010-06-13T01:49:57.000+0000
Case 1 does not work: Temporary uploaded files are erased by PHP. And you can't set a path on the element itself as you can not set a value on file elements due to HTML/Browser restrictions. So you always MUST upload a file completly.
Same for Case2.
The problem is not the limitation of the file element, the problem is that HTML/Browser does not allow to do this.
When you need a behaviour feel free to propose it.
Generally the file element does not work 100% identical to the other elements due to the previous mentioned restrictions. When we would change this, then we would have much problems we can not solve.
Posted by Cristian Bichis (avantis) on 2010-06-13T01:57:44.000+0000
Case 1: "Temporary uploaded files are erased by PHP. "
Is possibly to save the file on a form derived isValid.
I am not trying to propose a way to do uploads other than imposed by htm/browser. I am trying to say we should keep the File element open to be extended by developers to do more advanced ways to work with files.
Posted by Cristian Bichis (avantis) on 2010-06-13T01:59:21.000+0000
If you think we should not be able to extend the File element easier then you are saying we should actually do raw PHP and forget about using ZF...
Posted by Thomas Weidner (thomas) on 2010-06-13T04:08:04.000+0000
There is no reason to be ridiculous just because someone wants to discuss an issue in detail before coming to an conclusion.
I just want to know a usecase for eliminating the binding between Zend_File and it's helper.
Saving the temporary file and providing it later will as mentioned by you will cause an "attacker exception" from PHP itself.
Posted by Cristian Bichis (avantis) on 2010-06-13T04:29:33.000+0000
The standard way to work with File element (and generally with the way browsers/html are doing this) is simply too annoying to use more than for demo scripts, for learning ZF. Is not ZF fault of course.
But any kind of serious application needs to go beyond this very basic functionality, and i think would be easier for developer to go further based on existing File element by extending his functionality:
Posted by Thomas Weidner (thomas) on 2010-08-09T23:05:23.000+0000
Closing as non issue
*) The file form element provides the helper parameter *) The render method of it is not hardcoded to file but to parent *) The file decorator works identical to errors, fieldset, image and label which were the 4 decorators I used as reference
As the file element and it's decorator works identical to several other element regarding it's call and usage of view and view helpers this issue is closed as non-issue.
When you think that there is a generic problem on Zend_Form itself then please open a new issue. Because in my opinion the file element behaves correct (as all other elements)
Posted by Cristian Bichis (avantis) on 2010-08-11T12:30:50.000+0000
If is like you said that "As the file element and it's decorator works identical to several other element regarding it's call and usage of view and view helpers" so applies for other form elements then is a real problem in many cases and i will file a new issue on JIRA.
Have you found an issue?
See the Overview section for more details.