[Seaside] [BUG] [2.6a2-avi.66] #request doesn't work anymore

Tony Garnock-Jones tonyg at lshift.net
Tue Jan 3 12:18:47 CET 2006

Avi Bryant wrote:
> No, it's fine to send #request: from a callback, just not directly from
> #renderContentOn:.

Perhaps this is a situation where a dynamic context check could provide
a more perspicuous error message?

I've just implemented such a check - does this look like a reasonable
way to approach the problem?


Perhaps a better error message is needed - maybe something like "You
can't use #call: from within a component's rendering code. See FAQ entry


More information about the Seaside mailing list