It would need to use CB API to create the user instead of Joomla API. Our API for doing this is documented below.

www.joomlapolis.com/documentation/279-community-builder/tutorials/18362-registering-a-user-through-cb-api

If they've a Joomla event during that operation you'd be able to probably override the behavior using CB Auto Actions.

Worst case I guess is you'll need to run the synchronize users tool every now and again.

BTW is it still recommended to deactivate standard joomla registration with CB ? or do you override the behavior ?

As long as CBs system plugin is published and the redirect behavior in it was not turned off we will redirect from Joomla registration to ours.

I mean if we have other components trying to create joomla users and send email, what kind of autoaction can I write to be sure all will be in sync with CB ?

We don't have a way to sync like that. They need to be registered through CB. You'd need to be able to replace their registration save behavior with your own.


With CB 3.x we ideally won't have our own registration form anymore. I want to ideally just overrider com_users registration/edit/view layouts with our own custom ones as we want to move away from our custom _comprofiler table to instead just use Joomla's profile data storage. This would allow CB profile display that you're used to while being entirely compatible with core Joomla users. No idea if this will even be possible though and will cross that bridge when the time comes.

They would need their own Joomla event before the user is saved for you to interrupt their process with your own. That's Joomla's event and we can't interrupt that as CBs user store will trigger that as well.