Zend Framework – file input labels are not translated
I hade some time over and updated one of my own projects to Zend Framework 1.8.1. Apart from a change in the auto loader API everything went smooth. But I was a bit annoyed to find out that a simple translation bug still was unfixed. As my project is going live soon I need that bit fixed.
The bug is known and open so I didn’t need to report it. I voted for the issue to be fixed, waited two minutes and still no fix… I thought that was how open source projects worked 
Seriously though, I fixed the issue locally and added what I think should be a correct fix in the comments. (Even though I think it is weird that the transfer adapter should even have the remotest connection to translation logic.)
http://framework.zend.com/issues/browse/ZF-6647
Looking at the statistics for Zend Framework issues I think it is time to step back and slow down on implementing new features. The diff between new issues and resolved issues is constantly getting bigger and bigger while the average time to fix an issue is getting longer and longer. This is natural as the project constantly have grown since it’s birth. But as I like working with ZF I’d hate to see it become a big and unruly behemoth that adds more problems than solutions.
If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.
I thought the some days ago. ZF is awsome with so much features and with 1.8 and Zend_Application there were some realy great additions. But now there should be a cleanup — fixing Bugs and some logical “errors” and documentation also needs improvements and updating.
I agree completely, of course the ZF is great but they do spend much more time adding then fixing.
On the top of my head:
- The 2 or 3 years it took to fix the email subjects for non-english encoding
- The unbelievably slow Zend_Date
Funny you say that. This week, the Zend team started a bughunt week, with the intention to solve a lot of (voted) issues.
Another thing you shouldn’t forget is that there’s backwards compatibility that needs to be thought of. A lot of issues demand the api to be changed, and are therefore postponed to ZF2.0 . Hence these issues are left open (unresolved) until folks start to focus on 2.0.