Jump to content

Recommended Posts

Posted (edited)

Just fiddling around with eZ Publish and after I unzipped the distribution t my directory on my domain and went to the Wizard to configure, I got these messages:

 

Warning

 

* open_basedir

o open_basedir is in use and can give problems running eZ publish due to bugs in some PHP versions.

o It's recommended that it is turned off if you experience problems running eZ publish.

 

System check

 

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: settings settings/override var var/storage var/cache settings/siteaccess settings/siteaccess/admin design

Shell commands

 

These shell commands will give proper permission to the webserver.

 

cd /home/mydomain/public_html/nbcms

chmod -R ug+rwx settings settings/override var var/storage var/cache settings/siteaccess settings/siteaccess/admin design

chown -R nobody:nobody settings settings/override var var/storage var/cache settings/siteaccess settings/siteaccess/admin design

 

Alternative shell commands

 

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

 

cd /home/mydomain/public_html/nbcms

chmod -R a+rwx settings settings/override var var/storage var/cache settings/siteaccess settings/siteaccess/admin design

 

Any ideas on how I can fix these issues to be able to move on in the installation? I can't make sense of the way they said to fix the issues. Looks like greek to me! I have no idea what shell commands are.

Edited by webgyrl
Posted

Nat,

 

That wouldn't do any good if you did. For security reasons shell has been disabled from use by end users. You can chmod from most FTP programs though and as long as those directories are in your public_html directory, you "may" be able to do it that way.

Posted
Nat,

 

That wouldn't do any good if you did. For security reasons shell has been disabled from use by end users. You can chmod from most FTP programs though and as long as those directories are in your public_html directory, you "may" be able to do it that way.

 

Hmmm... I know I can CHMOD stuff from the file manager in cPanel and also with SmartFTP.. but it doesn't really say what permissions to set. Would the permissions just be 777?

 

Maybe I should email support to see if they should do it or if they would even allow that.

 

Thanks Rob & Bruce ;)

Posted (edited)

So I emailed support this morning and they have been cryptic. I basically emailed the above to them saying that I needed the permissions changed and asked for their advice or if they would be able to do it and got these replies:

 

1.) Hello,

 

We have received your ticket and are investigating this issue. We will reply back to this ticket very shortly with a update.

 

Thank you for your time.

 

 

Regards,

S*** S********

TotalChoice Hosting

 

_____________

 

 

2.) Hello,

 

Please be advised that we have some restrictions placed on the server for users to access folders for a security measure.

 

Thank you for your time and understanding.

 

Regards,

S*** S********

TotalChoice Hosting

 

 

Kinda useless replies!

 

So they didn't say yes they can do it or no they can't. I have emailed back asking for clarification. I really just want to know if they can do the permissions or if they will not do that a Yes or No would help.

 

Does anyone know if there is a list of 'approved' CMS packages that can run on TCH servers?

Edited by webgyrl
Posted

Ok, it's a no go:

 

Hello,

 

Please be advised that we can not able to change the file permissions in the server.

 

Thank you for your time.

 

Regards,

S**** S*********

TotalChoice Hosting

 

 

:thumbup1:

 

Bummer, ez is so comprehensive.

Posted

If you sent the Help Desk what you posted above, they may not have been clear on what directories you wanted the permissions changed on. A 'var' directory in your web space is okay, but there is also a '/var' system directory that would indeed be off-limits to you.

 

The directories to be changed should be have been specified as full paths:

>/home/username/public_html/nbcms/settings
/home/username/public_html/nbcms/settings/override
/home/username/public_html/nbcms/var
/home/username/public_html/nbcms/var/storage
/home/username/public_html/nbcms/var/cache
/home/username/public_html/nbcms/settings/siteaccess
/home/username/public_html/nbcms/settings/siteaccess/admin
/home/username/public_html/nbcms/design

(where 'username' is your CPanel username).

 

These shell commands will give proper permission to the webserver.

 

cd /home/username/public_html/nbcms

chmod -R ug+rwx settings settings/override var var/storage var/cache settings/siteaccess settings/siteaccess/admin design

chown -R nobody:nobody settings settings/override var var/storage var/cache settings/siteaccess settings/siteaccess/admin design

The 'chmod' command changes the permissions on the listed directories to 0775.

The 'chown' command changes the ownership of the directories from you to the user 'nobody' (which is the user ID that PHP scripts run under).

 

You could change the directory permissions yourself, using an FTP program or the File Manager in CPanel. However, the system will not allow you to perform any kind of 'chown' command - this is something that would have to be done by the Help Desk (assuming they would be willing to do it).

 

cd /home/mydomain/public_html/nbcms

chmod -R a+rwx settings settings/override var var/storage var/cache settings/siteaccess settings/siteaccess/admin design

The 'chmod' command in this case changes the permissions on the listed directories to 0777. Again, you can change the directory permissions yourself using an FTP program or the File Manager in CPanel. This option is your best bet to getting eZ Publish working on your site (and you don't need to Help Desk to do anything at all on your account).

Posted
If you sent the Help Desk what you posted above, they may not have been clear on what directories you wanted the permissions changed on. A 'var' directory in your web space is okay, but there is also a '/var' system directory that would indeed be off-limits to you.

 

The directories to be changed should be have been specified as full paths:

>/home/username/public_html/nbcms/settings
/home/username/public_html/nbcms/settings/override
/home/username/public_html/nbcms/var
/home/username/public_html/nbcms/var/storage
/home/username/public_html/nbcms/var/cache
/home/username/public_html/nbcms/settings/siteaccess
/home/username/public_html/nbcms/settings/siteaccess/admin
/home/username/public_html/nbcms/design

(where 'username' is your CPanel username).

The 'chmod' command changes the permissions on the listed directories to 0775.

The 'chown' command changes the ownership of the directories from you to the user 'nobody' (which is the user ID that PHP scripts run under).

 

You could change the directory permissions yourself, using an FTP program or the File Manager in CPanel. However, the system will not allow you to perform any kind of 'chown' command - this is something that would have to be done by the Help Desk (assuming they would be willing to do it).

The 'chmod' command in this case changes the permissions on the listed directories to 0777. Again, you can change the directory permissions yourself using an FTP program or the File Manager in CPanel. This option is your best bet to getting eZ Publish working on your site (and you don't need to Help Desk to do anything at all on your account).

 

 

David,

 

I had no idea that I had to list the directories like that. I just copied verbatim what the script told me upon install. Sorry, I am not really up to speed with this type of stuff so I am working with a very limited knowledge on CMS's and how they work etc. Scripting is not my strong point at all.

 

That being said, from the gist of the emails I got from support it seems that they may have issues with doing the chown command.

 

I am looking for an alternative CMS to try out that does not need Root or Shell Access. To be honest it's all very confusing to me at this point! I am just trying to design a site that is similar in function to this one: www . adamaworld . com

 

A CMS looks the best route to something like this.

 

Thanks so much for your help, I really apprecaite it.

Posted (edited)

David,

 

Are you generally saying that an install could be possible if I CHMOD 0775 or 0777 those listed directories?

If that is so, then maybe I can get it to work.

Edited by webgyrl
Posted
Are you generally saying that an install could be possible if I CHMOD 0775 or 0777 those listed directories?

Yes, I am! :thumbup1:

 

Since you cannot change the ownership of the directories, you would want to change the permissions on the directories to 0777. 0775 permissions would not help you in this case.

 

One thing I overlooked in my previous post: The 'chmod' command that is given includes the '-R' option, which makes the 'chmod' command recursively set permissions on every file and subdirectory within each listed directory. I don't know if this is strictly necessary or not (or even if there's any addtional files and subdirectories in the above listed directories). I'd suggest changing the permissions on the 8 listed directories above to 0777, and if eZ Publish still indicates permission problems, then go into each of those listed directories and set each file and subdirectory within them to 0777 permissions as well.

Posted

OK! Well then, I will give it a try. It's worth a shot for sure. I have to go to a session soon, but when I get back I will try it and let you know how I made out.

 

Thanks for translating Greek for me :thumbup1:

 

BTW is it foggy today in SF?

Posted
Several places on their site say that it is not recommended to install this CMS on a shared hosting account.

 

I saw that as well.

 

Hmmmm...

 

Also tried changing all the directories as specified to 777 and still got these two errors:

Warning

 

* open_basedir

o open_basedir is in use and can give problems running eZ publish due to bugs in some PHP versions.

o It's recommended that it is turned off if you experience problems running eZ publish.

 

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: settings settings/siteaccess/admin

Shell commands

 

These shell commands will give proper permission to the webserver.

 

cd /home/mydomain/public_html/nbcms

chmod -R ug+rwx settings settings/siteaccess/admin

chown -R nobody:nobody settings settings/siteaccess/admin

 

Alternative shell commands

 

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

 

cd /home/mydomain/public_html/nbcms

chmod -R a+rwx settings settings/siteaccess/admin

 

Even though I did chance the settings/siteaccess/admin to 777, it's still saying there are insufficient permissions.

 

That is weird.

 

The thing I like about eZPublish is that it seems easier to skin than other CMS's I have looved at.

 

Any suggestions.

Posted
Also tried changing all the directories as specified to 777 and still got these two errors:

Warning

* open_basedir

o open_basedir is in use and can give problems running eZ publish due to bugs in some PHP versions.

o It's recommended that it is turned off if you experience problems running eZ publish.

You're going to have to live with that warning - it is not something that you have the ability to 'turn off' (disable). The version PHP that TCH is currently running is pretty recent, so I would not expect to encounter any open_basedir 'bugs'.

 

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: settings settings/siteaccess/admin

Check the directories and make sure they have 0777 permissions, and also look within each of those directories and change the permissions of all files and subdirectories within them to 0777 as well.

 

BTW is it foggy today in SF?

Nope - blue skies and sunny today! ;)

Posted
While this script can be tweaked to run on our servers it was designed to be run on a dedicated server.

 

 

Yeah, that is what I am seeing as I read more.

 

I think I will abandon this idea.

 

David, thank you so much for your help ;) I don't wanna mess up the TCH servers or risk having to pull the site if it is indeed a resource hog. I think I will look for another option.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...