|
Community Builder Field Compatibility 14 Years, 6 Months ago
|
Karma: 0
|
Can I first say how awesome this component is? I'm completing my first implementation now and this thing rocks!
However, I've run into a couple of snags, one of which is with Community Builder. It works great with the default fields. But if fields are added after creating a slave site, something like this will appear when trying to add data to those fields: | Code: |
moscomprofiler::store failed: Unknown column 'cb_address' in 'field list' SQL=UPDATE `grp_comprofiler` SET `user_id`=65,`firstname`='Firstname',`lastname`='Lastname',`hits`='0',`message_last_sent`='0000-00-00 00:00:
00',`message_number_sent`='0',`avatarapproved`='1',`approved`=1,`confirmed`=1,`registeripaddr`='72.201.79.161',`cbactivation`='',`banned`='0',`acceptedterms`='0',`lastupdatedate`='2009-11-11 07:50:
16',`jboloallowall`='0',`cb_address`='123 Some Pl.',`cb_city`='',`cb_state`='',`cb_postalcode`='',`cb_country`='',`cb_homephone`='',`cb_celphone`='' WHERE id='65'
|
I have tried adding fields from the master site and the slave site, but it looks like something isn't talking somewhere. I've also tried it with third-party plug-ins disabled. The fields update across the sites in the admin back-end correctly (i.e. I can see the fields I created in the master site appear in the slave site).
Does the CB database need to be completely designed before creating slave sites?
Thanks again! |
|
|
|
Last Edit: 2009/11/12 00:28 By newbandon.
|
|
|
Re:Community Builder Field Compatibility 14 Years, 6 Months ago
|
Karma: 54
|
|
Try to re-install Community Builder directly in the slave site to see if the table are correctly created.
Compare also the DB table layout between you "master" and the "grp_" slave site.
Normally they should be identical.
|
|
|
|
|
|
|
Re:Community Builder Field Compatibility 14 Years, 6 Months ago
|
Karma: 0
|
The tables appear to be exactly the same.
I just tried uninstalling and re-installing (I was nervous about the plugins, but they all stayed), but no luck. Same errors.
When the new fields are not published, the integration works great... 
Any other ideas? |
|
|
|
|
|
|
Re:Community Builder Field Compatibility 14 Years, 6 Months ago
|
Karma: 54
|
|
What do you mean by "new fields are not published" ?
Can you provide a detailled scenario that show how to reproduce the error message.
We are not a CB specialist. We need a very detailled scenarion to reproduce it.
|
|
|
|
Last Edit: 2009/11/12 09:20 By edwin2win.
|
|
|
Re:Community Builder Field Compatibility 14 Years, 6 Months ago
|
Karma: 0
|
|
Sure. Here's the exact problem.
For this test, I added a single field to CB. It can be a text field, date, or anything. But let's use a a date for this example.
In CB on the master site, I added a date field called "cb_birthday" and published it.
The field instantly appears in the master site and the slave site and users now have that field available in their profile.
However, when someone tries to register or update their profile with that field, the previous error appears. If someone is updating their profile, the message appears and no updates happen. If someone is registering, the registration goes through, but only with the username and e-mail address; no other fields get processed (i.e. name, birthday).
When the field is unpublished (i.e. turned off) in the field list, CB works fine in both the master and slave site. It's definition remains in both databases just fine.
I don't know if that helps, but that is the complete process.
Thanks Erwin. You're awesome!
|
|
|
|
|
|
|
Re:Community Builder Field Compatibility 14 Years, 6 Months ago
|
Karma: 54
|
|
YES this can help us to try reproduce it.
Can you also tell us if the slave site have just install the CB or does they share the CB ?
|
|
|
|
|
|
|
Forum
