Using php build-in validation

[Alexander Obuhovich]

There is nice filter_var function (http://php.net/manual/en/function.filter-var.php), that can be used to do user input validation/sanitize.

For example these validating are already there and there is no need to do them manually each time:

• IP address
• url
• e-mail
• regexp

To benefit from these filters I'm proposing to add 2 optional options to field definition:

• filter_type - contant, that represents build-in filter
• filter_options - extra options (if any), that used filter type accepts

And maybe we need to move regexp validation to later stage (when whole validation routing takes place).

I know I talked about this before, but don't remember was there any progress in doing that or not.

--
Best Regards,

http://www.in-portal.com
http://www.alex-time.com

[Phil]

would these options would be accessible from admin/tpl?

Envoyé avec Sparrow

[Alexander Obuhovich]

Nope. Only from PHP, like current field validation options.

[Phil]

ok.

Envoyé avec Sparrow

[Dmitry A.]

Hi Alex,

I like the idea of what you are proposing here.

Would please also search and find that older discussion about "moving regexp validation to later stage"?

DA

[Alexander Obuhovich]

This is it: https://groups.google.com/d/topic/in-portal-bugs/uWeBloFOzio/discussion

Interesting fact, that in corresponding task in that discussion we made false assumptions about why we shouldn't fix that :)

[Dmitry A.]

Okay so what's next step here, task in 5.3.0?

Alex, would you please create one

PS. I have also noticed that there is more than just validation types - it also can sanitize - http://php.net/manual/en/filter.filters.php

DA

[Alexander Obuhovich]

I know that, but most of sanitization is about removing not allowed symbols. Right now functions is_numeric and preg_match, that we're using  provide pretty good protection against that kind of stuff.

[Dmitry A.]

Thanks for your explanation Alex.

Please move forward with creating new task than.

Cheers!

DA