Install Community Builder without automatically importing all the Joomla users

Hi,

Great work on CB - am loving it so far.
I have just installed CB onto an existing website which has about 300 users. These are all Joomla users.
Installing CB into this site and its existing users immediately lets me view these Joomla users through the CB 'User Management' page - great.
I assume though that this means that the users have been 'imported' into CB. And it seems that this happened automatically as part of the install process.

The problem is that this imported the Joomla users into CB before I had any chance to setup the 'Name Style' setting (in Joomla Config > General tab) to capture the Joomla name field as two separate parts - first and last name.

I searched the forum and this advises to use the 'Synchronize Users' tool but I realise that this only splits the names for Joomla users which have not already been imported into CB.

So, is there a way to stop this auto-user-import during install or is there a commonly used, robust workaround?

Thanks for reading this and for helping.

Best,

T

So, is there a way to stop this auto-user-import during install or is there a commonly used, robust workaround?

Nope, you can empty the _comprofiler table and run CB > Tools > Synchronize Users though I guess to force synchronization when ready. Make a backup before doing this.

Thanks @krileon,

I have tried your suggestion and it appears to work well.

I expect that truncating the comprofiler table is only a viable option if this is done straight after install of CB, when the comprofiler table is empty, i.e. before any changes are made to CB or the (CB) users and other objects it controls.

This way, the other CB database tables (which presumably link to comprofiler, e.g. comprofiler_fields, comprofiler_field_values) will not be left containing records which link to something in comprofiler that was just deleted.

Would you agree?

Thanks again for your help.

T

Correct, do not do that regularly as it will delete all CB related data. It is strictly for forcing initial synchronization again on new CB installs.