Forums / Install & configuration / Help to setup eZ publish 3.9.0

Help to setup eZ publish 3.9.0

Author Message

Stefan Stender

Sunday 11 March 2007 7:17:03 am

Hey,

I have the last week tryed to setup eZ publish.
But it fails every time, or make a new error.

Can someone please help me to setup the installation, that all when i can costimize it by myself.

Here is the URL for the installation.
http://lifeonthecouch.com/ezpublish-3.9.0/

Here is the first error, when I have uploaded all the files.

<b>System check</b>

There are some important issues that have to be resolved. A list of issues / problems is presented below. Each section contains a description and a suggested / recommended solution.

Once the problems / issues are fixed, you may click the Next button to continue. The system check will be run again. If everything is okay, the setup will go to the next stage. If there are problems, the system check page will reappear.

Some issues may be ignored by checking the Ignore this test checkbox(es); however, this is not recommended.

It is also possible to do some finetuning of your system, click Finetune instead Next if you want to see the finetuning hints.
Issues
1. Insufficient directory permissions

eZ publish cannot write to some important directories, without this the setup cannot finish and parts of eZ publish will fail.
The affected directories are: design extension settings settings/override settings/siteaccess settings/siteaccess/admin var var/cache var/storage
Shell commands

These shell commands will give proper permission to the webserver.

cd /mounted-storage/home45b/sub004/sc32673-NFGI/www/gourmetbornholm
chmod -R ug+rwx design extension settings settings/override settings/siteaccess settings/siteaccess/admin var var/cache var/storage
chown -R nobody:nobody design extension settings settings/override settings/siteaccess settings/siteaccess/admin var var/cache var/storage

Alternative shell commands

If you don't have permissions to change the ownership you can try these commands.

cd /mounted-storage/home45b/sub004/sc32673-NFGI/www/gourmetbornholm
chmod -R a+rwx design extension settings settings/override settings/siteaccess settings/siteaccess/admin var var/cache var/storage

Ignore this test

2. PHP safe mode is enabled

eZ publish may work with safe mode on, however there might be several features that will be unavailable. Some of the things that might occur are:

* Not possible to extend time limits
o Some parts of eZ publish relies on cronjobs to handle workflows etc., and may require a longer time to run than normal page loads. With this on the cronjob scripts will not succeed.
* Wrong permissions
o If the site is not setup correctly eZ publish will not be able to work with files correctly, this could mean file uploads, image handling and cache creation. Safe mode requires that the same owner is set on the index.php script and all other files for the site.
* File uploading
o Uploading files trough the web will not possible unless configured correctly. This means that images, files and media will not be possible to use.

It's recommended that the option is turned off. To turn it off edit your php.ini configuration and set safe_mode to Off. More information on the subject can be found at php.net.
php.ini example:

safe_mode = 0

If you're not able to turn safe mode off you should try to fix the following issues.
Permissions

To make sure that all files have the correct user and group owner run the following commands.

cd /mounted-storage/home45b/sub004/sc32673-NFGI/www/gourmetbornholm
chown nouser.nouser *.php
chown -R nouser.nouser cronjobs design doc lib settings update kernel sdk share var

Alternatively you may run

cd /mounted-storage/home45b/sub004/sc32673-NFGI/www/gourmetbornholm
chown nouser.nouser -R *

If you only have access to the site using ftp you will have to consult your ftp client and server to see if it is possible to run the chown command.

Note: The nouser.nouser must be changed to your webserver username and groupname.

Ignore this test

3. AcceptPathInfo disabled or running in CGI mode

You need to enable AcceptPathInfo in your Apache config file, if you're using apache 2.x. If you're running apache 1.3, eZ publish will not run in CGI mode.

Check the Apache documentation, or enter the following into your httpd.conf file.
AcceptPathInfo On

Remember to restart your web server afterwards.
Ignore this test

4. File uploading is not possible

The PHP upload directory /upload_tmp does not exists or is not accessible, without this you will not be able to upload files or images to eZ publish.

Create the directory /upload_tmp on your system. If you do not have the possibility to create this yourself ask the administrator to create it for you.
Shell commands

This shell command will create the upload directory.

mkdir -p /upload_tmp

<b>Can I just ignore the test?</b>

If Yes, the next error I get is when Iam 53% complete in the installation.

Please choose a site package you would like to test or base your site on.

Error

Retreiving remote site packages list failed. You may upload packages manually.

Remote repository URL: http://packages.ez.no/ezpublish/3.9

Why can't the installation find the packages?
Anyway, when I download the packages and uploade the files notthing happens?

Please help me! =)

I use Servage.net for hosting.

//Stefan Stender

Paul Wilson

Sunday 11 March 2007 3:52:25 pm

Hi Stefan,

I've had no experience of some of your errors, but I might be able to answer most of your questions.

The system check page ensures your server environment will allow EZ Publish to function properly. It may be possible to ignore some of these checks, but it is not always useful.

<b>Directory Permissions</b>
To streamline its operation, EZ Publish creates a lot of cache files which are placed within the "var" directory and its sub-directories. Files uploaded by your or by users are also stored in these folders. Although someone else might correct me, I think it's possible to say that all of the other EZ Publish folders deal with configuration, design and various code, while the "var" directories deal with what EZ Publish is <i>actually doing</i> to produce a site. It's the working area of EZ Publish. The other folders mentioned in this directory permissions section are essential to setting up EZ Publish.

Setting these directory permissions is pretty vital. You can usually do this by:
1. Entering the commands shown via a telnet shell program (eg absolute telnet)
2. Changing the permissions of the folders by using an FTP program (eg smartFTP), or
3. If you have a cpanel or other web front-end to a web hosting account, use it's file manager.

Looking at your hosting provider, they mention having a "Web Based Administration Panel" ... this is what I mention in (3) above. If you haven't had any experience of (1) or (2), try this (3).

To use this,
1) log into your hosting account.
2) click on "file manager" (or something similar) - this will bring up a file/folder structure of your hosting account
3) navigate to the folders indicated by EZ Publish
4) You then need to "change permissions" for these folders. In Cpanel, a menu for this comes up when you click on the name of a folder. The permissions commands need to be set for user/group or all ... and the rwx refers to read/write/execute permissions.Tick the relevant boxes and click the button to store the permisisons changes.

I haven't struck the other configuration problems you mentioned, though going on the fact that the EZ install suggestions for the directory permissions works fine, I expect their other suggestions would be fine too. If you have telnet / shell access (as per 1, above), then it looks like entering the indicated commands would deal with those tests.

<b>Packages Installation</b>
Looking at the system check messages you're getting (and ignoring), it seems pretty clear that EZ Publish is going to have problems uploading and installing the files it needs ... it looks like the packages problem you're getting to is just the first evidence of this. Packages are written to a directory below the "var" directory. But if EZ Publish can't create files there, then nothing is going to happen.

I hope this helps.

- Paul