Now this is something new

[Redeemer]

Well, I have no idea what happened, but suddenly my store is doing bizarre stuff. It was working fine, now I'm getting these errors on the store:

 

Warning: session_save_path(): open_basedir restriction in effect. File(/temp) is not within the allowed path(s): (/tmp:/usr/local/4admin/apache/vhosts/midwestbarbell.com/httpdocs:/usr/local/4admin/apache/vhosts/midwestbarbell.com/storage:/usr/local/4admin/apache/vhosts/midwestbarbell.com/web_users:/usr/local/4admin/apache/lib/php:/usr/local/4admin/phpstuff) in /usr/local/4admin/apache/vhosts/midwestbarbell.com/httpdocs/catalog/includes/functions/sessions.php on line 148

 

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/4admin/apache/vhosts/midwestbarbell.com/httpdocs/catalog/includes/functions/sessions.php:148) in /usr/local/4admin/apache/vhosts/midwestbarbell.com/httpdocs/catalog/includes/functions/general.php on line 1227

 

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /usr/local/4admin/apache/vhosts/midwestbarbell.com/httpdocs/catalog/includes/functions/sessions.php:148) in /usr/local/4admin/apache/vhosts/midwestbarbell.com/httpdocs/catalog/includes/functions/sessions.php on line 97

 

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /usr/local/4admin/apache/vhosts/midwestbarbell.com/httpdocs/catalog/includes/functions/sessions.php:148)

 

I'm getting similar errors on the admin page. The other thing I'm noticing is that there are two entries for some of the settings on the admin page.

 

Can anyone shed some light on this for me?

[kgt]

Do one of the following:

 

1. Edit includes/configure.php and change the STORE_SESSIONS line so that it looks like this:

 

define('STORE_SESSIONS', 'mysql');

 

2. Go to your admin tool and go to Configuration > Sessions. Change Session Directory to read

 

/tmp

[Redeemer]

I tried the second option - sorry, I should've mentioned that when I posted.

 

I e-mailed this issue to my hosting company as well, and have since found out that this is a result of some upgrades they've done, so I have to do a reinstall.

 

YAY.

[Redeemer]

Even better - just ran the reinstall, and that doesn't work either. Still getting the same errors.

 

This is what they're telling me they're upgrading:

 

REVISED: Due to significant incompatibilities between PHP 4 and 5 we have revised our upgrade plan. The following software will be upgraded to the specified versions within the next 14 days:

 

Apache 1.3.34

PHP 4.4.2

OpenSSL 0.9.8a

libmysqlclient 5.0.18

ionCube PHP Loader v3.1.9

Zend Optimizer v2.6.2

Fileinfo 1.0.3

 

We will be adding PHP 5 support for files with a .php5 extension by default, and each directory will be able to have PHP 5 selectively enabled for .php files. With this scheme, we will begin supporting PHP 4 and 5 on all servers simultaneously.

 

Any help anyone can offer would be appreciated.

[AlanR]

http://www.oscommerce.com/forums/index.php?showtopic=184484

[Redeemer]

http://www.oscommerce.com/forums/index.php?showtopic=184484

 

Alan - thank you.

 

It figures...I don't do a search before posting, and it comes back to bite me. :) I did not make that change, however. I wonder if it would have worked as well instead of what follows.

 

I've been working with my hosting company, and he wrote this back to me:

 

No, I actually had to add something to vhost configuration, which should last. I was checking through out the distribution files and I found a file called "catalog/admin/easypopulate.php" that has two lines at the top of the file referencing temp directories. The issue is that "/temp" is being read as if it was a separate section on the file system, something you do not have access to. You would need to change the links so that /temp actually points to /usr/local/4admin/apache/vhosts/midwestbarbell.com/httpdocs/catalog/temp/ , not /temp. I tried looking within your admin area for OsCommerce but I could not find where I could change it, so it must have been during the install process.

 

I did see how our auto-installer for oscommerce now is incorrect and I will notify our developers so that they can fix them.

 

The interesting part about that is when I ran my install originally, I was trying to store the sessions in files and not the DB, and ran into this very issue. I couldn't figure out how to get the path set correctly, so I just decided to store them in the DB since that's preferred anyway.