Skip to Content Skip to Menu

🎃 Happy Halloween! Treat yourself with an awesome discount on memberships! Get 20% off now with code SPOOKY-2024!

[SOLVED] Upgraded from 1.8.1 to 1.9 - have the following errors when running the CB checks

  • rokkmedia
  • rokkmedia
  • OFFLINE
  • Posts: 22
  • Thanks: 0
  • Karma: 0
11 years 7 months ago - 11 years 7 months ago #222990 by rokkmedia
I have upgraded a joomla 2.5.6 site's community builder from 1.8.1 to 1.9 following the instructions provided with the downloaded files.

installation was fine but when running the cb tool checks 3 of the 4 where issue free. The 'Check Community Builder User Fields Database' link had a list of issues and I continued to fix the issues and got the following errors:

CB fields data storage Database adjustments errors:

CBSQLupgrader::changeColumn (CHANGE `cb_pubdoyouoffertakeaway`) of Table #__comprofiler Column cb_pubdoyouoffertakeaway 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 `lle_comprofiler` CHANGE `cb_pubdoyouoffertakeaway` `cb_pubdoyouoffertakeaway` varchar(255) DEFAULT NULL
ALTER TABLE `#__comprofiler` CHANGE `cb_pubdoyouoffertakeaway` `cb_pubdoyouoffertakeaway` varchar(255) DEFAULT NULL
CBSQLupgrader::changeColumn (CHANGE `cb_pubdoyoudeliver`) of Table #__comprofiler Column cb_pubdoyoudeliver 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 `lle_comprofiler` CHANGE `cb_pubdoyoudeliver` `cb_pubdoyoudeliver` varchar(255) DEFAULT NULL
ALTER TABLE `#__comprofiler` CHANGE `cb_pubdoyoudeliver` `cb_pubdoyoudeliver` varchar(255) DEFAULT NULL
CBSQLupgrader::changeColumn (CHANGE `cb_pubmorethan3veggieoptions`) of Table #__comprofiler Column cb_pubmorethan3veggieoptions 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 `lle_comprofiler` CHANGE `cb_pubmorethan3veggieoptions` `cb_pubmorethan3veggieoptions` varchar(255) DEFAULT NULL
ALTER TABLE `#__comprofiler` CHANGE `cb_pubmorethan3veggieoptions` `cb_pubmorethan3veggieoptions` varchar(255) DEFAULT NULL
CBSQLupgrader::changeColumn (CHANGE `cb_size`) of Table #__comprofiler Column cb_size 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 `lle_comprofiler` CHANGE `cb_size` `cb_size` varchar(255) DEFAULT NULL
ALTER TABLE `#__comprofiler` CHANGE `cb_size` `cb_size` varchar(255) DEFAULT NULL
CBSQLupgrader::changeColumn (CHANGE `cb_bloggersreviewlink`) of Table #__comprofiler Column cb_bloggersreviewlink 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 `lle_comprofiler` CHANGE `cb_bloggersreviewlink` `cb_bloggersreviewlink` varchar(255) DEFAULT NULL
ALTER TABLE `#__comprofiler` CHANGE `cb_bloggersreviewlink` `cb_bloggersreviewlink` varchar(255) DEFAULT NULL


Now when checking this section again I get the following:

CB fields data storage Database structure differences:

Table #__comprofiler Column cb_pubdoyouoffertakeaway type is text instead of varchar(255)
Table #__comprofiler Column cb_pubdoyoudeliver type is text instead of varchar(255)
Table #__comprofiler Column cb_pubmorethan3veggieoptions type is text instead of varchar(255)
Table #__comprofiler Column cb_size type is text instead of varchar(255)
Table #__comprofiler Column cb_bloggersreviewlink type is text instead of varchar(255)


hopefully this is enough information to go on, If there is anybody with the knowledge to fix this it would be really helpful.
Last edit: 11 years 7 months ago by krileon.

Please Log in or Create an account to join the conversation.

  • krileon
  • krileon
  • ONLINE
  • Posts: 48459
  • Thanks: 8280
  • Karma: 1443
11 years 7 months ago #222999 by krileon
CB is trying to change the fields back to varchar, but looks like you changed them to text due to hitting database column size limits. You'll just have to ignore the tools check as it'll want to change them back, but it can't due to your database being at the column size limit.


Kyle (Krileon)
Community Builder Team Member
Before posting on forums: Read FAQ thoroughly + Read our Documentation + Search the forums
CB links: Documentation - Localization - CB Quickstart - CB Paid Subscriptions - Add-Ons - Forge
--
If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
--
If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please send me a private message with your thread and will reply when possible!
--
Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
--
My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
The following user(s) said Thank You: rokkmedia

Please Log in or Create an account to join the conversation.

  • rokkmedia
  • rokkmedia
  • OFFLINE
  • Posts: 22
  • Thanks: 0
  • Karma: 0
11 years 7 months ago - 11 years 7 months ago #223116 by rokkmedia
Thank you! your help is appreciated.
Last edit: 11 years 7 months ago by rokkmedia.

Please Log in or Create an account to join the conversation.

Moderators: beatnantkrileon
Powered by Kunena Forum