Getting SESSION ERROR on every page...

Joined: Jun 19, 2008 Posts: 18

Hey,

I'm getting a page that says "SESSION ERROR" on every single digital shop page i try to access, I haven't changed any of the files... could really use some help on this =/

Thanks,
- Koshy

Site Admin Joined: Oct 25, 2004 Posts: 754

Do you have sentinel installed? If so, try turning off the "Flood Blocker" and see if the error goes away. Let me know if it works.

Joined: Jun 19, 2008 Posts: 18

I went to Blocker Settings for Flood and it showed:

Activate: You can not use .ftaccess writting until you have set the ftaccess Path in admin.

Sooo IDK if it is enabled or disabled ... or how too do either tbh =(

Some direction from you would be greatly appreciated...

Thanks,
- Koshy

Code Authors · Joined: Dec 09, 2006 Posts: 248

If you see that message and under it, it says write to ftaccess set to 'No' then Flood Blocker is not turned on.
If this is an error that has suddenly just started appearing, the most likely cause is your host not allowing PHP_SESSION's which is possible if they have updated to a newer version of PHP or rebuilt Apache and forgot to 'allow' that function or the session.save path is set wrong on the server.
Here is a simple test code you can use. Create a new php file called test.php and place this code in it

Code:

<?php
session_start();

// If session variable doesnt exist, register it
if ( !isset ( $_SESSION['test'] ) ) {
$_SESSION['test'] = 'Hello World!';
echo $_SESSION['test'], ' is registered.<br />Please refresh page' ;
} else {
// Its registered so display it
echo '$_SESSION[test] = ' , $_SESSION['test'];
}
?>

When you execute the code (www.yoursite.com/test.php ) you should see the message

Quote:

$_SESSION['test'] is registered.
Please refresh page

if the session was registered properly.
When you refresh the page you should see

Quote:

$_SESSION['test'] = Hello World!

If tht doesn't work then definitely contact your host and ask them to check the path to session.save_path in their php.ini file

Joined: Jun 19, 2008 Posts: 18

Turns out the host had upgraded to apache 2 without telling me ;P

Thanks for your help,
- Koshy