This issue is now fixed in Community Builder 1.2 RC 2.
Community Builder 1.2 RC 2 is a recommended upgrade.



Here comes issue 4:

This got confirmed by a few users:

It's not really a bug, but we will be improving the database checker/upgrader.

In comprofiler_fields table, pluginid and tabid should never be 0 (NULL are fixed correctly by database fix but not 0).

We just saw a system where it was the case, and the upgrader didn't react to that. No idea why that was so, but it's very probably was already so prior to CB 1.2 RC upgrade.

Symptoms:

- Don't see fields in backend fields manager

- Don't see those fields in user profile

- Don't see those fields in users-list (in addition of the above !)

- Possibly cannot register or save user in frontend

- CB database checker returns that all is fine

Workaround:


Execute following 2 queries in phpMyAdmin to bring things back in order, then move out of status tab the fields that you don't want there:

[code:1]
UPDATE jos_comprofiler_fields SET pluginid = 1 WHERE pluginid = 0;
UPDATE jos_comprofiler_fields SET tabid = 21 WHERE tabid = 0;[/code:1]

Related main discussion-thread:

www.joomlapolis.com/component/option,com_joomlaboard/Itemid,38/func,view/catid,50/id,64608/#64608

EDIT: fixed related thread URL

Post edited by: beat, at: 2008/06/04 15:02

Post edited by: beat, at: 2008/07/01 14:02

This issue is now fixed in Community Builder 1.2 RC 2.

Community Builder 1.2 RC 2 is a recommended upgrade.