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 3. Folder permissions

Let me write, right?

We'll begin the process taking a look to the points mentioned in bullet four. Remember? It's the one that talked about making certain folders and a file writable. Let's take a look at what happens if you don't take care.

The first directory that needs writing permissions is uploads/. This is because in this directory is where you'll put the images you upload to your site. And to make a great site, you need to upload a lot of images. If this folder has no writing permissions, this is what you'll get:

The screen you get if the folder uploads/ is read only.

Figure 3.1. The screen you get if the folder uploads/ is read only.

So how do you make this folder writable? In Windows environments, you clear the “read only” attribute from the directory, either using Windows own commands (using the DOS command attrib) or some utility. In Linux environments, you need to set the permission on the folder to 777, using the command chmod. If the site is to be installed in a remote server, you can probably do this using your FTP client. If, for instance, you're using WS_FTP (a quite common FTP client), you position your cursor on the desired directory, click on its name using the right mouse button, and there you'll see a chmod command to apply to the directory. It will open a window with nine check boxes: all of them need to be checked.

Let's proceed. The next directory that need writing permissions is cache/. Why? Because this folder will contain none less than the whole structure of the administrative menu of your site. So if you want any control over your site, you need to be able to write here. When cache/ is not writable, you get a green screen warning you it's the first time you reach the admin section, even if you've been there zillions of times, so please be sure the folder is writable.

This is what you see if the folder is read only:

The screen you see if the folder cache/ is read only.

Figure 3.2. The screen you see if the folder cache/ is read only.

Ok. The third directory that needs writing permissions is templates_c/. In this directory you'll have the cached templates of your site. This means that for your site to run at full speed, you better can write here. When the folder is not writable, you'll see something like this:

This is what you see if the folder templates_c is not writable.

Figure 3.3. This is what you see if the folder templates_c is not writable.

Last, the bullet list of the writing permissions mentioned something about the file mainfile.php being writable. This is also crucial, as the file will contain, after the installation, a lot of the general system parameters, as you'll see after we install XOOPS. No wonder it's got this name. The file is essential for your XOOPS site to work. Mess with it and you'll risk losing your site. If you keep this file read-only, the wizard will warn you with a screen like this:

When mainfile.php is not writable, you see this screen.

Figure 3.4. When mainfile.php is not writable, you see this screen.

[Warning]Warning
I must warn you. You can proceed with the installation even if you see one of these red warning lights. The wizard will continue. However, some steps ahead you'll bump into an obstacle, as XOOPS finds out it can't do something that needs to be done. So if you see any of these red signs, correct the situation and refresh the screen.

What you need to see in order to proceed with peace of mind is something like:

The screen you want to see, filled with green go ahead lights.

Figure 3.5. The screen you want to see, filled with green “go ahead” lights.

If you see this screen while installing, congratulations! You have the writing permits okay, and you're set to continue installing XOOPS. To do so, click again in the button labeled Next. And to continue with this guide, see Chapter 4, General configuration.

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