Page 1 of 1

Session.save_path problem preventing proper installation

Posted: Thu Jun 05, 2008 9:10 pm
by orangecat
I have installed this CMS many times before and never had this problem. Can anyone help?

Here is what it says when I'm on step 1 of installation:

Checking if session.save_path is writable

Your session.save_path is "". Not having this as writable may make logins to the Admin Panel not work. You may want to look into making this path writable if you have trouble logging into the Admin Panel. This test may fail if safe_mode is enabled (see below).


I have tried installing it anyway, and it works fine for me, but the client can't log in no matter what he does. It also looks like the images in the admin part are all scrunched up. So I removed everything, and reinstalled agin. But the same thing happens. Tried the latest version, AND the previous one. Same issue on both.

Re: Session.save_path problem preventing proper installation

Posted: Thu Jun 05, 2008 10:10 pm
by calguy1000
Solution: Modify your setup so that your session save path is writable. (google?)

Re: Session.save_path problem preventing proper installation

Posted: Thu Jun 05, 2008 10:48 pm
by orangecat
I did google it but didn't find any clear instructions on how to make it writeable. Maybe I just didn't search the right terms, I don't know.

Can anyone please spell it out for me?

Thank you!

Re: Session.save_path problem preventing proper installation

Posted: Thu Jun 05, 2008 11:42 pm
by orangecat
I'm hosting it myself. I have several other sites there as well all of which have CMS made simple and have not run into this problem before.

I suppose I'll have to contact the company that I resell for and see if they can help. I was just hoping it was something easily done and that you guys might be able to point me int he right directions. I know I'll be waiting a while to hear back from the hosting company.

Re: Session.save_path problem preventing proper installation

Posted: Thu Jun 05, 2008 11:45 pm
by Dr.CSS
I had this on my main site just recently and it turned out they had just made some changes so they fixed it for me...

I was trying to do another install for another site in my server when it came up...

Re: Session.save_path problem preventing proper installation

Posted: Fri Jun 06, 2008 1:45 am
by orangecat
I got a response from the hosting people and they sad that it actually IS writable but I'm getting the error because the folder is not owned by the user.

I'm not sure what else to try. My client still cannot log in, although I can perfectly fine. And the images in the admin area are still scrunched up.

Suggestions?

Re: Session.save_path problem preventing proper installation

Posted: Sun Jun 08, 2008 2:38 am
by orangecat
I'm still having this problem. My host has simply stopped responding to my support ticket, and now I'm stuck. Does anyone know how to resolve this?

Re: Session.save_path problem preventing proper installation

Posted: Sun Jun 08, 2008 8:39 am
by alby
orangecat wrote: I'm still having this problem. My host has simply stopped responding to my support ticket, and now I'm stuck. Does anyone know how to resolve this?
Try to add this row in top of include.php:

ini_set('session.save_path', '/cms_root_path/tmp');

where cms_root_path is your root_path of config.php ($config['root_path'])

Alby

Re: Session.save_path problem preventing proper installation

Posted: Mon Jun 09, 2008 12:43 am
by orangecat
Tried it, no change. Thank you though.

Any other suggestion?

Re: Session.save_path problem preventing proper installation

Posted: Tue Jun 10, 2008 3:11 pm
by orangecat
Anyone?

Re: Session.save_path problem preventing proper installation

Posted: Tue Jun 10, 2008 3:47 pm
by alby
orangecat wrote: Anyone?
Mybe ini_set is disabled. Try with:
session_save_path('/cms_root_path/tmp');

Check with phpinfo() if you have php via cgi-bin (or fastcgi) or apache module

Alby

Re: Session.save_path problem preventing proper installation

Posted: Thu Jun 12, 2008 8:57 am
by SusanN
I've had problems with Session.save_path also.  The only solution I've found was posted by mww (the last post in this thread):  http://forum.cmsmadesimple.org/index.ph ... 568.0.html .