I wonder how this got missed:

By upgrade from Joomlaboard tables that are copied from joomlaboard don't get updated at all as CREATE TABLE IF NOT EXISTS lines stops right there.. Result? No indexes, no additional fields (group_id, uhits..).

I hope I got it all - developers please check! This is reason for those big speed degradations, wrong users on profile click etc.

EDIT: This should be the last version, previous ones were incomplete:

a) Use some kind of MySQL manager (phpMyAdmin)
b) Execute the below code. Normal prefix is jos_ (for some older instalations it could be mos_), so the code would look like this:

Code:

ALTER TABLE `jos_fb_attachments` ADD PRIMARY KEY ( `mesid` ); ALTER TABLE `jos_fb_categories` ADD PRIMARY KEY ( `id` ); ALTER TABLE `jos_fb_categories` ADD INDEX ( `parent` ); ALTER TABLE `jos_fb_categories` ADD INDEX `published_pubaccess_id` ( `published` , `pub_access` , `id` ); ALTER TABLE `jos_fb_messages` ADD PRIMARY KEY ( `id` ); ALTER TABLE `jos_fb_messages` ADD INDEX (`thread`); ALTER TABLE `jos_fb_messages` ADD INDEX (`parent`); ALTER TABLE `jos_fb_messages` ADD INDEX (`catid`); ALTER TABLE `jos_fb_messages` ADD INDEX (`ip`); ALTER TABLE `jos_fb_messages` ADD INDEX (`userid`); ALTER TABLE `jos_fb_messages` ADD INDEX (`time`); ALTER TABLE `jos_fb_messages` ADD INDEX (`locked`); ALTER TABLE `jos_fb_messages` ADD INDEX `hold_time` (`hold`,`time`); ALTER TABLE `jos_fb_messages_text` ADD PRIMARY KEY ( `mesid` ); ALTER TABLE `jos_fb_moderation` ADD PRIMARY KEY ( `catid` , `userid` ); ALTER TABLE `jos_fb_sessions` ADD PRIMARY KEY ( `userid` ); ALTER TABLE `jos_fb_smileys` ADD PRIMARY KEY ( `id` ); ALTER TABLE `jos_fb_subscriptions` ADD INDEX (`thread`); ALTER TABLE `jos_fb_subscriptions` ADD INDEX (`userid`); ALTER TABLE `jos_fb_users` ADD `group_id` INT( 4 ) DEFAULT '1' NOT NULL AFTER `karma_time` , ADD `uhits` INT( 11 ) DEFAULT '0' NOT NULL AFTER `group_id` ; ALTER TABLE `jos_fb_users` ADD PRIMARY KEY ( `userid` ); ALTER TABLE `jos_fb_users` ADD INDEX (`group_id`); ALTER TABLE `jos_fb_whoisonline` ADD PRIMARY KEY ( `id` ); ALTER TABLE `jos_fb_whoisonline` ADD INDEX (`userid`); ALTER TABLE `jos_fb_categories` CHANGE `id` `id` INT( 11 ) NOT NULL AUTO_INCREMENT; ALTER TABLE `jos_fb_messages` CHANGE `id` `id` INT( 11 ) NOT NULL AUTO_INCREMENT; ALTER TABLE `jos_fb_smileys` CHANGE `id` `id` INT( 4 ) NOT NULL AUTO_INCREMENT; REPLACE into `jos_fb_smileys`(`id`,`code`,`location`,`greylocation`,`emoticonbar`) values (1,'B)','cool.png','cool-grey.png',1),(2,':(','sad.png','sad-grey.png',1),(3,':)','smile.png','smile-grey.png',1),(4,':-)','smile.png','smile-grey.png',0),(5,': -(','sad.png','sad-grey.png',0),(6,':laugh:','laughing.png','laughing-grey.png',1),(7,':cheer:','cheerful.png','cheerful-grey.png',1),(8,';)','wink.png','wink-grey.png',1),(9,';-)','wink.png','wink-grey.png',0),(10,':P','tongue.png','tongue- grey.png',1),(12,':X','sick.png','sick-grey.png',0),(13,':x','sick.png','sick-grey.png',0),(14,':angry:','angry.png','angry-grey.png',1),(15,':mad:','angry.png','angry-grey.png',0),(16,':unsure:','unsure.png','unsure-grey.png',1),(17,':ohmy: ','shocked.png','shocked-grey.png',1),(18,':huh:','wassat.png','wassat-grey.png',1),(19,':dry:','ermm.png','ermm-grey.png',1),(20,':ermm:','ermm.png','ermm-grey.png',0),(21,':lol:','grin.png','grin-grey.png',1),(22,':sick:','sick.png','sick- grey.png',1),(23,':silly:','silly.png','silly-grey.png',1),(24,':y32b4:','silly.png','silly-grey.png',0),(25,':blink:','blink.png','blink-grey.png',1),(26,':blush:','blush.png','blush-grey.png',1),(27,':kiss:','kissing.png','kissing-grey.png',1) ,(28,':rolleyes:','blink.png','blink-grey.png',0),(29,':woohoo:','w00t.png','w00t-grey.png',1),(30,':side:','sideways.png','sideways-grey.png',1),(31,':S','dizzy.png','dizzy-grey.png',1),(32,':s','dizzy.png','dizzy-grey.png',0),(33,':evil: ','devil.png','devil-grey.png',1),(34,':whistle:','whistling.png','whistling-grey.png',1),(35,':pinch:','pinch.png','pinch-grey.png',1),(36,':p','tongue.png','tongue-grey.png',0),(37,':D','laughing.png','laughing-grey.png',0); UPDATE 'jos_fb_messages_text' set message = replace(message,'joomlaboard','fireboard');

c) Check for errors. If there is an error, phpMyAdmin stops executing code from that line onwards, so 1st fix the error, 2nd re-run the code from line that produced the error. Most likely the error is 'Duplicate entry (something) for key (somekey)':

Duplicate entry for key error means that there are entries that have the same value in column that is beeing set as key e.g. you can't have two posts with id 5 in jos_fb_messages as we are setting id as primary key for that table. You can manualy look up and delete or change the entry that produces error to value that doesn't exist yet.

To let myql fix errors for you, change all ALTER TABLE statements that produce errors to ALTER IGNORE TABLE. But this means you will loose entries with 'already used' key. If IGNORE is specified, then for rows with duplicates on a unique key, only the first row is used; the others are deleted.

If you get 'Duplicate key name (somename)' - this is different error. It means that key with that name already exists and that probably you can skip that line of above code.

THIS FIX REQUIRES SOME MYSQL KNOWLEDGE. DO NOT TRY TO DO ANYTHING IF YOU DON'T KNOW WHAT AND HOW THE ABOVE CODE WORKS.
IF YOU ARE NOT FAMILIAR WITH MYSQL QUERIES, GET SOMEONE THAT DOES OR LEAVE IT ALONE.

Edit: moved to first post.

Edit: moved to first post.

Does the code above fix this issue ? www.bestofjoomla.com/component/option,co...6/limitstart,6/#9852

Not, I'm afraid

kauselot wrote:
I wonder how this got missed:

By upgrade from Joomlaboard tables that are copied from joomlaboard DON'T GET UPDATED AT ALL. as CREATE TABLE IF NOT EXISTS lines stops right there. Result? No indexes, no additional fields (group_id, uhits..).

I hope I got it all - developers please check! This is also reason for those big speed degradations. Please change prefix mos to jos for those that started with joomla

For upgrade use some manager (PhpMyAdmin) as key creation stops on duplicate keys - delete those (Mysql experts, please add some direct solution):

ALTER TABLE `mos_fb_attachments` ADD PRIMARY KEY ( `mesid` );
ALTER TABLE `mos_fb_categories` ADD PRIMARY KEY ( `id` );
ALTER TABLE `mos_fb_categories` ADD INDEX ( `parent` );
ALTER TABLE `mos_fb_categories` ADD INDEX `published_pubaccess_id` ( `published` , `pub_access` , `id` );
ALTER TABLE `mos_fb_messages` ADD PRIMARY KEY ( `id` );
ALTER TABLE `mos_fb_messages` ADD INDEX (`thread`);
ALTER TABLE `mos_fb_messages` ADD INDEX (`parent`);
ALTER TABLE `mos_fb_messages` ADD INDEX (`catid`);
ALTER TABLE `mos_fb_messages` ADD INDEX (`ip`);
ALTER TABLE `mos_fb_messages` ADD INDEX (`userid`);
ALTER TABLE `mos_fb_messages` ADD INDEX (`time`);
ALTER TABLE `mos_fb_messages` ADD INDEX (`locked`);
ALTER TABLE `mos_fb_messages` ADD INDEX `hold_time` (`hold`,`time`);
ALTER TABLE `mos_fb_messages_text` ADD PRIMARY KEY ( `mesid` );
ALTER TABLE `mos_fb_moderation` ADD PRIMARY KEY ( `catid` , `userid` );
ALTER TABLE `mos_fb_sessions` ADD PRIMARY KEY ( `userid` );
ALTER TABLE `mos_fb_smileys` ADD PRIMARY KEY ( `id` );
ALTER TABLE `mos_fb_subscriptions` ADD INDEX (`thread`);
ALTER TABLE `mos_fb_subscriptions` ADD INDEX (`userid`);
ALTER TABLE `mos_fb_users` ADD `group_id` INT( 4 ) DEFAULT '1' NOT NULL AFTER `karma_time` ,
ADD `uhits` INT( 11 ) DEFAULT '0' NOT NULL AFTER `group_id` ;
ALTER TABLE `mos_fb_users` ADD PRIMARY KEY ( `userid` );
ALTER TABLE `mos_fb_users` ADD INDEX (`group_id`);
ALTER TABLE `mos_fb_whoisonline` ADD PRIMARY KEY ( `id` );
ALTER TABLE `mos_fb_whoisonline` ADD INDEX (`userid`);


BTW - mos prefix should be made optional also in 100 to 101 upgrade sql & those lines are wrong, as they update e.g: ALTER TABLE `jos_attachments` ADD INDEX `mesid` (`mesid`);
It is jos_sb_attachments or mos_sb_attachments (and so on.. add sb after jos!

All of these worked except for any ADD PRIMARY Key queries.

Overall - nothing really changed.

The Fireboard forum - as upgraded from a Joomlaboard is pretty messed
up. Until I can fix this myself or see some new versions, it is back
to the joomlaboard...

Complete (as far as I know) upgrade comes in 3rd post in this thread. Made a big difference on my instalation.

Edit: moved last version of upgrade to the first post to avoid confusion.

kauselot wrote:
Complete (as far as I know) upgrade comes in 3rd post in this thread. Made a big difference on my instalation.

Edit: moved last version of upgrade to the first post to avoid confusion.

Followed the SQL Upgrade to the letter --

I know my way around PHPMyAdmin and so far these SQL suggestions
have messed things up even more.

Will cross my fingers for Fireboard 1.02

For instance...

Follow-up on a thread from a JB import:

"An unknown SQL Error occured and your message was not posted. If the problem persists, please contact the administrator."

I know my way around PHPMyAdmin and so far these SQL suggestions

have messed things up even more.

All I did is upgrade database structure to reflect the one created on fresh install.

Works fine here and I'm sorry if it doesn't work for you. But I'm 100% sure it didn't mess anything, unless Fireboard database structure created on fresh install is wrong.