CMS Made Simple Forums

I have installed CMS Made Simple on a Lunar Pages account. Running Version 1.4.1 on PHP 5.2.6. I have been able to fit most of the problems with the php.ini file but am still experience difficulty with the following:

1) The session_save_path which says "No check because of OS!"

2) I get a message under permissions which says config_file 0666 X - I have contacted LunarPages about this and they say that 0666 is "just how their system writes 666" is there a workaround for this?

These are the only 2 errors that are showing.

Natalie

Dont worry about 1. Al my sites say that and they all run perfectly.

Where are you seeing problem 2.?

nncreativecity wrote: 1) The session_save_path which says "No check because of OS!"

PHP have not info on your session_save_path and use OS (temporary folders) for this
It's an info only

nncreativecity wrote: 2) I get a message under permissions which says config_file 0666 X - I have contacted LunarPages about this and they say that 0666 is "just how their system writes 666" is there a workaround for this?

For writing your configuration your config.php must be writable
After installation advice is to switch to read-only

Alby

I was able to fix the config_file problem by changing the permissions to read-only as you suggested. Thanks. But I don't know what you mean about the session_save_path ... could you perhaps explain in more depth. Can I designate a save.path directory instead of it working on local OS?

You could try setting it via .htaccess file.

php_value session.save_path "/path/to/your/cmsms/tmp/"

Nullig

If I change the .htacess file, I get a server error 500. I tried setting the session_save_path in php.ini and still get the message "No check because OS path"

nncreativecity wrote: If I change the .htacess file, I get a server error 500. I tried setting the session_save_path in php.ini and still get the message "No check because OS path"

Probably you have cgi php
but repeat, if SESSIONS works it's OK, it's a internal process only, of your system, that not affect CMS functionality

Alby

Ok, thanks. All seems to be working ok thus far. If I have any new problems, then I will repost.