![](https://secure.gravatar.com/avatar/fa0d5afe9854289a5c4724e724eb74c3.jpg?s=120&d=mm&r=g)
It is possible. The problem is probably elsewhere, perhaps one of the methods is misbehaving or does not exist. It can often be hard to tell from the traceback because almost everything in nevow is deferred, so the problem is not manifest until long after it was encountered. On Mon, Aug 02, 2004 at 10:36:40AM -0700, Jeff Bowden wrote:
Should it be possible to nest nevow:data declarations in a template? E.g.
<html nevow:data="order" nevow:render="order"> <head><title>Order <nevow:slot name="order_number"/></title></head> <body> <h1>Order <nevow:slot name="order_number"/></h1> <ul nevow:data="order_items" nevow:render="sequence"> <li nevow:pattern="item" nevow:render="mapping"> ... slots and stuff </li> </ul> </body>
When I do this I get a big long stack trace rooted in nevow/accessors.py. It works fine if I remove the outer nevow:data="order" (and dummy up a static fillSlots call for "order_number" in render_order). It also works if I remove the inner section.
I can work around the problem by putting the nevow:data="order" declaration in multiple places but it would be handy if I didn't have to. Is this a bug or is it by design?