This article will show you the basics of creating your own fully working Datamanager.
To start with, create your new PHP file to hold your DM code and save it as includes/class_dm_example.php
Now, the first thing we need to do is check that the vB_Datamanger class exists - without that, we can't do much of anything.
At the top of your new PHP file, put:
PHP Code:
if (!class_exists('vB_DataManager'))
{
exit;
}
This will end the script if the vB_Datamanger class doesn't exist.
Now we need to extend the vB_DataManager class to make our own Datamanager.
On the next line down in your PHP file, put:
PHP Code:
class vB_DataManager_Example extends vB_DataManager
{
This tells PHP that we want to create a Class called "vB_DataManager_Example", and that we want to base it on the vB_DataManager class. This means that our new DM class will inherit all of the vB_DataManagers variables and methods (functions) so we don't have to make our own save() method for example
Now we need to give our new Datamanager some fields to update. For example, the User DM would have fields such as "userid", "username", "email", etc. These fields will usually be the same as the columns in your database table.
These fields all go in an array called $validfields. The $validfields array is in the following format:
PHP Code:
'fieldname' => array(type, required?, verify data?, function name to verify data)
The verificatoin options (the last 2) are optional.
With that in mind, lets start adding to our own $validfields array. Our example datamanager will have 4 fields:
'exampleid' - this is an auto increment field from the database which is incremented automaticly.
'userid' - a vBulletin user id
'username' - a vBulletin username
'exampletext' - some random text
First things first, lets create our $validfields array variable.
First we have the field name - in this case 'exampleid'.
Next we have the type - in this case we're saying it will be an Unsigned Int (ie, a number). A list of valid types can be found at the bottom of this post.
Next we specify that it is required, and that it is an auto-increment value with REQ_INCR. Valid options for this field can be found at the bottom of this post.
Next we tell it that we want to verify the data, with VF_METHOD
And finally, we give it the name of a function to verifiy the data with. In this case, we are using the verify_nonzero() function which is a standard function in the vB_DataManager class.
Now we can add our other 3 fields to the $validfields array:
This has added a further 3 fields to the $validfields, and closed the $validfields array
Now, the next step is to tell vBulletin what table to save our data in. Your table should match the $validfields array in terms of layout and column names.
In this case, we'll use a table called "example":
PHP Code:
var $table = 'example';
Now we have to give vBulletin a temporary array that it uses to store the data we give it when it's saving to out database table that we specified above. It doesn't really matter what this is called, but for convention, try to stick with the name of your DM class
PHP Code:
var $example = array();
The final step in our very basic Datamanager is to create our Class Initator method. This is a function that is run automaticly when our Example Datamanager is created using datamanager_init().
PHP Code:
function vB_DataManager_Example(&$registry, $errtype = ERRTYPE_STANDARD)
{
parent::vB_DataManager($registry, $errtype);
}
The name of this functoin should be exactly the same as your class name. So in this case, we've called it "vB_DataManager_Example".
You don't need to worry about the rest of the code, and if you understand OOP, you'll know what it means
Now, all we've got left to do is add our closing bracket for our class, and we're done:
PHP Code:
}
You can now create your new Datamanager as you would any standard Datamanager by using the datamanager_init() function
That's the gist of it anyway, take a look at some of the existing Datamanagers for more advanced options such as Bitfields, custom verify methods, etc.
Valid field types:
TYPE_NOCLEAN - Any value - it won't be checked/cleaned
TYPE_INT - An signed integer
TYPE_UINT - An un-signed integer
TYPE_NUM - A number
TYPE_UNUM - An un-signed number
TYPE_UNIXTIME - A unix timestamp (time())
TYPE_STR - A string
TYPE_NOTRIM - A string that won't have trim() run on it
TYPE_NOHTML - A string that will have the HTML made-safe
TYPE_FILE - A file upload (ie, $_FILES)
TYPE_BOOL - A bool (true or false)
You can also pass Arrays of these items. For example to pass an array of INT's, use TYPE_ARRAY_INT. To pass an array of Strings, use TYPE_ARRAY_STR
Valid Requirement Options:
(The following is taken directly from vBulletin's DataManager documentation)
Quote:
REQ_YES - the field is required
REQ_NO - the field is not required
REQ_AUTO - the field can be automatically generated. The does not have any effect on code execution at this time. This is appropriate for things like post times that can be reasonably guessed before inserting the new data. (You will still need to write code to generate the appropriate value!)
REQ_INCR - this field is an AUTO_INCREMENT field in the database, and thus will be automatically generated upon insertion.
-------------------------------------------------
Good luck using your new found knowledge of the vBulletin Input Cleaner class, and remember: If you get stuck, just ask! Knowledge sharing is what vBulletin.org is all about!
(Note: If you want to reproduce this article anywhere, I have no objections, but I do request that you give me credit for writing it, and a PM letting me know would be appreciated )
06-21-2006, 10:00 PM
06-22-2006, 06:56 PM
