i have the same problems!

beat wrote:

delete field and tab, or even, delete completely comprofiler_fields and comprofiler_tabs sql table in phpmyadmin

- deleting completely comprofiler_fields and comprofiler_tabs sql table will make the 'check CB database' not properly functioning. therefore i just empty the comprofiler_fields and comprofiler_tabs sql table

beat wrote:

then do tools->check CB database -> fix db to recreate them.

- it will load CB default tabs and field

result = error on profile save is still there

beat wrote:

It it still doesn't work, Try adding the sample data in CB tools before creating your new field (after recreating tables with step above)

result = error on profile save is still there

- i have repeated above step again, this time with comprofiler_fields_values

result = error on profile save is still there

- unpublish all cb plugin except language, template and cb core

result = error on profile save is still there

Alright I tried everything suggested and still nothing. I did figure out though that if you go into the database and add the field manually to jos_comprofiler then everything saves ok. So that is a simple work around but tedious none the less. It's something between the creation of a new field and the database not creating the appropriate column in jos_comprofiler.

fresh install joomla 1.0.15
fresh install cb 1.2RC

login to frontend , edit profile, save - OK

create new cb field at backend (fieldname = cb_sbsignature), save

open profile page (frontend) , edit profile, save - ERROR

i went to phpmyadmin, open jos_comprofiler, the new fieldcolumn was not created in it.

i created the fieldcolumn manually, then the error on profile save is gone!!

Post edited by: fungkur, at: 2008/06/02 20:25

Well I gave it one more shot in the dark and it turns out that my fix was moving from PHP4 to PHP5. No problems to report so far after that change. Not sure why but it might just be the host provider I am using.

THANKS FOR ALL THE HELP GUYSB) AWESOME PRODUCT and I'm really happy to see CB1.2 out.

Post edited by: georges, at: 2008/06/02 23:14

upgraded to php5 but the error is still there