TOPIC: Community Builder Synch

Just trying to get some insight....found this quote from an earlier post in Oct 2010:

"The current DT Register syncs with both CB and JomSocial for the default fields only. When someone registers for the event and creates the user account, the address, city, phone, etc will all be loaded into CB or JomSocial... whatever exists on your site.

Next week, we release the new 2.7 which allows you to sync ALL fields with CB and JomSocial, so you'll be able to gather whatever info you need for the profile as part of the event registration. Also, the new version allows you to set the auto-user creation PER EVENT... and make it optional or required."

What happened to this synch with CB for existing DTRegister Users in 2.7?

Please advise

Configuration >>Profile Sync

thepiston @ 11:35 -- tell us more, I'm really, really hoping it's some magic fix for this issue... please?

@thepiston; sorry guy/gal that would be too obvious a solution set and I am way past that as an answer. Too bad it isn't that simple. There is clearly a glitch or missing code in the application.

Intent was for that integration to occur; IT IS SIMPLY NOT HAPPENING and my post was deliberately written to stir the pot.

Nathan??

thx, ginajack -- so, it's not just me feeling a little miffed that I'm being told to go use the CB Sync tool to sync. Uh, duh... thepiston, we're a bit beyond that at this point and hoping to get an actual response, since this is seriously gumming up the works.

Ok, so I upgraded my CB component as well to 1.3.1 (current version) and performed the CB tools check on the database to find the following error for DT Register - which may explain why the frontend and the backend NO LONGER populate with CB User information as before.......there is NO SYNCH of the information - there is no database linkage.

This error was received both PRIOR and SUBSEQUENT to re-installing the DTregister plugin as a part of 2.7.1d update.

[attachment=0:1lsx167r]<!-- ia0 -->Screen shot 2011-01-06 at 4.53.31 PM.png<!-- ia0 -->[/attachment:1lsx167r]

This completely renders the component invalid and not very useful for existing sites, community organization, databases, registrations, etc.