Agreed. The benefits of this component are not clear to me.
Here is a query to insert approved, non-banned, "Staff" (JACL) users into the contacts table - YMMV!:
"
INSERT INTO jos_contact_details ( name, address, suburb, state, country, email_to, telephone, [image], imagepos, user_id, published, catid )
SELECT [firstname] & " " & [Lastname] AS Expr1, jos_comprofiler.address, jos_comprofiler.city, jos_comprofiler.state, jos_comprofiler.country, jos_users.email, jos_comprofiler.phone, jos_comprofiler.avatar, "top" AS Expr2, jos_comprofiler.user_id, "1" AS Expr3, 12 AS Expr4
FROM jos_users INNER JOIN jos_comprofiler ON jos_users.id = jos_comprofiler.user_id
WHERE (((jos_comprofiler.firstname) Is Not Null And (jos_comprofiler.firstname)>="A") AND ((jos_comprofiler.banned)=0) AND ((jos_comprofiler.approved)=1) AND ((jos_comprofiler.confirmed)=1) AND ((jos_users.block)=0) AND ((jos_users.usertype)="Staff"));
"
Maybe CB_Contacts needs to BREAK from the standard contacts component, and read directly from comprofiler, rather than being compatible?
Thanks, all!