[SOLVED] Will CB 1.2.2 Upgrade Affect CBSubs?

9 years 5 months ago #132346 by SusanC
My site is using Joomla 1.5.15, PHP version 5.1.4, with Community Builder 1.2.1 and CBSubs 1.0.3. CBSubs was indeed a bit tricky when we first installed it, yet I've gradually been learning about all its various settings and things seem to be working pretty well so far. I don't want to "rock the boat," but definitely would like to try out the Facebook and Twitter Plugins. Guess I'm nervous about the upgrade, because I'm not completely clear on exactly how CB and CBSubs relate to each other. So, can anyone tell me, if I upgrade CB from 1.2.1 to 1.2.2, could doing so negatively affect my CBSubs settings or installation in any way? Is there any reason I shouldn't do it, or is it best to just go ahead and perform the upgrade to CB 1.2.2?

Post edited by: krileon, at: 2010/05/17 20:51
9 years 5 months ago #132361 by nant
You should be able to upgrade without losing anything.

Upgrading from CB 1.2.1 to CB 1.2.2 is simple on a Joomla 1.5 environment. Just install CB 1.2.2 component and modules right over existing ones - nothing will be lost and all plugins and settings should be kept intact.

Always make a backup first - just in case!
9 years 5 months ago #132575 by SusanC
All installs went well. Checking CB Database was all green & up to date. However, checking CB User Fields Database threw out red "Table jos_comprofiler does not exist." Using PHPMyAdmin, I can see the table "jos_comprofiler" is indeed in there. I did an additional backup of that DB, then tried CB Tools' "dry run," which was all green & successful, but I can see it saying it creates a table "jos_comprofiler" and I'm concerned about ending up with TWO tables, as that may not be a good thing. Wonder if a DB prefix issue has something to do with it, but I don't think I've used Joomlapack recently. I attached a text file of a log I kept during this process, FYI. So my question is, should I proceed past the dry run and go ahead and click to fix all the database differences? Thanks, -susan

Attachment SusanC_table_jos.txt not found



Post edited by: SusanC, at: 2010/05/08 23:32

Post edited by: SusanC, at: 2010/05/09 15:02
Attachments:
9 years 5 months ago #132780 by SusanC
Update: Going past the dry run, after clicking to actually fix the database differences, I noticed all is green, except for the additional custom fields I had previously (before upping from 1.2.1 to 1.2.2) added to our users' profile. This is on a live site. Can anyone tell me if this is normal behavior for CB?

CB fields data storage Database adjustments errors:
CBSQLupgrader::createTableof Table jos_comprofiler failed with SQL error: Table 'jos_comprofiler' already exists SQL=CREATE TABLE `jos_comprofiler` ( `cb_expirationdate` date DEFAULT NULL ) ENGINE=MyISAM
CREATE TABLE `jos_comprofiler` ( `cb_expirationdate` date DEFAULT NULL ) ENGINE=MyISAM
CBSQLupgrader::createTableof Table jos_comprofiler failed with SQL error: Table 'jos_comprofiler' already exists SQL=CREATE TABLE `jos_comprofiler` ( `cb_chartermember` tinyint(3) unsigned DEFAULT NULL ) ENGINE=MyISAM
CREATE TABLE `jos_comprofiler` ( `cb_chartermember` tinyint(3) unsigned DEFAULT NULL ) ENGINE=MyISAM
CBSQLupgrader::createTableof Table jos_comprofiler failed with SQL error: Table 'jos_comprofiler' already exists SQL=CREATE TABLE `jos_comprofiler` ( `cb_membershiptype` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CREATE TABLE `jos_comprofiler` ( `cb_membershiptype` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CBSQLupgrader::createTableof Table jos_comprofiler failed with SQL error: Table 'jos_comprofiler' already exists SQL=CREATE TABLE `jos_comprofiler` ( `cb_favoritecomposers` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CREATE TABLE `jos_comprofiler` ( `cb_favoritecomposers` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CBSQLupgrader::createTableof Table jos_comprofiler failed with SQL error: Table 'jos_comprofiler' already exists SQL=CREATE TABLE `jos_comprofiler` ( `cb_recordingsilove` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CREATE TABLE `jos_comprofiler` ( `cb_recordingsilove` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CBSQLupgrader::createTableof Table jos_comprofiler failed with SQL error: Table 'jos_comprofiler' already exists SQL=CREATE TABLE `jos_comprofiler` ( `cb_geographicalarea` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CREATE TABLE `jos_comprofiler` ( `cb_geographicalarea` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CBSQLupgrader::createTableof Table jos_comprofiler failed with SQL error: Table 'jos_comprofiler' already exists SQL=CREATE TABLE `jos_comprofiler` ( `cb_mystyles` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CREATE TABLE `jos_comprofiler` ( `cb_mystyles` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CBSQLupgrader::createTableof Table jos_comprofiler failed with SQL error: Table 'jos_comprofiler' already exists SQL=CREATE TABLE `jos_comprofiler` ( `cb_state` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CREATE TABLE `jos_comprofiler` ( `cb_state` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CBSQLupgrader::createTableof Table jos_comprofiler failed with SQL error: Table 'jos_comprofiler' already exists SQL=CREATE TABLE `jos_comprofiler` ( `cb_myinstrument` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CREATE TABLE `jos_comprofiler` ( `cb_myinstrument` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CBSQLupgrader::createTableof Table jos_comprofiler failed with SQL error: Table 'jos_comprofiler' already exists SQL=CREATE TABLE `jos_comprofiler` ( `cb_country` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CREATE TABLE `jos_comprofiler` ( `cb_country` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CBSQLupgrader::createTableof Table jos_comprofiler failed with SQL error: Table 'jos_comprofiler' already exists SQL=CREATE TABLE `jos_comprofiler` ( `cb_technologyiuse` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CREATE TABLE `jos_comprofiler` ( `cb_technologyiuse` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CBSQLupgrader::createTableof Table jos_comprofiler failed with SQL error: Table 'jos_comprofiler' already exists SQL=CREATE TABLE `jos_comprofiler` ( `cb_professionalaffiliations` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CREATE TABLE `jos_comprofiler` ( `cb_professionalaffiliations` varchar(255) DEFAULT NULL ) ENGINE=MyISAM
CBSQLupgrader::createTableof Table jos_comprofiler failed with SQL error: Table 'jos_comprofiler' already exists SQL=CREATE TABLE `jos_comprofiler` ( `cb_mtnacertification` tinyint(3) unsigned DEFAULT NULL ) ENGINE=MyISAM
CREATE TABLE `jos_comprofiler` ( `cb_mtnacertification` tinyint(3) unsigned DEFAULT NULL ) ENGINE=MyISAM
CBSQLupgrader::createTableof Table jos_comprofiler failed with SQL error: Table 'jos_comprofiler' already exists SQL=CREATE TABLE `jos_comprofiler` ( `cb_mybiography` mediumtext ) ENGINE=MyISAM
CREATE TABLE `jos_comprofiler` ( `cb_mybiography` mediumtext ) ENGINE=MyISAM

Click here to Show details
Table #__comprofiler Column avatar structure is up-to-date.
Table #__comprofiler Column avatarapproved structure is up-to-date.
Table #__comprofiler Column hits structure is up-to-date.
Table #__users Column registerDate structure is up-to-date.
Table #__users Column lastvisitDate structure is up-to-date.
Table #__comprofiler Column lastupdatedate structure is up-to-date.
Table #__users Column username exists but is not of strict type, so not checked.
Table #__users Column name exists but is not of strict type, so not checked.
Table #__comprofiler Column firstname structure is up-to-date.
Table #__comprofiler Column middlename structure is up-to-date.
Table #__comprofiler Column lastname structure is up-to-date.
Table #__users Column params exists but is not of strict type, so not checked.
Table #__users Column username exists but is not of strict type, so not checked.
Table #__users Column name exists but is not of strict type, so not checked.
Table #__comprofiler Column firstname structure is up-to-date.
Table #__comprofiler Column middlename structure is up-to-date.
Table #__comprofiler Column lastname structure is up-to-date.
Table #__users Column username exists but is not of strict type, so not checked.
Table #__users Column name exists but is not of strict type, so not checked.
Table #__comprofiler Column firstname structure is up-to-date.
Table #__comprofiler Column middlename structure is up-to-date.
Table #__comprofiler Column lastname structure is up-to-date.
Table #__users Column username exists but is not of strict type, so not checked.
Table #__users Column name exists but is not of strict type, so not checked.
Table #__comprofiler Column firstname structure is up-to-date.
Table #__comprofiler Column middlename structure is up-to-date.
Table #__comprofiler Column lastname structure is up-to-date.
Table #__users Column username exists but is not of strict type, so not checked.
Table #__users Column name exists but is not of strict type, so not checked.
Table #__comprofiler Column firstname structure is up-to-date.
Table #__comprofiler Column middlename structure is up-to-date.
Table #__comprofiler Column lastname structure is up-to-date.
Table #__users Column email exists but is not of strict type, so not checked.
Table #__users Column password structure is up-to-date.
Table #__comprofiler Column cb_streetaddress exists but is not of strict type, so not checked.
Table #__comprofiler Column cb_postalcode exists but is not of strict type, so not checked.
Table #__comprofiler Column cb_contactphone exists but is not of strict type, so not checked.
Table #__comprofiler Column cb_mywebsite structure is up-to-date.
Table #__comprofiler Column cb_twitter structure is up-to-date.
9 years 5 months ago #132786 by beat
Looks like the formal description of the database records for those fields in red is not correct.

What field-types are they ?

At first glance, it looks like either:

- your database prefix is not jos_ anymore, and that in table comprofiler_fields the column "table" has hardcoded jos_comprofiler instead of #__comprofiler ?

- or an XML file like plugin/user/cb.core.xml hasn't been updated correctly.

Beat - Community Builder Team Member

Before posting on forums: Read FAQ thoroughly -- Help us spend more time coding by helping others in this forum, many thanks :)
CB links: Our membership - CBSubs - Templates - Hosting - Forge - Send me a Private Message (PM) only for private/confidential info
9 years 5 months ago #132787 by beat
To be complete: If it's that table that has these wrong entries:

I've seen site migration tools auto-change by error the #__comprofiler content in database contents to jos_comprofiler !!!

So if you migrated your site from joomla 1.0 to 1.5, or moved it using one of these migration tools, you should report this bug to that tool developer as well.

Beat - Community Builder Team Member

Before posting on forums: Read FAQ thoroughly -- Help us spend more time coding by helping others in this forum, many thanks :)
CB links: Our membership - CBSubs - Templates - Hosting - Forge - Send me a Private Message (PM) only for private/confidential info
Moderators: beatnantkrileon
Time to create page: 0.407 seconds
Facebook Twitter Google LinkedIn