Just installed Drupal 4.5.1 on a server that, according to phpInfo(), is running PHP as a CGI standalone with session.save_handler = files, instead of user. Since I don't have access to the php.ini file, I finished the install anyway and, surprisingly, was able to register and log-in the first user.

What will happen if leave it this way? Has the code been modified to run with either save_handler option? Just want to know before I bug the sysadmin for a copy of php.ini..

Comments

boris mann’s picture

The .htaccess file in the root of the drupal directory overrides those settings.

jpklein’s picture

My provider is running PHP in CGI standalone mode, so PHP won't read .htaccess. The fix is to copy php.ini to the drupal directory, but they won't give me a copy..

so again, is it OK to run 4.5.1 with the "files" setting? what are the consequences?

boris mann’s picture

Sessions are stored in the DB. AFAIK, Drupal won't work correctly with the "files" setting -- users can't login, etc.

I would probably find a new provider that supports (at least) .htaccess.

moshe weitzman’s picture

you set the environment you want with ini_set() statements at top of includes/conf.php. if that doesn't work, just put them at the top of index.php