Joomla 1.0.11 Installation

[oddconcept]

Yes I am using plesk 8.0

Thanks for all your help.
Please let me know if you find out any more information about adding apache to spacln.

Thanks again for all your help.

 

[AWD__@]

I need to know how to make the /tmp directory writeable. I'm running Plesk 8.0.1 and am installing Joomla 1.0.11. The install page continues to show the session save path of /tmp as unwriteable.

Here's what I've done so far.

chmod 666 /tmp so everyone will read and write but no exec. This is verified by ls -las:
8 drw-rw-rw- 4 root root tmp

Any info will be appreciated,

Michael

 

[carliebentley]

Originally posted by AWD__
I need to know how to make the /tmp directory writeable. I'm running Plesk 8.0.1 and am installing Joomla 1.0.11. The install page continues to show the session save path of /tmp as unwriteable.

Here's what I've done so far.

chmod 666 /tmp so everyone will read and write but no exec. This is verified by ls -las:
8 drw-rw-rw- 4 root root tmp

Any info will be appreciated,

Michael

I had this same problem, and it's not a matter of makeing the permissions 0666 on the /tmp directory.

In order for the /tmp directory to be useable, and have the noexec flag, it has to be mounted (like a drive) as a seperate partition with noexec commands.

There are many tutorials on here to walk you through the process.

Do a search for tmp noexec and see if this helps with your situation.

 

[AWD__@]

I discovered a relationship between the safe mode setting in php.ini and the session save path (at least using the /tmp dir.) Hopefully this will be helpful if it's not already in the forum.

I had created the hosting for the domain I'm installing Joomla on via the domain template in Plesk. When creating a domain template the option to have safe mode off (unchecked) is not there. I was unaware the option becomes available at the time of hosting set up and by default it's checked in the services section. It's easy to skip over the fact that safe mode will be On for a domain even though you may have turned safe mode Off in php.ini.

With safe mode Off in php.ini and safe mode On in Plesk settings for domain hosting settings, the session save path directory was not writeable. So, I turned safe mode On in the php.ini file and Off in Plesk domain hosting settings and discovered the session save path is now writeable. I don't know if that will always be the case if someone chooses a different path in the php.ini settings, but if you use /tmp, you won't need to mount it as a separate drive to get it writeable. You could run safe mode Off globally and have it unchecked in the domain hosting settings, but if you don't have to open it up globally, then I wouldn't.

Hope this helps...

Joomla rules!

 

[carliebentley]

I haven't found a reason to be concerned with what Joomla writes to the /tmp directory.

Mostly it's just session data, so the tmp directory doesn't have to be a noexec mounted partition, but, if there is more than one site on your server, there may be other scripts on there that could allow someone to upload a perl script to the tmp directory and execute it.

 

[CritiKill]

Joomla 1.0.12 and Plesk 8 Linux nightmares

I have a new Plesk 8 installation on my server. I've created a domain (set PHP to not run in safe mode) and FTP'ed the Joomla installation files to the domain's httpdocs folder. When I try to run the Joomla web installer, I get all the folders are unwriteable and so is the PHP sessions path.

Does anybody have a solution for this that does not involve chmodding 777 or PHPSUEXEC or anything too fancy. All I would like to do is to run a few Joomla installs without breaking out in cold sweats every time. This problem is costing me lots of time and money and I would REALLY like if somebody could help me get some kind of solution to this.

I like the suggestion of putting the domain ftp user into the Apache group or something, does anybody know if that is a viable, workable solution? Also, what is the command syntax to actually do this?

I am appalled that Plesk does'nt work out of the box with something as commonplace as Joomla.

 

[carliebentley]

Don't blame Plesk.

Your problem really isn't revolving around some deficiency of Plesk. In fact, Plesk and the wonderful Filemanager system makes installing Joomla a breeze.

Chmodding the folders to 0777 is actually pretty easy, and is only required to install Joomla. Once Joomla is installed it's possible to set most of those folders back to 0644 or some other more secure setting.

Personally I leave the folders at 0777, because of the security built into Joomla, there's a slim chance that those folders could be exploited.

Granted, it's not the most secure situation, but I've used other scripts that are no where near as secure and thanks to XMLRPC (which isn't in Joomla), those scripts are very exploitable.

I've had no problems running Joomla on nearly all of my sites even leaving the folders set to 0777.

Yes, I know it's possible to exploit a folder on a site set to 0777, but it's not easy and there's not that much that can be done with it.

I wouldn't blame plesk, because you are afraid of setting your folders to 0777. You can always set them to 0777, install Joomla, and then change them back. However you could break Joomla by setting the permissions too low.

 

[dyrer]

Warning: is_writable() [function.is-writable]: open_basedir restriction in effect. File(/var/lib/php/session) is not within the allowed path(s): (/var/www/vhosts/domain.com/httpdocs:/tmp) in /var/www/vhosts/domain.com/httpdocs/main/includes/joomla.php on line 2012
Unwriteable
Any way to fix that

 

[carliebentley]

Is there any reason you're attempting to write your session data to, "(/var/lib/php/session)"?

On my plesk server with RHEL4 on it, I make certain that Joomla! knows to put the session data in the /tmp directory, which on my server has been converted to a mounted partition that does not allow execution.

Also, it would help to know the particular version of Joomla!.

But once again, this doesn't look like a problem with Plesk, but looks like a problem with your Joomla! installation.