Table phocaguestbook_logging doesn't exist

[maglott]

Hi,

Following a migration from Joomla 2.5 to Joomla 3, 1 year ago, I find the following message, while submitting a post :

Table 'zelie_lemercurey.v0ei7_phocaguestbook_logging' doesn't exist SQL=SHOW FULL COLUMNS FROM `v0ei7_phocaguestbook_logging`

I remember having followed the procedure mentionned here https://www.phoca.cz/documents/50-phoca/ ... o-joomla-3
Unfortunately I haven't kept the 2.5 database, it's 1 year ago.

The guestbook url is http://www.restaurant-le-mercurey.com/g ... ant-chalon

Can you help?

Thanks in advance

Xavier

[Benno]

Hi,
try to create this table manually.
Take this guide as an example: https://www.phoca.cz/documents/16-joomla ... ase-column

Kind regards,
Benno

[maglott]

Thanks Benno for your reply.
But, as far as know, this table "phocaguestbook_logging" shouldn't exist.

[Benno]

Hi,

But, as far as know, this table "phocaguestbook_logging" shouldn't exist.

Of course, it should exist.
If you run Phoca Guestbook current version, run this query with help of phpMyAdmin:

Code: Select all

CREATE TABLE IF NOT EXISTS `#__phocaguestbook_logging` (
  `id` int(11) unsigned NOT NULL auto_increment,
  `catid` int(11) NOT NULL default '0',
  `postid` int(11) NOT NULL default '0',
  `captchaid` smallint(6) NOT NULL,
  `fields` tinyint(4) NOT NULL,
  `hidden_field` tinyint(4) NOT NULL,
  `forbidden_word` tinyint(4) NOT NULL,
  `used_time` int(11) NOT NULL,
  `session` tinyint(4) NOT NULL,
  `incoming_page` varchar(255) NOT NULL,
  `ip` varchar(20) NOT NULL default '',
  `ip_list` tinyint(4) NOT NULL,
  `ip_stopforum` tinyint(4) NOT NULL,
  `ip_stopforum_txt` varchar(128) NOT NULL,
  `ip_honeypot` tinyint(4) NOT NULL,
  `ip_botscout` tinyint(4) NOT NULL,
  `ip_botscout_txt` varchar(128) NOT NULL,
  `content_akismet` tinyint(4) NOT NULL,
  `content_akismet_txt` varchar(128) NOT NULL,
  `content_mollom` tinyint(4) NOT NULL,
  `content_mollom_txt` varchar(128) NOT NULL,
  `date` datetime NOT NULL default '0000-00-00 00:00:00',
  `state` tinyint(3) NOT NULL default '0',
  `params` text NOT NULL,
  PRIMARY KEY  (`id`),
  KEY `state` (`state`)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8 ;

Important! Change this prefix: #_ to your prefix before.

Kind regards,
Benno

[maglott]

Hi Benno,

Many thanks for your MySQL code, I have created the table with change prefix, and also catid default '10' (instead of '0')
I'm wondering what is 'postid" field, and is '0' the default value ?

Anyway I have now a new message :
Duplicate entry '1' for key 'PRIMARY' SQL=INSERT INTO `v0ei7_phocaguestbook_items` (`id`, `catid`, `parent_id`, `lft`, `rgt`, `level`, `path`, `username`, `userid`, `email`, `homesite`, `ip`, `title`, `alias`, `content`, `date`, `published`, `checked_out`, `checked_out_time`, `params`, `language`) VALUES (1, 0, 0, 0, 1, 0, '', 'ROOT', 0, '', '', '', 'root', 'root', '', '0000-00-00 00:00:00', 0, 0, '0000-00-00 00:00:00', '', '*');

Trying to google this message, it's a very old story.

Maybe you have another idea?

Thanks in advance.

Xavier

[Benno]

Hi,

Maybe you have another idea?

Unfortunately not.

Kind regards,
Benno

[maglott]

Thanks anyway.
Do you know what is 'postid' field, and is '0' the default value ?

[Jan]

Hi, this means: "Duplicate entry '1'"

there is one item set in table with ID 1 - so the row can be only added when the table is empty - now this means, you want to add row with ID 1 but there is one with ID 1 so such cannot be added again.

Postid is and ID of the post - this means, when you paste a post (message) it gets an ID and such can be stored in logging table (if logging is enabled)

Jan