Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

My webhost upgraded to PHP 4.4.1, now . . .


BaileyBoy

Recommended Posts

I get the following errors on my catalog pages:

 

Warning: session_save_path(): SAFE MODE Restriction in effect. The script whose uid is 931 is not allowed to access owned by uid 0 in /home/virtual/site266/fst/var/www/html/browse/includes/functions/sessions.php on line 118

 

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /home/virtual/site266/fst/var/www/html/browse/includes/functions/sessions.php:118) in /home/virtual/site266/fst/var/www/html/browse/includes/functions/sessions.php on line 67

 

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/virtual/site266/fst/var/www/html/browse/includes/functions/sessions.php:118) in /home/virtual/site266/fst/var/www/html/browse/includes/functions/sessions.php on line 67

 

I looked into the line numbers and found no easy fix, I'm kind of a PHP noob. I thought I'd ask around here for assistence before I do anything drastic. It sucks because now no orders can be placed just as my visitation was really starting to grow :angry:

 

THANKS!!!!

Link to comment
Share on other sites

Create a directory named sessions in your catalog folder (the actual name and location are not important, it can be anywhere in your webspace).

 

Go into admin -> Configuration -> Sessions and set the Session Directory to point to this new directory.

Local: Mac OS X 10.5.8 - Apache 2.2/php 5.3.0/MySQL 5.4.10 • Web Servers: Linux

Tools: BBEdit, Coda, Versions (Subversion), Sequel Pro (db management)

Link to comment
Share on other sites

I've appied the same fix ... I don't have the 'SAFE MODE Restriction in effect' line anymore but still have the following?

 

Any insight?

 

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /home/virtual/site16/fst/var/www/html/includes/functions/sessions.php:117) in /home/virtual/site16/fst/var/www/html/includes/functions/sessions.php on line 67

 

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/virtual/site16/fst/var/www/html/includes/functions/sessions.php:117) in /home/virtual/site16/fst/var/www/html/includes/functions/sessions.php on line 67

Thank you.

Link to comment
Share on other sites

I've appied the same fix ... I don't have the 'SAFE MODE Restriction in effect' line anymore but still have the following?

 

Any insight?

 

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at functions/sessions.php:117) in /home/virtual/site16/fst/var/www/html/includes/functions/sessions.php on line 67

 

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/virtual/site16/fst/var/www/html/includes/functions/sessions.php:117) in /home/virtual/site16/fst/var/www/html/includes/functions/sessions.php on line 67

 

Did you open the sessions.php file and save? If you did make sure you did not add any white space before the first <?php or after the last ?>

 

Did you use the correct path in admin?

 

It'll be something like:

 

/home/virtual/site16/fst/var/www/html/mynewsessionsfolder.

 

Make sure you have sessions set to mysql in includes/configure.php (the last line)

 

define('DB_SERVER', ''); // eg, localhost - should not be empty for productive servers

define('DB_SERVER_USERNAME', '');

define('DB_SERVER_PASSWORD', '');

define('DB_DATABASE', 'osCommerce');

define('USE_PCONNECT', 'false'); // use persistent connections?

define('STORE_SESSIONS', 'mysql'); // leave empty '' for default handler or set to 'mysql'

?>

Local: Mac OS X 10.5.8 - Apache 2.2/php 5.3.0/MySQL 5.4.10 • Web Servers: Linux

Tools: BBEdit, Coda, Versions (Subversion), Sequel Pro (db management)

Link to comment
Share on other sites

the headers must be the first thing that is sent by the page hence if you put whitespace in by acident then it messes it up. so it is always only the first error message you have to worry about. Also - I would not put full paths to your code on public forums. just for security, cut out the stuff thatis specific to you. e.g cut this out

 

/home/virtual/site16/fst/var/www/

always here to offer some useless advice....

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...