Issue Type: Improvement Created: 2009-04-24T01:00:52.000+0000 Last Updated: 2009-04-27T01:38:36.000+0000 Status: Resolved Fix version(s): - 1.8.0 (30/Apr/09)
Reporter: Jan Sorgalla (jsorgalla) Assignee: Thomas Weidner (thomas) Tags: - Zend_File_Transfer
Related issues: Attachments:
Create method to retreive the actual destination of transferred file after a possible Rename filter is applied.
<pre class="highlight"> $upload = new Zend_File_Transfer_Adapter_Http(); $upload->setDetination('/tmp'); $upload->addFilter('Rename', 'C:\mypics\new\my_unique_filename.ext', 'upload'); $upload->receive(); $filename = $upload->getFileName('upload'); // Does not respect Rename filter and returns the "old" destination /tmp/uploaded_filename.ext // Possible new method $filename = $upload->getActualTransferedFileName('upload'); // Should return C:\mypics\new\my_unique_filename.ext
Posted by Thomas Weidner (thomas) on 2009-04-25T03:52:04.000+0000
Not reproducable in trunk (next major release)
Posted by Jan Sorgalla (jsorgalla) on 2009-04-26T23:33:12.000+0000
It would be nice if you could correctly respond to issues reported. It took me some time to figure out that getFileName() was changed in trunk (after i filed this issue) to now respect Rename filters. So, "Not reproducable" was very misleading here...
Posted by Thomas Weidner (thomas) on 2009-04-27T00:06:18.000+0000
You filled in a issue for trunk without giving a release number. So my intention was that you are using the latest trunk version (next major release).
getFileName has not changed but another issue has been solved this week which has been told over IRC. It could be, based on your reply, that both issues are based on the same reason but as the other issue was based on another method and uses different code I thought that they are also based on different reasons.
I'm sorry if that seems irritating and would ask you next time to give the svn release number you've tested against. This allows me to test against that special release and respect this within the reply.
I will change the solution to respect what you noted.
Posted by Thomas Weidner (thomas) on 2009-04-27T00:08:35.000+0000
Already fixed by another issue within trunk release.
Posted by Jan Sorgalla (jsorgalla) on 2009-04-27T01:38:33.000+0000
I actually used latest trunk version (at time of writing the issue). But yes, i will add the svn release number next time. Thanks a lot for your work, really appreciated.
Have you found an issue?
See the Overview section for more details.