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 2. Introduction

It's time to begin

Although the title of this document is XOOPS Installation Guide, the truth is that for the moment the document is just a look at how the XOOPS Installation Wizard takes your through the steps necessary to first install your XOOPS site. This means in particular a couple of things:

  • For the moment it doesn't address the needs of people upgrading their XOOPS installation.

  • It assumes you already have a working environment, that is either LAMP or WAMP.

To compensate for this, I promise this is not your average sequential installation document. Rather, it attempts to guide you through the installation while at the same time giving you some useful pointers about how XOOPS works. So, you'll probably will be able to install your XOOPS site and certainly will end up knowing more than if you just fill in the blanks and click on the Next buttons.

So, if these points haven't changed your mind, that is, if you're still firm on your decision of going ahead no matter what, well, you've been warned.

Still here? Well, that means you want to install a XOOPS site, this is a first installation and you already have a working environment. That is, you already have a place to run together the web server Apache, the database manager MySQL and the scripting language PHP, either on a Linux or a Windows platform, either on your local machine or on a hosted remote server. You have all this and you also have an archive downloaded from the XOOPS site.

As of this writing, the XOOPS version of choice is 2.0.6, and you have two download options. You got the archive as a TAR file (1,013 kb, quite better compression) or as ZIP file (1,602 kb), so the first thing to do is to uncompress the archive in some local directory. What will you get?

You get a directory called xoops-2.0.6 that has three subdirectories:

  • docs, a place where you can read the change log, the GNU/GPL license, a credits file and a HTML install document.

  • extras, where you have an option to display your login form in a pop up, as well as another version of the x2t theme. Why this second version? Because here it includes the whole template set, not just the theme files. It even includes a few extra goodies, such as a template to display your news in a two column format;

  • html, which contains all the code of your XOOPS site.

So, in order to begin your installation, you have to copy the contents of the full html directory to the root directory of your environment. What was that again? You need to copy the contents of the full html directory to the root directory of your environment. Oh, you'd rather have a little explanation about this. Well, here it goes.

If you're installing this to a local machine, this means copying the directory to the directory where your web server will look for files. For instance, my testing environment is a package I got from the Apache friends, called WAMPP1. In many of these packages, the web root is a directory called htdocs, so the first step is to copy the entire html folder so that it sits inside htdocs. Ready? Now change its name to xoops. This means that, when you run things locally, you'll have to type http://localhost/xoops" to access your XOOPS site.

Now, if you're installing your site in a hosted remote server, you'll have to upload the html directory to one of the directories you have access to. In this case, you'll probably have a public_html folder, and that's where you'll need to upload the complete html directory. Again, after uploading everything (probably with an FTP client software), change the name of this folder to xoops. Since you'll be installing in your root folder, in this case you'll access your site typing in your browser http://www.yoursite.com.

Are we ok so far? Well, we're ready now to begin the installation of the XOOPS software. To do it, point your browser to the directory you just made, that is, type http://localhost/xoops if you're in your local machine, or http://www.yoursite.com if you installed in a hosted remote server. If everything went well, this will awaken the XOOPS genie, and the system will run the file index.php. In doing so, the first thing it'll do is to include the file mainfile.php, which is the file in charge of holding a lot of system parameters. But for the moment, the file contains a reference to another file: install/index.php. In short terms, this means that the file launches the XOOPS Installation Wizard. And so the fun begins.

The wizard opens in your browser a page with the following content:

This is the welcome language selection page of the XOOPS Install Wizard

Figure 2.1. This is the welcome language selection page of the XOOPS Install Wizard

As you can see, the idea is to have installers for different versions, but for the moment there's just the English file. Of course we'll begin recollecting other languages version, so, if for some reason you need to install in a different language, within the install folder there's another folder called language. Inside there's still another folder called English, with some files inside. Copy the folder and rename the copy to another language's name, for instance, Spanish. Then translate the files inside and send us your translated files to include in a future repository for different installation languages. Ok?

All this needs to be done before the installation, so when the wizard reads the files, it can be aware there's more than one language to use during the actual installation.

But let's not spend more time on this. Since you're ready to install your software, you have to click on the button labeled Next. Another screen will appear, with some introductory content. There you can read what XOOPS is, the terms of its license, its environment requirements and, what's more important, the things you need to have ready before the actual installation begins. Many first-time users don't even bother reading this five short points, and thus march into installation hell just for not reading this stuff. See the screen:

This explanatory page includes crucial information about things that need to be there for the install to work

Figure 2.2. This explanatory page includes crucial information about things that need to be there for the install to work

Let's review each of these five bullets, one at a time.

  • Setup WWW server, PHP and database server properly. This means you need to be sure your Web server is active, it can process PHP files and there's a MySQL server running. Also means you know the details to connect to the database server. In other words, you'll need a user name and a password.

  • Prepare a database for your XOOPS site. This is a bit misleading. If you're installing locally, you don't need to prepare the database, and the wizard will create it for you, as we'll see a bit ahead. However, if you're installing in a remote server, you'll certainly need to create the database before installing XOOPS. This is because most host providers won't let you create databases easily; you have to use their tools (usually, a control panel) to do that. So in this case you'll need the database created, and you'll need to know the user and password necessary to communicate with that database.

  • Prepare user account and grant the user the access to the database.. This is already taken care of in the past steps, if you know the details about how to edit the database contents, or if you have root access in the case of a local installation, you're ready to proceed.

  • Make the directories of uploads/, cache/ and templates_c/ and the files of mainfile.php writable.. This is overlooked many times. What this means is these three directories and this file should be editable, you need to have writing privileges over them. In the next part of this guide we'll go over each option carefully.

  • Turn cookie and Javascript of your browser on.. Many of XOOPS options require the use of cookies. If you have them off, your XOOPS site will mysteriously fail. The same is true about Javascript; you need it to run many XOOPS core functions. Then again, if you don't have Javascript activated, you'll probably have a poor Internet experience, as many sites do need Javascript to work correctly.

So, to sum things up, you need all these things solved before attempting the installation. When you're ready, it's time to click on the button labelled Next. This will take you to the next screen, and we also need to go to the next chapter in this guide. Let's go to Chapter 3, Folder permissions

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