Hi Ricardo, > > On 15 Mar 2017, at 12:23 am, Ricardo Parada <rpar...@mac.com> wrote: > >> Have others experienced a problem where a form is submitted and then during >> takeValuesFtomTequest a condition that was false when the page was rendered >> becomes true all of a sudden causing some input elements (textfields, pop-up >> list, etc.) to participate in takeValuesFromRequest even though those >> elements were not on the page when the form was submitted? This causes those >> elements to be set to null. I've ran into such bugs in the past many times. > > I’ve seen the inverse of that manifest in a slightly different way: condition > changes from true to false, and then an action method that was the target of, > say, a WOHyperlink rendered inside the conditional doesn’t fire and the > current page is returned instead. I’m not sure I would characterise it as a > “bug”, so much as just “how it works”. > > > -- > Paul Hoadley > http://logicsquad.net/ > https://www.linkedin.com/company/logic-squad/ >
I’ve also had that kind of thing happen many times. I agree that it is just “how it works”. Using a local variable that is initialized and then not changed will make sure a conditional does not change in the R-R loop. Steve _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
