Hi, this problem is changed in the current Embperl CVS which will be released as 2.0b9 during the next days. There will be no changes for EMbperl 1.3.x
Gerald -------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh IT-Securitylösungen * dynamische Webapplikationen * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 939-122 WWW: http://www.ecos.de/ Fax: +49 6133 939-333 -------------------------------------------------------------- | | ECOS BB-5000 Firewall- und IT-Security Appliance: www.bb-5000.info | +------------------------------------------------------------- ----- Original Message ----- From: "Tom Briles" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 23, 2003 10:40 PM Subject: RE: SELECTs not appearing in %idat > Hi Again - > > Turns out the problem is not as simple as I thought (duh...). > > The problem occurs when (assume p1 submits to p2, and both use [$ hidden > $]): > > 1) I fill out the form on p1 and submit > 2) p2 has a select which dynamically (via javascript) deletes the > default option, and adds a new one > 3) I go back to p1 (the select has now become a hidden on p1), then > submit again > 4) The option for the p2 select (passed via a hidden on p1) does not > exist (it was created dynamically the first time I was on p1) > 5) Because of 4, the select does not get put into %idat > 6) There is now a select and a hidden on p2 with the same name > > The way I plan to work around this is to add [- $idat{select_name} = 1 > -] on p2 (since I don't care about the values in %idat). > > But it seems there must be a better way. > > Thanks again, > Tom > > > -----Original Message----- > > From: Tom Briles [mailto:[EMAIL PROTECTED] > > Sent: Friday, May 23, 2003 2:18 PM > > To: '[EMAIL PROTECTED]' > > Subject: SELECTs not appearing in %idat > > > > > > Hello - > > > > I am unable to get SELECT inputs to appear in %idat. This > > causes problems with wizards, [$ hidden $], and going back > > then forward. > > > > I am using 1.3.4 - is this fixed in a later version? I found > > references to this bug, but it was fixed in 0.26 (in June 1998). > > > > Any suggestions? I can send sample code if necessary. > > > > Thanks, > > Tom > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
