steve kelsey
Sophomore
Just Getting Started
Member Likes (0)
Hi,
This is my first request to the support team, nice to meet you.As it's the weekend I understand you won't be along for a while, hope you have a good one.
Here is my site which is in alpha at the moment...as you can see I have a lot to do....
http://www.irrilium.com/SecretPlan
The site is running on WP 3.1 and BP 1.2.8
Here is my problem
I have installed the Wordpress Chat plugin. I can see it in the setup panel and adjust settings just fine but no WSIWG icon shows up in the post editor and the corner pop-up does not show on the site.
I tried a reinstall just in case I had made an error but I have the same problem
This is my error log
/home8/irrilium/public_html/SecretPlan/wp-admin/error_log: AND b.spam = '0' AND b.deleted = '0' AND b.archived = '0' AND u.ignore = '0' AND b.blog_id != '' AND u.certainty > 0 ORDER BY u.certainty DESC, b.last_updated DESC LIMIT 0, 15 made by require_once, do_action, call_user_func_array, ust_admin_output
[13-Mar-2011 14:08:06] scraping text
[13-Mar-2011 14:08:06] scraping text
[13-Mar-2011 14:13:22] scraping text
...... repeated untill
[19-Mar-2011 10:13:13] scraping text
[19-Mar-2011 14:09:16] WordPress database error Multiple primary key defined for query ALTER TABLE wp_chat_log ADD PRIMARY KEY (id) made by activate_plugin, do_action, call_user_func_array, Chat->install, dbDelta
[19-Mar-2011 14:09:16] WordPress database error Duplicate key name 'blog_id' for query ALTER TABLE wp_chat_log ADD KEY blog_id (blog_id) made by activate_plugin, do_action, call_user_func_array, Chat->install, dbDelta
[19-Mar-2011 14:09:16] WordPress database error Duplicate key name 'chat_id' for query ALTER TABLE wp_chat_log ADD KEY chat_id (chat_id) made by activate_plugin, do_action, call_user_func_array, Chat->install, dbDelta
[26-Mar-2011 14:31:02] WordPress database error Multiple primary key defined for query ALTER TABLE wp_chat_log ADD PRIMARY KEY (id) made by activate_plugin, do_action, call_user_func_array, Chat->install, dbDelta
[26-Mar-2011 14:31:02] WordPress database error Duplicate key name 'blog_id' for query ALTER TABLE wp_chat_log ADD KEY blog_id (blog_id) made by activate_plugin, do_action, call_user_func_array, Chat->install, dbDelta
[26-Mar-2011 14:31:02] WordPress database error Duplicate key name 'chat_id' for query ALTER TABLE wp_chat_log ADD KEY chat_id (chat_id) made by activate_plugin, do_action, call_user_func_array, Chat->install, dbDelta
[26-Mar-2011 14:43:25] WordPress database error Multiple primary key defined for query ALTER TABLE wp_chat_log ADD PRIMARY KEY (id) made by activate_plugin, do_action, call_user_func_array, Chat->install, dbDelta
[26-Mar-2011 14:43:25] WordPress database error Duplicate key name 'blog_id' for query ALTER TABLE wp_chat_log ADD KEY blog_id (blog_id) made by activate_plugin, do_action, call_user_func_array, Chat->install, dbDelta
[26-Mar-2011 14:43:25] WordPress database error Duplicate key name 'chat_id' for query ALTER TABLE wp_chat_log ADD KEY chat_id (chat_id) made by activate_plugin, do_action, call_user_func_array, Chat->install, dbDelta
which is pretty insistent that I have goofed up the install with a duplicate key name blog id. I'll take it's word for it as I am very new to this.
What do I do to fix this?
How do I make sure it doesn't happen again?

Responses (3)
Member (joined April 2009) Likes (0)
Hiya steve,
First off, welcome to the forums! :)
Sorry for the trouble here. Let's start again and see if we can get things working. Firstly, disable the chat plugin within WordPress.
Next, log into your database - via phpmyadmin or other and look for the table 'wp_chat_log' and go ahead and remove the entire table.
Now, go back into WordPress and re-enable the Chat plugin. Let us know what happens.
It seems like the chat plugin was trying to create a chat where there was an ID already in existence - by removing that table we're allowing the plugin to get a fresh start.
Let us know how this goes for ya.
Thanks!
Member (joined January 2011) Likes (0)
Thank you for the feedback and I am now good to go.
The visibility cause was a little different as I had added some CSS in my child theme that did't help.
I will clean out the database as you suggest.
Thank you for your help!
Steve
Member (joined April 2009) Likes (0)
Hiya Steve,
Cool. Just let us know if you need anything further :)
Become a member