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 4. General configuration

Over the first hurdle

The time has come to start configuring our soon-to-exist XOOPS site. Since you already have your folder permissions correct, it's time to give the wizard information about you, beginning with the user with rights over the database and then following with some general information. This is the screen you see now:

In this screen you'll capture the information to access your database.

Figure 4.1. In this screen you'll capture the information to access your database.

The first selector is for the moment a reminder that XOOPS looks into the future, as now there's only support for MySQL databases. So you don't choose at all. If you don't see the mysql option, then something weird is happening. I'd advise you to re-upload you the full package before attempting to do anything else. You should see there the option even if you have no power over it. Ok?

Next comes the database host name, that is, the name of the host of the MySQL database server. It already reads localhost, and chances are that's all you'll ever need. Leave it as it is.

What happens if you write here something different? The wizard will let you continue your installation, but some steps ahead you'll find yourself stopped with the following screen:

If you can't connect to the MySQL server, you'll see this ugly message.

Figure 4.2. If you can't connect to the MySQL server, you'll see this ugly message.

Now jump to the database user name. Remember what you read back in the Introduction part? Yes: it's time to use that knowledge. If you're installing locally, you probably are using the user called root, so that would be the name to write in this field. If you're a more experienced MySQL user, maybe you have different users with different access levels. If that's the case, fill the blank with the name of the user you created to handle your XOOPS database. If you're installing in a remote hosted server, you most surely had to create the database before the installation, so you already got a user name. Put in this field that name.

Next comes the password that user will employ to access the XOOPS tables. Again, if you're installing locally, you know the password you use to access MySQL, and if you're installing in a remote server, you also have the password you input when defining the database. This is the place to write it.

In the following field you define the name of your XOOPS database. Use a name that makes sense to you, more so if you install locally and have a lot of sites running together. You might want to try short names, though, because XOOPS will prefix each name with the string contained in the next field, "Table Prefix". Of course you can change the prefix used in your tables, but be sure to remember it afterwards. The recommended option is to leave it as it is. Although the field says xoops, actually the prefix added to every table is xoops_, with an underscore at the end.

Next comes a Yes/No question about using persistent connections in your MySQL database. The default option is No, and there's reasons for that. I won't detail more here, but if you want a more lucid explanation, there's a very good one here: "MySQL Newsletter Using persistent connections with MySQL". My advice? Leave it at No.

Then come two ways of referring to your soon-to-be XOOPS site: the physical path, that is, the folder structure pointing to the directory where you installed everything, and the virtual path, that is, the URL you'll use to access your site. As you can see in the screenshot, taken from a WAMP environment, the physical path is c:/wampp1/htdocs/test, which means the software was installed in a directory called test. In a UNIX environment, this usually amounts to the document root, which, for a typical installation, reads something like /home/yoursite/public_html. Be sure to write the path without trailing slash, so you can reach your destinations

If you write the wrong path to your XOOPS site, the wizard will be smart enough to tell something is amiss. This is what you'll eventually see, and you can readily see there's a typo in the name written in the path field: instead of ending with test it ends with tess:

Beep! You've misspelled the path to your XOOPS installation. You better go back and correct it

Figure 4.3. Beep! You've misspelled the path to your XOOPS installation. You better go back and correct it

If you proceed without correcting stuff, you might end up seeing another strange screen:

You went a bit too far. Now you need to restart the installation.

Figure 4.4. You went a bit too far. Now you need to restart the installation.

In this screen you see a message indicating you already have the XOOPS tables written. What happened here? You went ahead with some mistake, created the tables and then restarted the process in the wizard, when the tables were already set. If you ever get to this point, you'll have to literally start over. That means using your database tool of choice (probably MySQLadmin) to drop the tables and start all over. See why it's important to have always green lights during your installation?

Anyway. Next comes the URL and that should be very easy to fill. If you're installing locally and copied the XOOPS software to the folder xoops, the URL will be http://localhost/xoops. See? No trailing slash. If you add a slash at the end, your paths will lead nowhere and you'll ruin your installation, so no trailing slash. Ok?

Very well. Now you've filled all the fields and are ready to continue. What to do? Just press the button labeled Next. This will take you to a simple confirmation screen that'll repeat the values you entered so you have a chance to correct them before committing them. This is the confirmation screen you'll see:

This is just to make sure everything is right. If it isn't click on Back and correct things.

Figure 4.5. This is just to make sure everything is right. If it isn't click on Back and correct things.

Once you read carefully the values you entered, click again on the button Next. This action will show you an informational screen that looks like this:

The data you entered have just been saved. All systems are Go!

Figure 4.6. The data you entered have just been saved. All systems are Go!

Let's pause a bit here to see what happened. First, the wizard took the file mainfile.dist.php and copied it over mainfile.php. What for? To have a correctly structures configuration file. If you take a look at mainfile.dist.php, you'll see it contains a lot of variable assignments, though the values are generic ones. Now the file is ready for XOOPS to write the actual values, taken from... you guessed it: from the page you just filled with values.

  • The value you entered in XOOPS Physical Path is assigned to the variable XOOPS_ROOT_PATH.

  • The value you entered in XOOPS Virtual Path (URL) is assigned to the variable XOOPS_URL.

  • The value you, er, entered in Database is assigned to the variable XOOPS_DB_TYPE.

  • The value you entered (or left) in Table Prefix is assigned to the variable XOOPS_DB_PREFIX.

  • The value you entered in Database Hostname is assigned to the variable XOOPS_DB_HOST.

  • The value you entered in Database Username is assigned to the variable XOOPS_DB_USER.

  • The value you entered in Database Password is assigned to the variable XOOPS_DB_PASS.

  • The value you entered in Database Name is assigned to the variable XOOPS_DB_NAME.

  • The value you chose in Use persistent connection? (where Yes = 1 and No = 0) is assigned to the variable XOOPS_DB_PCONNECT.

  • The wizard assigned, arbitrarily, the value 1 to indicate the users group called by the variable XOOPS_GROUP_ADMIN (webmasters).

  • The wizard assigned, arbitrarily, the value 2 to indicate the users group called by the variable XOOPS_GROUP_USERS (registered users).

  • The wizard assigned, arbitrarily, the value 3 to indicate the users group called by the variable XOOPS_GROUP_ANONYMOUS (anonymous users).

And all these values or assignments were written to the file mainfile.php, as you'll be able to see when you finish the installation. as you can notice, these aren't peanuts: these values define the access to your database and the paths used to access your site. Fail in this and you won't find things where they should be. Do this correctly and XOOPS will manage things for you easily.

If all you see is a nice battery of green lights, you're ready to continue by clicking on the button named Next. And to continue with this manual, let's go to Chapter 5, Path and URL.

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