Row size too large

I got Row size too large when I tried to make a save a new image field

The field was actually created anyway but when I try to upload and SAVE the image I get 1054 - Unknown column 'cb_myimage in 'field list'
Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

Since this problem I have been getting more problems with cb_fields not saving properly.
I have to change tables or something?
Can you explain exactly do I do?

Thanks

You've hit row size limits for your database. You probably have too many fields. How many fields do you currently have?

I have 229 cb_fields
I need more?

Thanks

You shouldn't be hitting limits with only 229 fields, but it'll depend on what types of fields you are using.

It's possible this is entirely due to wrong collation on the database table. Using phpmyadmin navigate to _comprofiler table and click Operations then under "Table options" set "Collation" to "utf8mb4_unicode_ci" and select the "Change all column collations" checkbox then click Go.

Aside from that please search the forums as we've extensively covered this topic. We won't have a complete fix to this until we redesign the _comprofiler table and that's not happening until CB 3.x where we want to just move the fields to Joomla profile storage.

I got error changing the field collation to "utf8mb4_unicode_ci"

Error
Static analysis:

2 errors were found during analysis.

Missing comma before start of a new alter operation. (near "DEFAULT CHARSET" at position 33)
Unrecognized alter operation. (near "DEFAULT CHARSET" at position 33)
SQL query: Edit Edit

ALTER TABLE `dfiffg_comprofiler` DEFAULT CHARSET=utf8mb4 COLLATE utf8mb4_unicode_ci;

MySQL said: Documentation

#1067 - Invalid default value for 'message_last_sent'

That's due to our datetime columns not using NULL default yet. We're working on merging and releasing a fix for that to make the database structure compatible with SQL strict mode. There isn't really a simple workaround unless you're experienced with SQL as you'll have to write the SQL to change the collations manually instead of using the phpmyadmin operation.

We should have the database structure fix out sometime this week.