Verbose Validation Edition
Sponsored by Child Share and AFS Espania
Profile 1.65 is a version of Profile module for XOOPS that allows for a verbose registration to be done and comments on User profiles.
This has a field for validation that allows for Text Match, RegEx or SQL Validation to be used to prevent people registering with your website without having validation data of sometype such as an existing email address or an invite code or some regular expression statement.
Featuring still Multiple Fields, 2 Types of validation – one which uses JSON; the other that uses the Field $_POST validation method.
Simply upgrade your existing XOOPS 2.4 or 2.5 to XOOPS Profile 1.65 to experience the difference. We can really recommend XinCodes 1.02 for a user based invitation to be done.
I have amended the changelog and added the full featured system for verbose validation of a registration form. And you can have multiple stages of validation, on per step. This means our clients will have the option to have a closed system either through email or other system of referrer.
This is now bug free and fully featured in the 1.6x series of profile minor version number. It is ready to be distributed with XOOPS 2.5.1 and any future versions of 2.4.6
In this version you will have to select the rules you want to be used on a validation field unlike the earlier version which ran all matches, this is so you can have multiple stages of registration validation.
There are 3 types of validation these are explained below and will need to be formulated into a technical brief:
Any preg_match clause for regex will validate the field if this is specified as on of the fields validations.
Any binary match of the string specified here will validate
SQL Record Count
A Select statement that returns a record count only, if the count is over one then it validates. There is some scripting with the sql for example [value] will insert the text field value of the validation field, and/or you can include other fields in the form for example the one for username would be [uname] and you can have multiple of options like [uname|password] which would insert the first occurring field with value of either username or password.
An example SQL script is this one for check if the client knows an existing email address:
SELECT COUNT(*) FROM `prefix_users` where `email` LIKE '[value]' AND `level` > 0
Just say for example you have a list of usernames in the table `prefix_badusernames` and you wanted to check email and username you could on step one of registration do the following:
SELECT COUNT(*) FROM `prefix_users` a, ` prefix_badusernames ` b, where `a`.`email` LIKE '[value]' AND '[uname]' NOT LIKE `b`.`uname`
Download: xoops2.5_profile_1.65.zip – 113 Kb