500- Internal Server Error

We've no documentation for creating fieldtype plugins at this time. Yes, CB Query Field is a fieldtype plugin. I recommend using CB Gravatar Field as your starting point for a fieldtype plugin as it extends a core fieldtype to add its own custom functionality, which is what you'll be needing to do (extend the editor fieldtype).

Still looking for solution to the Community Builder database limitations and came across some old postings on the forum and wondering if relevant to my issue?

This post says it is from 6 years and 2 months ago so must have been an old version of CB but still sounds relevant?

“When building a large community with many user-registration I encountered a mayor structural flaw in Community Builder.

Because all CB-fields are added in one Table called "comprofiler". You get a serious restriction in the total amount of fields you can add!

I've reached that total amount of data in one Table, as you can see in the code-block below!


[code:1]moscomprofilerFields::«»store failed: CBSQLupgrader::changeColumn (ADD) of Table #__comprofiler Column cb_5c3communitynaam failed with SQL error: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs SQL=ALTER TABLE `jos_comprofiler`\n ADD `cb_5c3communitynaam` varchar(255) DEFAULT NULL Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs SQL=ALTER TABLE `jos_comprofiler`\n ADD `cb_5c3communitynaam` varchar(255) DEFAULT NULL[/code:1]

As it says, i've reached the maximum ammount of field-data a table can contain.

In order to let Community Builder evolve, we maybe need to change this data-structure dramaticly!
Because nothing seems to be joined, this reaches serious limitations.


Yes, I've reached the limit of Community Builder.
But this doesn't have to be a limitation of CB!


Perhaps there is a sollution to this:
You can let Community Builder build a new database-table for each new Tab that is created within the CB admin.
Because all information is then devided by tabs, and so, all data-fields containing this tab are stored in different database-tables, you minimize the possibility of reaching this database-entry-limit.

Please feel free to discus this!
And hopefully the development team will have a look at this important issue.”

I am wondering if this is same issue as mine?

I saw another post that seems to say the problem would be fixed in future version of CB? In this post, it also suggests a workaround?

“MySql has a limit of max-sizes of fields in a row of 64 kilobytes.

With varchar(255) types, this means maximum 256 fields of type text.

This is not a design flaw, it's a limit for that field type.

That said there is an easy cure in CB 1.2 RC3 until we remove that limit in next CB version.

Open file:

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

search for:

Code:

varchar(255)

within field type 'text' and change that one to:

Code:

text

then go to CB -> tools -> check CB database -> fix.

because text is outside the row in MySql, it uses only 4 bytes instead of 256, so you can now store 30'000 such fields instead of 256... Should be enough for some time.

Don't forget to do that change in each new version until we make the fields SQL typing available in a future version.”

Would this last suggestion be something I should pursue? Essentially, it seems like from everything that has been told to me previously, I need to find some way to store some of my user’s data outside of the CB comprofiler database, correct? It was suggested that I look at various form solutions and I have done that. Some are just not compatible with CB and some just don’t work or are too complicated for me to get to work. I have tried Easy Form Builder, Form Maker, Uniform, RSForm, Fabrik, Content Builder, ProForms, FlexiContent and others. Still haven’t found a solution. In my search, I came across these previous posts pertaining to similar issues?

There is no way to have a CB Field store it’s data outside of the Comprofiler database? Is there any way to integrate a regular Joomla field that stores data in the Joomla database outside of CB database? It just seems like there should be plug-in for this or a parameter setting somewhere that would simplify this issue? Is there any html code that I could use for creating and displaying a form field on a CB tab that would store data outside of CB database??

Data can be stored outside of _comprofiler. You just need a fieldtype plugin designed for it. A fieldtype plugin can specify what database table its information is stored in. This will allow getFields API to pull it appropriately, but queries to _comprofiler won't build this information.

You're looking for simple solutions. There isn't one. You need to dig into code and create a solution, because what you want does not exist out of the box. You're hitting standard database limitations. We've no workaround for this as it's just how SQL works.

We'd like to improve out field database structure, but right now that just is not an option. I maybe able to create a plugin later down the road that allows external field value storage, but at this time we have no such plugin.

You can pull external information and display it as a field value using CB Query Field. I've already explained this possible solution to you among a dozen others. None of them are going to be simple solutions. They're all going to require some form of coding.