Write a patch, this way you can re-patch the files if there is another release. Plus you can upload the patch to the ticket and hope it will get applied :)
2009/5/18 lightflowmark <1...@lightflowinterrupted.com>: > > Hi, > How do you guys handle unfixed bugs in ZF? Suppose you're working on a > project, and some genuine bug in a ZF component prevents it working for your > use-case. It's a fairly simple fix, this issue is on the issue tracker, but > it won't be fixed by Zend until the next version (at the earliest) and you > need it working now. > > How do you work with this? I can only see two options > 1) editing your version of the ZF component, which then breaks when you > upgrade later, or > 2) overriding the offending class with one of your own, with the only change > being your bugfix - typically overriding a whole function (perhaps a > protected or private one) by copy-and-pasting it and changing a couple of > lines. Then going through your whole app and altering every reference to > ZF's broken component with your own. > > If the component is something like Zend_View, which is referenced in dozens > of places by other ZF components, then you can't override it without > overriding the dozens of other ZF components which reference it. > > FWIW, the bugs that are currently causing me headaches (vote now!) are > http://framework.zend.com/issues/browse/ZF-6563 > http://framework.zend.com/issues/browse/ZF-4026 > > > Any help with this appreciated, I'm not really sure how to solve this one. > > Cheers, > Mark > -- > View this message in context: > http://www.nabble.com/Living-with-bugs-in-ZF--tp23602103p23602103.html > Sent from the Zend Framework mailing list archive at Nabble.com. > > -- ---------------------------------------------------------------------- [MuTe] ----------------------------------------------------------------------
