the same has already been discussed in this thread: http://groups.google.com/group/pylons-discuss/browse_thread/thread/b7b2448e97849f99/27a00f067eb25e10?q=greif&rnum=1#27a00f067eb25e10
Alex. On 6/6/06, Ben Bangert <[EMAIL PROTECTED]> wrote: > > On May 8, 2006, at 7:25 AM, askel wrote: > > > Accessing http://127.0.0.1:5000/test/ shows form but selecting > > different component calling options doesn't make any difference. > > index.myt doesn't see call_type from form variable. I suspect, > > controller has to call a template in a different way to let it see post > > variables. Am I missing something that explained in Pylons > > documentation? > > For those variables to make it into your components under an <%args> > block, they need to be explicitly passed in by the controller, ie: > m.subexec('/some/template.myt', arg1=var, arg2=var2) > > In plain Myghty, all arguments go straight to the template. This is why > the example doesn't work under Pylons. If you wanted to automatically > pass all the args in like that, try: > def somefunc(self, ARGS): > m.subexec('/some/template.myt', **ARGS) > > That will relay all the args through so that an <%args> block can catch > them. > > HTH, > Ben > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss -~----------~----~----~----~------~----~------~--~---
