Fatal Error - Table sessions doesn't exist. Fatal Error - Table sessions doesn't exist.
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Fatal Error - Table sessions doesn't exist.

Started by ToddW, November 30, 2010, 08:21:57 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

ToddW

Just upgraded to 1.5, and get "FATAL ERROR".
I enabled debug, and I see this:

While executing query 'DELETE FROM `ruff_copp1`.cpg_sessions WHERE time < 1291097513 AND remember = 0' in bridge/coppermine.inc.php on line 248

mySQL error: Table 'ruff_copp1.cpg_sessions' doesn't exist

What to do?

Nibbler

Did you try to update directly from 1.3 to 1.5? That's not supported. You have to update to 1.4 first then 1.5.

http://documentation.coppermine-gallery.net/en/upgrading.htm#upgrade_10

ToddW

Pretty sure I had 1.4 then wen to 1.5 though.

Αndré

You can manually add that table with the following query:
CREATE TABLE CPG_sessions (
  session_id char(32) NOT NULL default '',
  user_id int(11) default '0',
  time int(11) default NULL,
  remember int(1) default '0',
  PRIMARY KEY (session_id)
) COMMENT='Used to store sessions';

ToddW

Thanks, I did that, and also added a couple other missing columns in 2 other tables, and it seems to be working again on the front end.

I have yet to check the user/admin area but it's actually displaying something now :)

wurfgang

Quote from: Αndré on November 30, 2010, 03:02:04 PM
You can manually add that table with the following query:
CREATE TABLE CPG_sessions (
  session_id char(32) NOT NULL default '',
  user_id int(11) default '0',
  time int(11) default NULL,
  remember int(1) default '0',
  PRIMARY KEY (session_id)
) COMMENT='Used to store sessions';


solved my problem, thanks. but: case sensitive! it's "cpg" (not CPG):

CREATE TABLE cpg_sessions (
  session_id char(32) NOT NULL default '',
  user_id int(11) default '0',
  time int(11) default NULL,
  remember int(1) default '0',
  PRIMARY KEY (session_id)
) COMMENT='Used to store sessions';

phill104

It is capitalised as the prefix could be a number of things. On one of my galleries for instance it is cpg133, on another it is cpg154. We simply use the capitalisation to highlight that area.
It is a mistake to think you can solve any major problems just with potatoes.