Re: DOFormBuilder update-freeze Problem
| From: | Justin Patrin | Date: | Fri, 03 Dec 2004 01:34:34 +0000 |
| Subject: | Re: DOFormBuilder update-freeze Problem | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-15980@lists.php.net to get a copy of this message | ||
On Fri, 03 Dec 2004 01:26:47 +0100, Alexander Petri <alex.petri@gmx.de> wrote:
> i will try something like this
>
> ...
> if($form->validate()){
> $form->process(....);
> ....
> header("Location: ".$PHP_SELF."?freeze=1");
> exit();
> }
>
> if(isset($freeze)) $form->freeze();
>
> $form->display();
> ...
>
> thats not very elegant...
> but i guess it will help for the first time...
>
IMHO that's much better than freezing and displaying after the post.
Leaving a POST in the browser history can easily cause problems.
>
>
>
> Justin Patrin wrote:
> > On Thu, 2 Dec 2004 16:44:08 +0100, Alexander Petri <alex.petri@gmx.de> wrote:
> >
> >>i guess i have pointet out the error now...
> >>
> >>in DB/DataObjects/FormBuilder.php
> >>
> >>the array $formValues in Method: &_generateForm
> >>
> >>$formValues = $this->_do->toArray();
> >>
> >>does not contain the crossLink Values
> >>
> >>can someone help me to write a workaround for that.
> >>
> >>Or isnt it the right position for that error?
> >>
> >
> >
> > Actually, since setDefaults doesn't work for checkboxes anyway
> > (grumble, grumble) this isn't the right place to look.
> >
> > In point of fact, the triple link code actually gets the HTML for the
> > checkboxes and doesn't add the elements to the form due to QF's lack
> > of an easy way to add such a table.
> >
> > Looks like the crosslink code also suffers from the same basic problem.
> >
> > Further looking points out that it's not FormBuilder which sets those
> > values. Since the form is processed after it is created, FB doesn't
> > *see* the new posted values. QF sets the previously posted values
> > automatically, but doesn't seem to get the checked checkboxes for some
> > reason...
> >
> >
> > Markus? Shall we add some kind of workaround?
> >
>
--
Justin Patrin