With all of the information added, the Installation Wizard is ready to write all the information to the mainfile.php and the secure.php file. If the information provided about the database was correct, the result should be similar to Figure 11.
Figure 11: You have another chance to take a look at what you entered If all data is correct, push the [Next] button and the Installation Wizard will attempt to connect to the database server to confirm the MySQL database is active and running and then will try to connect to the database specified.
If the MySQL server is setup correctly, the Installation Wizard will try to access the database, in this case the one called “xoops250final”. If it accessed the database successfully, the required tables for XOOPS.
Figure 12: Database table creation list
Screen 8/14 (Figure 12) presents all of the database tables that support the System Module of a new XOOPS site.
A new XOOPS site creates 32 tables. Following is a list of the tables and a brief description of their function:
Holds the identity, path and name of user avatars.
Ties an avatar's id with a user's id, so each user “knows” its avatar.
Holds all the information about a specific banner.
Holds all the information about a banner customer.
Holds all the information about expired banners, with their click count.
Ties a block's id with a module's id, so each block “knows” the module to which it belongs.
holds value for cache model.
Holds XOOPS general configuration variables.
Holds the configuration categories.
Holds configuration options.
Holds the details of permissions granted to each group of users.
Holds the identity of users' groups.
Ties a user's id with a group's id, so each group "knows" its users, or each user "knows" to which group it belongs.
Holds all the information about an image stored in the system.
Holds an image, in case you decide to write images in the database.
Holds the image categories you define in the Image Manager.
Holds the identity of an image set.
Ties an image set's it with a template set's id, so a template set "knows" what images belong to it.
Holds all the information about a module.
Holds all the defining attributes of a block.
Holds the information about users online.
Holds all the information about a private message.
Holds the users ranks defined in the admin area, to qualify user's participation in the site.
Holds the information about a session.
Holds the information about the codes used to display smilies.
Holds the metadata of a file that's part of a template set.
Holds the information about a template set.
Holds the data (the source code) of a file that's part of a template set.
Holds all the information about a user.
Holds all the information about a comment.
Holds all the information about notifications.
All tables are created blank, ready to be populated.
The list of tables will grow with each module that is added to the site. As noted earlier, the tables listed above are for the System Module only.