Login
Username:

Password:

Remember me



Lost Password?

Register now!
Main Menu
Site Info
Webmasters
admin
admin

Who's Online
1 user(s) are online (1 user(s) are browsing XOOPS Docman)

Members: 0
Guests: 1

more...

Chapter 6. Database settings

Talk to your database

Ok, let's see if the information you provided about your database is correct. The first screen you'll see just repeats what you entered in the General Configuration (Chapter 4, General configuration screen. This is it:

You have another chance to take a look at what you entered.

Figure 6.1. You have another chance to take a look at what you entered.

If all data are correct, push the button labeled Next and the wizard will attempt to do two things: first, it'll try to connect to the database server, that is, it's check to see if MySQL is active and running. It'll then try to connect to the database whose name you defined. You've already seen the screen displayed if for some reason the MySQL server is not available, its in Figure 4.2, “If you can't connect to the MySQL server, you'll see this ugly message.”. So, although this is stating something a bit obvious, please be sure you have MySQL active while installing XOOPS.

Assuming your MySQL server is correctly setup, the wizard tries to access the database, in this case the one called test. What happens now? It depends. If you're installing locally, you probably haven't created the database just yet. In that case, you'll be facing a screen with a single red light on:

This is not a real error if you're installing locally. Just go ahead.

Figure 6.2. This is not a real error if you're installing locally. Just go ahead.

XOOPS didn't find a database on the server, for the simple reason there's still no database there. So of course you should attempt to create it. The attempt, by the way, will put to test your data about the database user and password. So click on Next.

Wham! Everything was ok so you now have a blank database installed.

Figure 6.3. Wham! Everything was ok so you now have a blank database installed.

This terse screen just gives you feedback: yes, you now have a blank database called test in your server. So you click again on the omnipresent button labeled Next. This is what you want to see:

You are ready to install the tables that create your XOOPS site.

Figure 6.4. You are ready to install the tables that create your XOOPS site.

If you see any red light, something is wrong. Either your MySQL is not accessible or the user/password combination you entered doesn't have the rights over that specific database. But must probably you'll see this screen with two green lights. This means you have a clear path and are ready to write your tables.

By the way, if you are installing into a remote hosted server, you won't see the bit about creating a table, since you already had done that. The most probable outcome is that you'll jump directly to the screen shown in Figure 6.4, “You are ready to install the tables that create your XOOPS site.”. So don't hesitate and go ahead: click on Next.

A lot happened here. You now have a table-populated database.

Figure 6.5. A lot happened here. You now have a table-populated database.

This screen is very informative, because it gives you a still portrait of the tables that comprise your XOOPS site. Let's see what can we tell about what XOOPS just did.

The first thing to notice is that a blank, brand new XOOPS site has 31 tables defined. I'll attempt a definition of what these tables contain, so you can begin to grasp a bit about XOOPS power. Let's see...

  • xoops_avatar - Holds the identity, path and name of user avatars.

  • xoops_avatar_user_link - Ties an avatar's id with a user's id, so each user “knows” its avatar.

  • xoops_banner - Holds all the information about a specific banner.

  • xoops_bannerclient - Holds all the information about a banner customer.

  • xoops_bannerfinish - Holds all the information about expired banners, with their click count.

  • xoops_block_module_link - Ties a block's id with a module's id, so each block “knows” the module to which it belongs.

  • xoops_xoopscomments - Holds all the information about a comment.

  • xoops_xoopsnotifications - Holds all the information about notifications.

  • xoops_config - Holds XOOPS general configuration variables.

  • xoops_configcategory - Holds the configuration categories.

  • xoops_configoption - Holds configuration options.

  • xoops_groups - Holds the identity of users' groups.

  • xoops_groupspermission - Holds the details of permissions granted to each group of users.

  • xoops_groups_users_link - 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.

  • xoops_image - Holds all the information about an image stored in the system.

  • xoops_imagebody - Holds an image, in case you decide to write images in the database.

  • xoops_imagecategory - Holds the image categories you define in the Image Manager.

  • xoops_imgset - Holds the identity of an image set

  • xoops_imgset_tplset_link - Ties an image set's it with a template set's id, so a template set "knows" what images belong to it.

  • xoops_imgsetimg - Don't know what this is for.

  • xoops_modules - Holds all the information about a module.

  • xoops_newblocks - Holds all the defining attributes of a block.

  • xoops_online - Holds the information about users online.

  • xoops_priv_msgs - Holds all the information about a private message.

  • xoops_ranks - Holds the users ranks defined in the admin area, to qualify user's participation in the site.

  • xoops_session - Holds the information about a session.

  • xoops_smiles - Holds the information about the codes used to display smilies.

  • xoops_tplset - Holds the information about a template set.

  • xoops_tplfile - Holds the metadata of a file that's part of a template set.

  • xoops_tplsource - Holds the data (the source code) of a file that's part of a template set.

  • xoops_users - Holds all the information about a user.

These are all blank tables, ready to be populated. You must know that in a very short time, this list will grow. Why? Because the default installation of XOOPS just sets up for you one module: the System module. From here, you must install whatever modules you want your site to have... but I'm running ahead. We still haven't finished installing XOOPS.

So, let's continue. If you don't see all these green lights, you'd probably start be best starting over, because there won't be tables on your database. Then again, if you're very knowledgeable about MySQL, you may be able to set the tables manually, by importing into your database the script install/sql/mysql.structure.sql. But let's hope you don't need to do this. If you already have the battery of green lights, get set, because now you need to... click on the button labeled Next. So what else is new? Ah, of course. Let's go to Chapter 7, Admin settings

The comments are owned by the author. We aren't responsible for their content.

Author Thread
dalong
Published: 2006/11/16 8:00  Updated: 2006/11/16 8:00
Just popping in
Joined: 2006/11/16
From:
Comments: 2
 Re: xo-002 http://www.apachefriends.org/en/xampp.html
very good!
I like here!

Author Thread
dalong
Published: 2006/11/16 10:13  Updated: 2006/11/16 10:13
Just popping in
Joined: 2006/11/16
From:
Comments: 2
 Re: xo-002 http://www.apachefriends.org/en/xampp.html
thank for your work!

Author Thread
huqilong
Published: 2006/11/20 2:50  Updated: 2006/11/20 2:50
Just popping in
Joined: 2006/11/16
From:
Comments: 3
 Re: xo-002 http://www.apachefriends.org/en/xampp.html
I hava a question ,when I have installed phpeclipse,I can't user the button for the apache in the Eclipse IDE,how shoud I do?

Author Thread
huqilong
Published: 2006/11/20 3:10  Updated: 2006/11/20 3:10
Just popping in
Joined: 2006/11/16
From:
Comments: 3
 Re: xo-002 http://www.apachefriends.org/en/xampp.html
dddd

Author Thread
Mark_1900
Published: 2006/11/18 11:05  Updated: 2006/11/18 11:09
Just popping in
Joined: 2006/11/18
From:
Comments: 2
 Alias Permission Problems
For an Alias I also had to add a Directory tag to the httpd.conf, otherwise I had permission problems accessing the files... <br /> [code] Alias /wiki "C:/Documents and Settings/Me/wiki"<br /> <Directory "C:/Documents and Settings/Me/wiki"><br /> Options Indexes MultiViews<br /> AllowOverride None<br /> Order allow,deny<br /> Allow from all<br /> </Directory><br /> [/code]<br /> Oh and all these editing tags seem broken!!

Author Thread
Mark_1900
Published: 2006/11/18 11:21  Updated: 2006/11/18 11:32
Just popping in
Joined: 2006/11/18
From:
Comments: 2
 Getting the correct php_dbg.dll
I want a debugger. I downloaded the latest XAMPP 1.5.4a and noticed that it comes with PHP 5.1.6 & PHP 4.4.4, and neither are supported. The debugger module only supports a subset of these major versions from 5.1.0 to 5.1.2 and 4.4.0 to 4.4.2 (http://dd.cron.ru/dbg/downloads.php). I think right at the beginning you should specify which versions to download to get a debugger Version "XAMPP 1.5.2" would be fine.

Author Thread
huqilong
Published: 2006/11/30 6:28  Updated: 2006/11/30 6:28
Just popping in
Joined: 2006/11/16
From:
Comments: 3
 Re: xo-002 http://www.apachefriends.org/en/xampp-windows....
I want to know how to use phpeclipse with eclipse detailly!

Author Thread
thierrybo
Published: 2007/2/3 16:19  Updated: 2007/2/3 16:21
Just popping in
Joined: 2007/2/3
From:
Comments: 1
 Re: xo-002 ch02s03.html Workspace Method 2
I do not agree with the suggested method 2: Quote:
For example you have set up XAMPP and your “document root” path is the XAMPP default:
C:Program Filesapachefriendsxampphtdocs
Quote:
,then your appropriate workspace path should be one level less:
C:Program Filesapachefriendsxampp
If htdocs is your document root, then each folder inside IS a new project and you should set workspace directory as Document Root directory. With suggested method, all your web projects are managed with ONE big PHPeclipse project.

Author Thread
dafydd
Published: 2007/4/3 6:01  Updated: 2007/4/3 6:01
Just popping in
Joined: 2007/4/3
From:
Comments: 2
 Re: xo-002 ch01.html
Trying this out on a Mac. J2SE 1.5.0_07-164 installed. 1.5.0_06 is what's available on the download site. However, it would almost certainly be updated with Software Update.

Author Thread
dafydd
Published: 2007/4/6 1:00  Updated: 2007/4/6 1:00
Just popping in
Joined: 2007/4/3
From:
Comments: 2
 Re: xo-002 ch01s04.html
Second question: How do we point the XAMPP start/stop buttons in the Eclipse toobar to where we put XAMPP?

dafydd

Author Thread
dysmas
Published: 2007/8/4 14:18  Updated: 2007/8/4 14:18
Just popping in
Joined: 2007/8/4
From:
Comments: 1
 Debugging standalone PHP applications
Thanks hundred times for all the detailed explanations here !!

And especially for the note which explains why debugging a CLI application does not work in 1.1.8 version and only in 1.1.9. (wrong port, as I guessed, but I have been looking for this information for some hours before coming here). Unfortunately this 1.1.9 CVS version does not work in the last 3.2.0 Eclipse version I just got. Let us hope the stable version is going quickly.

Author Thread
Mercyful
Published: 2007/9/10 14:46  Updated: 2007/9/10 14:46
Just popping in
Joined: 2007/9/10
From:
Comments: 1
 Re: dbg is not working
I want using eclipse3.2 with php-plugin and for debugging i want using dbg.
I'm using xampp 1.6.3a with php 4.4.7. and php_dbg.dll-4.4.x
After step by step installation
http://docs.schuetzengau-freising.de/ ... =xo-002&file=ch01s05.html
the debugger dbg will not work.
When i called phpinfo() there is no section dbg shown.
Who have any ideas?
Thanks a lot!
Regards Mercyful

Author Thread
keryx
Published: 2007/9/26 22:59  Updated: 2007/9/26 22:59
Just popping in
Joined: 2007/9/26
From:
Comments: 1
 Re: xo-002 ch04.html
A section about verrors should be nice. I get the following:


<terminated, exit value: 0>PHP C:\Program\PHP\php.exe : <path>/<fil>.php

I've googled like crazy but to no avail. And yes - it does not stop at breakpoints and "variables" are empty. DBG is working:

if (function_exists ("DebugBreak")) {
DebugBreak ();
echo "debugging started!<br />\n";
}

Outputs "debugging started!" And DBG is reported on phpinfo().

Author Thread
koski
Published: 2007/10/19 3:55  Updated: 2007/10/19 3:55
Just popping in
Joined: 2007/10/19
From:
Comments: 1
 Re: xo-002 ch01s03.html
Hi,

Seems that the mentioned link for cvs:

http://phpeclipse.sourceforge.net/update/cvs

is out of date or wrong.

Author Thread
andybruk
Published: 2007/11/18 1:11  Updated: 2007/11/18 1:11
Just popping in
Joined: 2007/11/18
From:
Comments: 1
 Re: xo-002 index.html
I've been searching for a PHP debugger for ages. This is the only one I can find that works perfectly, thanks very much for providing this documentation.<br /><br />I doubt if I could ever get it to work on Windows, but it works so well with Ubuntu Linux and Eclipse 3.1.<br />
Powered by XOOPS 2.0 © 2001-2005 The XOOPS Project