Bah. Tripped myself up with a client regexp validation that was associated to the upload component, which caused the page init to partially fail. Why is it always the smallest things that take the longest?
Kalle On Wed, Sep 22, 2010 at 8:53 AM, Kalle Korhonen <kalle.o.korho...@gmail.com> wrote: > How odd. I have a conventional non-ajax form with one field that's > using Inge's ZoneUpdater for checking value's uniqueness and > displaying the results in a zone. As soon as I add the Upload > component (the standard, non-ajax one), the zone update breaks saying > "Ajaz Zone <zone> does not have an associated Tapestry.ZoneManager > object". The Upload component doesn't add any complex Javascript or > otherwise do anything special, so I don't quite understand what can > cause it to break. Obviously the upload component changes the form's > enctype to multipart, but could that be the cause for failure and why? > Anyone run into this? > > Kalle > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
