Hello,

We are experiencing a very similar issue as the user in this thread www.jms2win.com/forum?id=2510&catid=25&func=fb_pdf

It seems that any Community Builder user profile fields that are added to our our slave site user profile after deployment are configured to connect to the incorrect _comprofiler table under the 'slave' db table prefix as opposed to the 'master' db table prefix as they should. We are sharing both community builder tables and users (exactly as the user above describes).

Error:
moscomprofiler::store failed: Unknown column 'cb_newcontactfield' in 'field list' SQL=UPDATE `tblAZCI_comprofiler` SET `user_id`=42,`firstname`='Admin',`lastname`='User',`hits`='0',`message_last_sent`='0000-00-00 00:00:00',`message_number_sent`='0',`avatarapproved`='1',`approved`=1,`confirmed`=1,`registeripaddr`='',`cbactivation`='',`banned`='0',`acceptedterms`='0',`lastupdatedate`='2011-07-25 16:17:49',`website`='',`location`='',`occupation`='',`interests`='',`company`='',`address`='',`city`='',`state`='AZ',`zipcode`='',`country`='',`phone`='',`fax`='',`cb_misc`='',`cb_miscpostazcislave`='1',`cb_newcontactfield`='' WHERE id='42'



Additionally we encounter a similar issue when attempting to add user profile fields to Community Builder from within the slave site back end admin interface:

Error:
moscomprofilerFields::store failed: CBSQLupgrader::changeColumn (ADD) of Table #__comprofiler Column cb_newcontactfield failed with SQL error: 'db375493331.tblAZCI_comprofiler' is not BASE TABLE SQL=ALTER TABLE `tblAZCI_comprofiler`\n ADD `cb_newcontactfield` varchar(255) DEFAULT NULL 'db375493331.tblAZCI_comprofiler' is not BASE TABLE SQL=ALTER TABLE `tblAZCI_comprofiler`\n ADD `cb_newcontactfield` varchar(255) DEFAULT NULL

We have checked the Joomla file/folder permissions and cannot seem to get around this issue. Changing file permissions seems to be what solved the issue for the user above but we are unclear on specifically what folders/files needed the permission changes and what steps were taken after changing such permissions to resolve their issue (did the issue resolve itself at that point? or did they have to create a new slave site with the permissions changed?)


Thanks,

John

When you share an extension, MySQL create a snapshot of the fields that are used between the tables.
Therefore, if you add fields in the website where the table are physically created, then you have to "uninstall" the CB in the website where it is shared and re-share the CB to let MySQL.

When an extension is shared, its content is in the website where the physical tables are created.
So you can uninstall the "shared extension" and re-share it to let MySQL rebuild the snapshot of the table layout.

Hello,

Thank you very much for the reply. When we follow your instructions and run an uninstall of the slave site "comprofiler" component for a slave site using JMS Multisites Tools menu our entire Joomla MySQL database gets erased. This includes all master and slave tables; there are literally no tables left in the database requiring us to have to completely restore from .sql backup. Is there any way around this behavior so that we can safely uninstall re-install comprofiler for a slave site as described?

**Update
We are using Joomla 1.7 when encountering this loss of database when uninstalling a shared component from within MultiSites. This does not seem to be occurring when we follow your instructions using Joomla 1.5 and re-sharing does indeed enable the new profile fields within the slave site.

Can you let us know if this is a known issue with Joomla 1.6, 1.7?

Thanks Again,

John

I don't know what you did but if you have verified that the extension is effectivelly a link, it should only remove the link and not the data.
What you described is that you have uninstall the website where the data are physically stored and not the one where you have the link.

I will retest that with Joomla 1.7.
As joomla never provide any ascending compatibility and that their version number do not reflect that they are compatible with earlier version, perhaps that joomla changed something that affect that. I will restest it.
Understand that retest everything at each release of Joomla take a lot of time and we just need time.

Hello,

Thanks again for the reply. We followed these steps:

From master site, navigate to Multisites->Tools
Choose slave site to uninstall linked comprofiler from
Execute removal of comprofiler from slave site

Upon execution of action the website disappears and all database tables are deleted. I have attached a PDF containing screenshots of each step.

Thanks Again,

John

Received an error attaching a PDF to the last message ... this is accessible here:
Screenshots PDF

Thanks!