Subversion Repositories php_users

Rev

Rev 10 | Rev 16 | Go to most recent revision | Show entire file | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed

Rev 10 Rev 11
Line 121... Line 121...
121
                     // will be displayed on a hover in HTML5 (ie, title=)
121
                     // will be displayed on a hover in HTML5 (ie, title=)
122
                     'instructions' => 'Enter your e-mail address (WARNING, not verified)',
122
                     'instructions' => 'Enter your e-mail address (WARNING, not verified)',
123
                     // this is entered in an empty box, ie placeholder=
123
                     // this is entered in an empty box, ie placeholder=
124
                     'hint'     => 'E-Mail Address',
124
                     'hint'     => 'E-Mail Address',
125
                     // a regex to run it against to verify it is ok
125
                     // a regex to run it against to verify it is ok
126
                     'filter'   => '/[-_a-z0-9.]+@[_a-z0-9]\.[a-z0-9]/i',
126
                     'filter'   => '/^[-_a-z0-9.]+@[_a-z0-9]+\.[a-z0-9]+$/i',
127
                     
127
                     
128
                     // == for Data Source ==
128
                     // == for Data Source ==
129
                     'dbColumn'  =>  'email',
129
                     'dbColumn'  =>  'email',
130
                     // actual mySQL column type
130
                     // actual mySQL column type
131
                     'type'      => 'varchar(64)',
131
                     'type'      => 'varchar(64)',
Line 196... Line 196...
196
 
196
 
197
== restrict ==
197
== restrict ==
198
If set to true, will not be displayed when a user is editing their own record (so, not updateable by a user). Examples would be admin and enabled, which would not be something a user should change themselves. If an admin is editing a different user, these fields are available.
198
If set to true, will not be displayed when a user is editing their own record (so, not updateable by a user). Examples would be admin and enabled, which would not be something a user should change themselves. If an admin is editing a different user, these fields are available.
199
 
199
 
200
== filter ==
200
== filter ==
201
If set, this is assumed to be a regular express. The result of the input is checked against the regex. If it does not match the regex, the update is declined and an error message displayed. By default, the username can only be alpha-numeric and an underscore, so the regex '/[a-zA-Z0-9_]/' is set as the filter. If a user puts a period in their password, it will be rejected. Validity of the regex is not checked.
201
If set, this is assumed to be a regular express. The result of the input is checked against the regex. If it does not match the regex, the update is declined and an error message displayed. By default, the username can only be alpha-numeric and an underscore, so the regex '/^[a-zA-Z0-9_]+$/' is set as the filter. If a user puts a period in their password, it will be rejected. Validity of the regex is not checked.
202
 
202
 
203
== size ==
203
== size ==
204
For database creation, if set, will create a column (like varchar) with this size, ie size='128' in a varchar field will result in varchar(128)
204
For database creation, if set, will create a column (like varchar) with this size, ie size='128' in a varchar field will result in varchar(128)
205
 
205
 
206
== required ==
206
== required ==