Upon upgrade to v. 1.2, it appears that the user search has been broken. Puts out the following error:
unknown column formatname - and a bunch of other stuff

Hi,

I think reggiem is talking about cb advanced search and the sql error looks like this:
[code:1]
Unknown column 'ue.formatname' in 'where clause' SQL=SELECT *, '' AS 'NA' FROM jos_users u, jos_comprofiler ue WHERE u.id=ue.id AND u.block!=1 and ue.approved=1 AND ue.banned=0 AND ue.confirmed=1 AND u.gid IN (29,19,20,21,18, 18, 19, 20, 21, 30,24,23,25, 23, 24, 25) AND ((LOWER(ue.avatar) LIKE '%wd%' OR LOWER(ue.website) LIKE '%wd%' OR LOWER(ue.cb_pbfamily) LIKE '%wd%' OR LOWER(ue.company) LIKE '%wd%' OR LOWER(ue.cb_pbkids) LIKE '%wd%' OR LOWER(ue.cb_position) LIKE '%wd%' OR LOWER(ue.cb_tagcloud) LIKE '%wd%' OR LOWER(ue.cb_pblanguages) LIKE '%wd%' OR LOWER(ue.cb_branch) LIKE '%wd%' OR LOWER(ue.cb_selfdesc) LIKE '%wd%' OR LOWER(ue.address) LIKE '%wd%' OR LOWER(ue.cb_pbjob) LIKE '%wd%' OR LOWER(ue.zipcode) LIKE '%wd%' OR LOWER(ue.cb_companydesc) LIKE '%wd%' OR LOWER(ue.city) LIKE '%wd%' OR LOWER(ue.cb_pbcustomer) LIKE '%wd%' OR LOWER(ue.state) LIKE '%wd%' OR LOWER(ue.cb_pbmotto) LIKE '%wd%' OR LOWER(ue.interests) LIKE '%wd%' OR LOWER(ue.country) LIKE '%wd%' OR LOWER(ue.phone) LIKE '%wd%' OR LOWER(ue.cb_pbfavhead) LIKE '%wd%' OR LOWER(ue.formatname) LIKE '%wd%' OR LOWER(ue.cb_mobile) LIKE '%wd%' OR LOWER(ue.fax) LIKE '%wd%' OR LOWER(ue.cb_companymail) LIKE '%wd%' OR LOWER(ue.cb_agency) LIKE '%wd%' OR LOWER(ue.cb_streetsec) LIKE '%wd%' OR LOWER(ue.cb_plzsec) LIKE '%wd%' OR LOWER(ue.cb_citysec) LIKE '%wd%' OR LOWER(ue.cb_statesec) LIKE '%wd%' OR LOWER(ue.cb_countrysec) LIKE '%wd%' OR LOWER(ue.cb_phonesec) LIKE '%wd%' OR LOWER(ue.cb_mobilesec) LIKE '%wd%' OR LOWER(ue.cb_faxsec) LIKE '%wd%' OR LOWER(ue.hits) LIKE '%wd%' OR LOWER(ue.onlinestatus) LIKE '%wd%' OR LOWER(u.registerDate) LIKE '%wd%' OR LOWER(u.lastvisitDate) LIKE '%wd%' OR LOWER(ue.lastupdatedate) LIKE '%wd%' OR LOWER(ue.connections) LIKE '%wd%' OR LOWER(ue.forumrank) LIKE '%wd%' OR LOWER(ue.forumposts) LIKE '%wd%' OR LOWER(ue.forumkarma) LIKE '%wd%' OR LOWER(ue.cb_pbcar) LIKE '%wd%' OR LOWER(ue.cb_pbdestination) LIKE '%wd%' OR LOWER(ue.cb_xing) LIKE '%wd%' OR LOWER(ue.cb_mb) LIKE '%wd%' OR LOWER(ue.cb_pbshop) LIKE '%wd%' OR LOWER(ue.cb_skype) LIKE '%wd%' OR LOWER(ue.cb_pbibusiness) LIKE '%wd%' OR LOWER(ue.cb_icq) LIKE '%wd%' OR LOWER(ue.cb_pbeat) LIKE '%wd%' OR LOWER(ue.cb_pbiprivate) LIKE '%wd%' OR LOWER(ue.cb_pbbestfriend) LIKE '%wd%' OR LOWER(ue.cb_pbmags) LIKE '%wd%' OR LOWER(ue.cb_pbclothes) LIKE '%wd%' OR LOWER(ue.cb_pbactor) LIKE '%wd%' OR LOWER(ue.cb_pbrestaurant) LIKE '%wd%' OR LOWER(ue.cb_pbmotorbike) LIKE '%wd%' OR LOWER(ue.cb_pbsmell) LIKE '%wd%' OR LOWER(ue.cb_pbtaste) LIKE '%wd%' OR LOWER(ue.cb_pbnoise) LIKE '%wd%' OR LOWER(ue.cb_pbcolor) LIKE '%wd%' OR LOWER(ue.cb_pbwebs) LIKE '%wd%' OR LOWER(ue.cb_pbdrink) LIKE '%wd%' OR LOWER(ue.cb_pbfeeling) LIKE '%wd%' OR LOWER(ue.cb_pbliving) LIKE '%wd%' OR LOWER(ue.cb_pbart) LIKE '%wd%' OR LOWER(ue.cb_pbblogs) LIKE '%wd%' OR LOWER(ue.cb_pbrelax) LIKE '%wd%' OR LOWER(ue.cb_pbsport) LIKE '%wd%' OR LOWER(ue.cb_pbplaces) LIKE '%wd%' OR LOWER(ue.cb_pbmusic) LIKE '%wd%' OR LOWER(ue.cb_pbnews) LIKE '%wd%' OR LOWER(ue.cb_pbfilm) LIKE '%wd%' OR LOWER(ue.cb_pblitrature) LIKE '%wd%')) ORDER BY `lastname` ASC LIMIT 0, 10
[/code:1]

... unfortunately I did not find the query yet.

Ok I found the difference in the comprofiler_fields table:

with CB 1.1 undefined fields like formatname, onlinestatus column name (comprofiler_fields.name) look like:
[code:1]NA[/code:1]

now in CB 1.2
[code:1]formatname[/code:1]

I guess that the author of cb advanced search is checking somewhere against comprofiler_fields.name == NA but did not find it yet...

Me again,

I found 2 places where the query checked comprofiler_fields.name<>'NA' and changed them to check cb_fields.name<>'formatname' AND cb_fields.name<>'onlinestatus' and now the sql query hangs at ue.connection

[code:1]Unknown column 'ue.connections' in 'where clause' SQL=SELECT *, '' AS 'NA' FROM jos_users u, jos_comprofiler ue WHERE u.id=ue.id AND u.block!=1 and ue.approved=1 AND ue.banned=0 AND ue.confirmed=1 AND u.gid IN (29,19,20,21,18, 18, 19, 20, 21, 30,24,23,25, 23, 24, 25) AND ((LOWER(ue.avatar) LIKE '%a%' OR LOWER(ue.website) LIKE '%a%' OR LOWER(ue.cb_pbfamily) LIKE '%a%' OR LOWER(ue.company) LIKE '%a%' OR LOWER(ue.cb_pbkids) LIKE '%a%' OR LOWER(ue.cb_position) LIKE '%a%' OR LOWER(ue.cb_tagcloud) LIKE '%a%' OR LOWER(ue.cb_pblanguages) LIKE '%a%' OR LOWER(ue.cb_branch) ... <snip>[/code:1]

What did you change when updating cb? What I see is that in comprofiler_fields there is a new one called connections which was not there before. Maybe because the new type? Hm.. any api docs, changes around? Or better info, docs how new cb 1.2 search can be used to build a new component