[#4946] Error 1118 - Error upgrading from CB 1.9 to CB 2.0.4

I think this problem is similar to problem I was having some weeks ago and posted in this forum at www.joomlapolis.com/forum/154-advanced-members-support/227416-the-page-you-requested-is-not-available-when-updating-profile-after-using-editor-text-area-fields?limitstart=0

I moved to a different host, hoping that would resolve the problem and cut the number of fields so that I only have about a quarter of the fields that I had before. Now I am having the same problem when a lot of data is added to a record and have posted again to the forum at www.joomlapolis.com/forum/153-professional-member-support/227895-500-internal-server-error

I think this is same problem I have had and there is no indication here that the problem was resolved. Here is how it was resolved for me for a fews days but now having problem again: I moved to a cloud server with the innodb_page_size = 64K now. The PHP variable upload_max_filesize has been increased to 100m. It apparently worked. No more error messages when inputing multiple paragraphs into a Text Editor field.

This seemed to work for a few days and I was pretty excited but then started getting another error message. "Error, your profile could not be updated."

The tech people at my current host looked into it and ultimately came to same conclusion as my previous host, that this is caused by a limitation of CB and not a hosting issue. Since this is now the second host to say this, I guess this is the case. Here is what my host said this time:

"I have spent quite a bit of time attempting to resolve this. Increasing InnoDB page size did not help unfortunately. After researching this on the Internet I found many topics related to the exact same error, and the proposed solution was to increase the innodb_log_file_size setting. I increased that from 5 MB to 128 MB, yet the issue still remained. The problem itself appears to be due to way the Community Builder database records are structured.

Krileon, of Joomlapolis, had said a couple times to me and to kunarkintir that he thought the problem had to do with how much data we were trying to save in one field: "I believe this is due to you storing a very large amount of text (10+ paragraphs it would seam) into a single field." Apparently, this appears to be a limitation due to the way CB database is currently set up? Maybe that will change with future upgrades of CB. If anyone figures out an answer, I will be eager to hear it but otherwise, will try rebuilding yet once again and seeing if I can work around this CB database limitation.

Target version has been changed from CB 2.0.5 to CB 2.0.6 ? :S

forge.joomlapolis.com/issues/4946

It's a database limitation. We do not have a fix or workaround for this at this time. The ticket has been left open to brainstorm possible solutions. You could change to Barracuda then set the row format to compressed. This further reduces the size of a row and effectively increases its limits. This error can also be caused by innodb_log_file_size being too small, but it's not always the cause. The page size limit can be increased with innodb_page_size, but that can be dangerous and should be done with caution.

I really don't have anything further to suggest at this time. You're just hitting database limitations that CB can't really do anything about. When this happens it's time to rethink how you've configured CB, what you're wanting out of CB, and begin manual database optimizations.

What is Barracuda? I Googled "Barracuda," and got this link:https://community.barracudanetworks.com but not sure what I am looking for??

Thanks!

It's an InnoDB file format.

dev.mysql.com/doc/refman/5.5/en/innodb-file-format.html