Problem with Installation or Database?

Hi Kyle,

I have not yet moved to JP hosting. Thought I would rectify this problem before doing so.

I try once more with the varchar columns. Please guide me how to do that.

If that also doesn't work, or even if it works, I am even ready to start developing the site from scratch using the latest versions of Joomla!, CB and its plugins on JP hosting.

I will be purchasing JP hosting tomorrow or Saturday to work on my site through the weekend.

All help are appreciated in advance!

Sincerely yours,

Anis

As an authorative reference, here a very detailed background article:
Understanding the maximum number of columns in a MySQL table

The best way to fix is to edit core.xml found below and change text field, select field, etc.. varchar(255) usage to text. Then run CB tools and it should detect the fields are wrong type and ask if you want to fix.

/components/com_comprofiler/plugin/user/plug_cbcore/cb.core.xml

Another way is to edit _comprofiler and change the "cb_" columns that use varchar to text.

Thanks, Beat and Kyle! I will do as suggested and let you know the results.

Does the number of maximum MySQL columns mean that there IS a limit to the maximum number of profile fields that can be created in CB?

I currently have 133 profile fields of which most are published. I cannot add the 134th one!

I have never encountered this issue before.

Anyway, I will let you know whether the varchar method succeeds.

Sincerely yours,

Anis

Does the number of maximum MySQL columns mean that there IS a limit to the maximum number of profile fields that can be created in CB?

No, it is not a CB limitation. CB does not limit the amount of fields you can create. This is strictly a MYSQL limitation, but there are ways to get around it such as using text column type instead of varchar. We'll be addressing this internally with CB 2.0 though so column size limits won't be hit.

Hi Kyle,

Thank you for your help! I used the second method. That is modifying using phpMyAdmin the type from varchar to text. And it worked! The problem got solved! I added 3 new fields to try and they were all added and no errors were shown.

Additionally, please clarify on the following so that I can be informed before moving to JP hosting:

(1) There is no problem at all with the change to text type, and the site will be running fine as before, right?

(2) Since I changed the database using phpMyAdmin, when I ran the CB Tools from the backend, as the core xml file was not changed, it reported inconsistencies like being "text" type instead of "varchar". This is expected. I just leave them as such, right?

(3) Of course, the easier way should have been changing the core xml file. As you suggested, when CB Tools is run, it will show the incorrect type in the database, and can be fixed. But I couldn't find in which all places the type should be changed into "text". In other words, I really didn't understand what you said exactly. I have attached the core xml file for your review. Would you be kind enough to guide me?

(4) If the core xml file is changed, will future CB upgrades change the type back to "varchar", as I presume the core xml file will be written over?

(5) Do I have to do this field type change if I am moving to JP hosting with MySQL 5.5? If 'yes,' I will keep the engine as MyISAM itself (the current setting) and change the field type to "text" before moving to JP hosting, and then import the database into JP hosting. Please guide me...

I look forward to your help and reply soon.

Sincerely yours,

Anis