On 15 Feb 2009, at 14:50, Michal Charemza wrote:
>
> On 15 Feb 2009, at 14:16, Craig Fairhurst - youds.com wrote:
>>>> Looking at your global_filters.xml, you will need to add the
>>>> "field_error_messages" parameter, see attached for an example
>>>>
>>> I have tried both with and without this parameter.
>>>
>> I think the important bit is the <parameter name="parent::$
>> {htmlnsPrefix}label"></parameter>
>> I may be wrong, but the "label" bit is what to attach the
>> class="error" too
>
> Although obviously I don't really know what I'm doing, in this case
> I do suspect you're wrong. As in my modified sample app I don't have
> that, and the class="error" is still attached to the input elements,
> and their associated labels.
I found the issue! The setup I have is that I have two actions "Post"
and "PostComments". The "Post" view calls the "PostComments" action
within a slot. It seems that the data that passed to the FPF has gone
through two validation steps:
Validation for "Post" action
Validation for "PostComments" action.
Before, I had validation rules for the data within "PostComments" but
not for "Post". If I just copy/past the rules from PostComments.xml to
Post.xml, everything works as it should. *However*
- Copy/pasting is obviously not a great solution. How can this be
avoided?
- There seems to be an inconsistency. In the PostComments view, the
submitted data is available from the request data holder, even if
there are no validation rules for the data specified in Post.xml.
*However* for the data to be available in the FPF, there must be rules
in Post.xml. Why is this?
Also: sorry if I'm using the wrong terminology for things. Please let
me know if I'm not being clear.
Michal.
_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users
