[pLog-svn] r6443 - plog/branches/lifetype-1.2/templates/admin

[Jon Daley]

On Mon, 5 May 2008, Reto Hugi wrote:
> On 05/05/2008 09:02 PM, Jon Daley wrote:
>> On Mon, 5 May 2008, reto at devel.lifetype.net wrote:
>>> It's not obvious in the action classes that, if some validators fail and
>>> the error view outputs data from the request that data never get's
>>> filtered.
>>
>>  	Is this because we register the validator, but then later go
>> straight to the _request object?
>
> well, yes. But that would be easy. Simply filter the requests
> appropriately in the action classes. The tricky part immo is, that if
> the validation fails, we go directly to the view which "gets" the
> request data through the properties class automagically.
 	Ah, right. because the view doesn't get passed the data from the 
action...

>>  I guess validate *all* inputs, save them
>> to the local variables, and then print the error.
> I'm not sure, I'm fully understanding this. Validation does not touch
> the data, it just tells true or false. Filters modify data. So, do you
> mean "filter *all* inputs"?

 	Yes, I guess that is what I mean.  When I write php forms, I write 
them like the attached.

I guess you could say the "break;" statement is where I drop out to the 
view, and the $password variable goes out of scope, so I can't display it 
even if I tried when it doesn't validate properly.