Re: tal:on-error should be removed
ajung <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <[email protected]> |
It should not be used but you can not remove a feature that has been out for a decade. -aj Marc W. Mengel-2 wrote > Michel Pelletier wrote: >> as the guide says: >> >> http://plone.org/development/info/development-guidelines >> >> it should not be used upon pain of death. Currently if a portlet raises >> an error it gets totally swallowed (and yes, logged). Regardless we'd >> like to remove this in the goldegg-phase-one branch and then, >> eventually, in 2.2. Any objections? > > Yes! Sure, you shouldn't put it in production code, but it's a great > way to chase down protection errors in page templates -- you partition > the page with > > <div tal:on-error="string: top half"> > ... > > </div> > > <div tal:on-error="string: bottom half"> > ... > > </div> > and a few rounds of binary search finds you your problem... > > Marc > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Plone-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/plone-developers -- View this message in context: http://plone.293351.n2.nabble.com/Re-tal-on-error-should-be-removed-tp340304p7570189.html Sent from the Core Developers mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk