As useful as ezkeyword datatype is, it has a very limited validation.
This makes it quite risky to let anonymous, or even untrained users
fill object attributes based on this datatype.
eZ Public Keywords datatype provides a set of validation techniques
that can prevent submitting of unwanted or potentially dangerous
data. It makes it possible to define:
- minimum number of comma-separated keywords/phrases (per class
attribute)
- maximum number of comma-separated keywords/phrases (per class
attribute)
- minimum length of one keyword/phrase (per class attribute)
- maximum length of one keyword/phrase (per class attribute)
- all of the above globally (as a security parameter)
- valid charset (per content object attribute language)
- valid default charset
Additionally, it provides detailed validation messaging for user's easier problem
identification.
I believe this might be a step towards making keywords datatype
publicly available. Hope you find it useful, too.
Internally, this datatype extends original ezkeyword datatype (class), which
means that it uses exactly the same database keywords engine. All of
the phrases collected by the attributes of this type should be
available for standard fetching functions and other standard
operations.