I'm sure it's not related to SELF:/current_comp in any way. It's only happening on a few pages? Is there something different with how these pages are being invoked?
Try cutting out stuff until you get the simplest possible test case. In the process you will find that cutting something out suddenly makes it work, or you will have a simple test case to send us. ~ John Williams On Thu, 27 Jul 2006, Mark Elrod wrote: > I am not sure if this is related somehow to my SELF: != current_comp > problem but I just noticed that on the few pages where I take > advantage of the <%args> section that any GET or POST variables are > being ignored and only my default value are set. I can print out > $m->request_args and the variables are there but <%args> does not > assign them. If I remove my default values the script errors and says > a required arg is missing. Can someone point me to where I should be > looking for how this mechanism is being foiled? > > Thanks! > > elrod > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Mason-users mailing list > Mason-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mason-users > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
