Insatlation problem with templates_c and php.ini

[avtuvy]

I am getting the errors listed below, I cannot find php.ini and I changed the permissions (chmod) on templates_c to 755. Please help



Checking PHP version: OK! ( 5.0.0 [minimun version] <= 5.2.6 [your version] )
Checking if Register Globals = OFF: Failed! is ON - Please change the setting in your php.ini file
Checking if sessions are properly configured: OK!
Checking if ../gui/templates_c directory exists: OK!
Checking if ../gui/templates_c directory is writable: Failed!

[havlatm]

The directory must be writable for web server (not for your user). Modify owner of the directory. For example:
chown apache:apache gui/templates_c

Location of php.ini depends on you OS distribution and php installation. Linux supports two commands to find it: locate and find. See web for more proper using of this commands.

[avtuvy]

I created a user called apache and a group called apache and ran that command. I am still getting the same error about the directory.
WhenI created user apache I entered a password for the user, do I need to configure that on the web server? web server and directory are on the same physical machine

[havlatm]

User apache should be already existing ...
chmod 777 template_c
do the job as well.

[kasirajan]

Give full permission of the whole testlink folder. Use this command..

chmod 777 -R WEBSERVER_ROOT_FOLDER\testlink.

[fman]

777 is not a good SysAdmin practice for a Production site.
Why you need to give exec rights to everyone?

[avtuvy]

I tried both chown and chmod as suggested and I still get the same error message, is it just templates_c that need to be changed or the whole path from root?

[havlatm]

It must be just this directory and all directories under must be readable. Could you add here what gets #ls -la <path_of_web_root>/testlink/gui

[avtuvy]

I might not have installed it with the correct privliges, what do you mean by web root?

[TurboPT]

Navigate down to the gui directory, and issue this command:

chown apache:apache templates_c

That should work without giving all permission. If there are still problems, post another reply.

[avtuvy]

I am still having the same set of error messages shown in my first post

[havlatm]

And you will still have. Because you are not able to share what you see on your command line. So do not wait for answer.

[avtuvy]

Sorry I missed it the last time

drwxr-xr-x 10 atuvy users 4096 2008-02-17 15:29 .
drwxr-xr-x 10 atuvy users 4096 2008-02-17 15:36 ..
drwxr-xr-x 2 atuvy users 4096 2008-02-17 15:29 css
drwxr-xr-x 5 atuvy users 4096 2008-02-17 15:29 drag_and_drop
drwxr-xr-x 15 atuvy users 4096 2008-02-17 15:29 help
drwxr-xr-x 2 atuvy users 4096 2008-02-17 15:29 javascript
drwxr-xr-x 2 atuvy users 4096 2008-02-17 15:29 niftycube
drwxr-xr-x 2 atuvy users 4096 2008-02-17 15:29 templates
drwxr-xr-x 2 apache apache 4096 2008-02-17 15:29 templates_c
drwxr-xr-x 4 atuvy users 4096 2008-02-17 15:29 themes
toshiba-tablet:/home/atuvy/TestLink/testlink/gui #

[TurboPT]

Another reason, that I've just noticed missing in your path...

You posted:

toshiba-tablet:/home/atuvy/TestLink/testlink/gui #

I would have expected: (note the bold)
toshiba-tablet:/home/atuvy/public_html/TestLink/testlink/gui #

Then all these permission troubles might be resolved.

Here's a link about setting up for the 'public_html' -- it's NOT just a simple matter of adding the directory: (see NOTE, below)
http://httpd.apache.org/docs/2.0/howto/public_html.html

Basically, there is still permission issues all the way up to the /home path -- so that everything we've set up to now has been pointless for your current location.

Try to apply the public_html and let us know.

NOTE:
Another other way to test the installation, without going through the public_html hassle, would be to copy [or setup] Testlink at the /var/www/html/ directory as an alternative (this assumes you have privileges to do so, of course, which appears that you do by the root [#] prompt). Remember the apache owner change? That will need to be applied to the /templates_c directory in the new location.

Otherwise, if you don't have the privileges, then the sysadmin will need to get involved.