Ok, maybe I should be specific with my issue. It is a very similar
issue to one I posted previously about (although it is now with
different outer/inner actions, hence I suspect my understanding is
off...)
I have a form that is output in the view of an action, which is itself
called as a slot (and so called 'within', if that's the right word,
another action). In the Error view of the inner action I now have the
following code:
$vm = $this->container->getValidationManager();
$errors = $vm->getErrors();
$this->setAttribute('errors', $errors);
I can manually output the errors in the template, using $t['errors'].
*However* I would prefer to use the FPF. The FPF seems to work in
other forms in the app, but not this one. Somehow the errors are 'in'
the validation manager, but they don't get to the FPF. Any suggestions?
Sorry if I'm being a bit pushy with this issue, but it is slightly
driving me crazy...
Michal.
On 18 Feb 2009, at 07:36, Michal Charemza wrote:
> I'm having trouble getting validation and the Form Population Filter
> (FPF) to work as I expect, when the action that processes the form
> is called as a slot within another action. I wonder if just my
> understanding of what is going on is wrong. I have some general
> questions:
>
> - What is the data 'flow' of input (say, from the actual $_POST
> variable), through validation and into an action (where it ends up
> as the AgaviRequestDataHolder).
>
> - What is the data 'flow' of input through validation and into an
> action called within another action. Is the validation from the
> *outer* action also applied?
>
> - How are these 'flows' different if there is a validation error?
>
> - At which stage does the FPF get its data? At what stage do the
> validation errors get passed to the FPF?
>
> Sorry if I'm being a bit vague with the word 'flow', I'm not sure
> what would be a better word.
>
> Michal.
>
_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users