However, curiously, the upgrade worked fine on my local (work) machine, and I'm not aware that I changed any stylesheet to make it work. I just installed it from CPAN and it worked. But something on our server sure doesn't like it. Makes me think about the possibility incompatibilities with certain library versions. Something like that ..
Colin On Fri, 2004-04-02 at 17:36, Michael A Nachbaur wrote: > I ran into something similar a while back due to a PerForm update. I > cannot remember what the version numbers are, so its possible this isn't > your problem, buuuttt... > > When I updated PerForm, I didn't take the updated XSL stylesheet for > rendering the PerForm elements. Some of the code changes relied on > changes in the form field names (for instance, __submitted or something > like that became __submitted_<name>). So, when you submit, the XSP > taglib didn't know what form you were submitting, and subsequently > didn't do anything. > > Try that out and see if it solves anything for you. > > Colin Goodier wrote: > > >Hi, > > > >We recently upgraded to PerForm 1.83 in an attempt to get rid of the bug > >in the 1.7 version whereby the drop-down menus are not re-populated when > >the form is re-submitted when there is an error in the original > >submission. > > > >However, we found that the upgrade caused more problems, in that the > >form appeared not to be submitted at all! So, as the lesser of two evils > >we reverted to the older version, which at least works. > > > >Has anybody else had any problems with the latest version of PerForm? > > > >I was wondering if I could get round it by using JavaScript to validate > >the form, but I see that the 'onSubmit' (or onClick') call is a feature > >of the later versions only, so may be a no-no for us too :-( > > > >Colin Goodier > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
