[SOLVED] CB Activity 3 RC1

Installing the new plugin gives me the following message:

Specified key was too long; max key length is 1000 bytes SQL=CREATE TABLE `jos_comprofiler_plugin_activity_comments` ( `id` int(11) unsigned NOT NULL auto_increment, `user_id` int(11) NOT NULL DEFAULT 0, `type` varchar(255) NOT NULL DEFAULT '', `subtype` varchar(255) DEFAULT NULL, `item` varchar(255) DEFAULT NULL, `parent` varchar(255) DEFAULT NULL, `message` text, `date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `params` text, PRIMARY KEY (`id`), KEY `user_id` (`user_id`), KEY `type` (`type`), KEY `subtype` (`subtype`), KEY `item` (`item`), KEY `parent` (`parent`), KEY `date` (`date`), KEY `user_id_date` (`user_id`, `date`), KEY `type_item_date` (`type`, `item`, `date`) )AUTO_INCREMENT=1, ENGINE=MyISAM

ENGINE=MyISAM

You never migrated your table engine. Run the database tools in CB > Tools to migrate to InnoDB then re-install CB Activity. No one should be using MyISAM at this point. Please also see the below post regarding changes in CB Activity and not yet implemented features.

www.joomlapolis.com/forum/6-news-and-publicity/229413-cb-activity-30-preview?start=6#262964

I do not see that option in the CB tools. When I go into the "Check CB Plugins Database" it comes up with the following:

CB plugin "CB Activity" database structure differences:
Table #__comprofiler_plugin_activity_comments does not exist
Table #__comprofiler_plugin_activity_hidden does not exist
Table #__comprofiler_plugin_activity_actions does not exist
Table #__comprofiler_plugin_activity_emotes does not exist

When I click on fix it gives me the same message as above.

Not sure where I upgrade to InnoDB

Thanks

You need to run all of the database tools and apply their fixes. Specifically be sure to run "Check Community Builder Database".

Everything is green (no fixes suggested) for all database checks except for the one I mentioned previously in the Plugins check.

Check your database and ensure your Joomla _users table has also been changed to InnoDB. CB matches Joomlas _users table. If Joomla is stuck on MyISAM then something went wrong with your Joomla install/upgrade and you'll need to manually change the engine. The key length of index on MyISAM is too short for CB Activity indexes, which are needed to maintain performance. Will review reducing some of the indexes as needed for RC2, but your table engine really needs fixed.