Skip to Content Skip to Menu

CBSubs 1.2.2 upgrade error with main file

  • sorozco
  • sorozco
  • OFFLINE
  • Posts: 92
  • Thanks: 5
  • Karma: 1
13 years 2 months ago #171820 by sorozco
Hello, I'm trying to upgrade CBSubs from 1.1.2 to 1.2.2 (Joomla 1.5 CB 1.4). The problem is, when trying to install cbplug_CBSubs_MAIN_122-E.zip, the process fails and the next error is displayed:



ERROR:

Plugin database XML SQL Error CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_1_plans_required failed with SQL error: Column length too big for column 'cond_1_plans_required' (max = 255); use BLOB or TEXT instead SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_1_plans_required` varchar(1024) NOT NULL DEFAULT '' AFTER `cond_1_operator` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_1_plans_status failed with SQL error: Unknown column 'cond_1_plans_required' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_1_plans_status` varchar(40) NOT NULL DEFAULT '' AFTER `cond_1_plans_required` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_1_purchase_ok failed with SQL error: Unknown column 'cond_1_plans_status' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_1_purchase_ok` tinyint(4) NOT NULL DEFAULT 0 AFTER `cond_1_plans_status` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_1_date_1 failed with SQL error: Unknown column 'cond_1_purchase_ok' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_1_date_1` varchar(20) NOT NULL DEFAULT '' AFTER `cond_1_purchase_ok` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_1_date_cbfield_1 failed with SQL error: Unknown column 'cond_1_date_1' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_1_date_cbfield_1` int(11) NOT NULL DEFAULT 0 AFTER `cond_1_date_1` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_1_value_1 failed with SQL error: Column length too big for column 'cond_1_value_1' (max = 255); use BLOB or TEXT instead SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_1_value_1` varchar(1024) NOT NULL DEFAULT '' AFTER `cond_1_date_cbfield_1` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_1_dates_diff_a failed with SQL error: Unknown column 'cond_1_value_1' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_1_dates_diff_a` varchar(21) NOT NULL DEFAULT '' AFTER `cond_1_value_1` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_1_dates_diff_b failed with SQL error: Unknown column 'cond_1_dates_diff_a' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_1_dates_diff_b` varchar(21) NOT NULL DEFAULT '' AFTER `cond_1_dates_diff_a` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_1_date_2 failed with SQL error: Unknown column 'cond_1_dates_diff_b' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_1_date_2` varchar(20) NOT NULL DEFAULT '' AFTER `cond_1_dates_diff_b` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_1_date_cbfield_2 failed with SQL error: Unknown column 'cond_1_date_2' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_1_date_cbfield_2` int(11) NOT NULL DEFAULT 0 AFTER `cond_1_date_2` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_1_value_2 failed with SQL error: Column length too big for column 'cond_1_value_2' (max = 255); use BLOB or TEXT instead SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_1_value_2` varchar(1024) NOT NULL DEFAULT '' AFTER `cond_1_date_cbfield_2` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_2_operator failed with SQL error: Unknown column 'cond_1_value_2' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_2_operator` varchar(7) NOT NULL DEFAULT '' AFTER `cond_1_value_2` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_2_plans_required failed with SQL error: Column length too big for column 'cond_2_plans_required' (max = 255); use BLOB or TEXT instead SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_2_plans_required` varchar(1024) NOT NULL DEFAULT '' AFTER `cond_2_operator` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_2_plans_status failed with SQL error: Unknown column 'cond_2_plans_required' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_2_plans_status` varchar(40) NOT NULL DEFAULT '' AFTER `cond_2_plans_required` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_2_purchase_ok failed with SQL error: Unknown column 'cond_2_plans_status' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_2_purchase_ok` tinyint(4) NOT NULL DEFAULT 0 AFTER `cond_2_plans_status` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_2_date_1 failed with SQL error: Unknown column 'cond_2_purchase_ok' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_2_date_1` varchar(20) NOT NULL DEFAULT '' AFTER `cond_2_purchase_ok` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_2_date_cbfield_1 failed with SQL error: Unknown column 'cond_2_date_1' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_2_date_cbfield_1` int(11) NOT NULL DEFAULT 0 AFTER `cond_2_date_1` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_2_value_1 failed with SQL error: Column length too big for column 'cond_2_value_1' (max = 255); use BLOB or TEXT instead SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_2_value_1` varchar(1024) NOT NULL DEFAULT '' AFTER `cond_2_date_cbfield_1` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_2_dates_diff_a failed with SQL error: Unknown column 'cond_2_value_1' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_2_dates_diff_a` varchar(21) NOT NULL DEFAULT '' AFTER `cond_2_value_1` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_2_dates_diff_b failed with SQL error: Unknown column 'cond_2_dates_diff_a' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_2_dates_diff_b` varchar(21) NOT NULL DEFAULT '' AFTER `cond_2_dates_diff_a` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_2_date_2 failed with SQL error: Unknown column 'cond_2_dates_diff_b' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_2_date_2` varchar(20) NOT NULL DEFAULT '' AFTER `cond_2_dates_diff_b` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_2_date_cbfield_2 failed with SQL error: Unknown column 'cond_2_date_2' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_2_date_cbfield_2` int(11) NOT NULL DEFAULT 0 AFTER `cond_2_date_2` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column cond_2_value_2 failed with SQL error: Column length too big for column 'cond_2_value_2' (max = 255); use BLOB or TEXT instead SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `cond_2_value_2` varchar(1024) NOT NULL DEFAULT '' AFTER `cond_2_date_cbfield_2` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column upgrade_conds failed with SQL error: Unknown column 'cond_2_value_2' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `upgrade_conds` tinyint(4) NOT NULL DEFAULT 0 AFTER `cond_2_value_2` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column upgrade_conds_plans_required failed with SQL error: Unknown column 'upgrade_conds' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `upgrade_conds_plans_required` varchar(255) NOT NULL DEFAULT '' AFTER `upgrade_conds` CBSQLupgrader::changeColumn (ADD) of Table #__cbsubs_plans Column upgrade_conds_plans_disallowing failed with SQL error: Unknown column 'upgrade_conds_plans_required' in 'joomlalp_cbsubs_plans' SQL=ALTER TABLE `joomlalp_cbsubs_plans` ADD `upgrade_conds_plans_disallowing` varchar(255) NOT NULL DEFAULT '' AFTER `upgrade_conds_plans_required`



After the error ocurrs, the previous installation is deleted with other components, so to restore CBSubs to it's current state I had to reinstall the previous version and all plugins.

I really need to make the upgrade to 1.2.2. but I can't seem to find the problem. Any ideas?

Thanks in advance.

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

  • krileon
  • krileon
  • ONLINE
  • Posts: 48424
  • Thanks: 8274
  • Karma: 1443
13 years 2 months ago #171848 by krileon
Replied by krileon on topic Re: CBSubs 1.2.2 upgrade error with main file
This is due to using an obsolete MYSQL version (less than 5.0.4). Please contact your host to upgrade at minimal MYSQL 5.0.4. For more details on this and a possible workaround please see the below thread.

www.joomlapolis.com/forum/88-usage/169000-sql-errors-when-trying-to-upgrade-to-12#169006


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.

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

  • sorozco
  • sorozco
  • OFFLINE
  • Posts: 92
  • Thanks: 5
  • Karma: 1
13 years 2 months ago - 13 years 2 months ago #171852 by sorozco
Replied by sorozco on topic Re: CBSubs 1.2.2 upgrade error with main file
Hi, our database is on MySQL 5.0.32. According to the post you suggested, the character limit was lifted in 5.0.3. If thats the case, why do we have the problem? Do you think I should change the varchar settings in cbpaidsubscriptions.xml mentioned?

Also, I believe the previous version (CB Subs 1.1.2) wasn't so different in that area, and we didn't have problems installing it.
Last edit: 13 years 2 months ago by sorozco.

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

  • krileon
  • krileon
  • ONLINE
  • Posts: 48424
  • Thanks: 8274
  • Karma: 1443
13 years 2 months ago #171864 by krileon
Replied by krileon on topic Re: CBSubs 1.2.2 upgrade error with main file

Hi, our database is on MySQL 5.0.32. According to the post you suggested, the character limit was lifted in 5.0.3. If thats the case, why do we have the problem? Do you think I should change the varchar settings in cbpaidsubscriptions.xml mentioned?

You need at minimum 5.0.4, 5.0.3 I believe still has issues. Please contact your host regarding updating.

Also, I believe the previous version (CB Subs 1.1.2) wasn't so different in that area, and we didn't have problems installing it.

1.1.2 is quite a few version ago. 1.2.2 has many changes in all aspects that are not present in 1.1.2.


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: sorozco

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

  • sorozco
  • sorozco
  • OFFLINE
  • Posts: 92
  • Thanks: 5
  • Karma: 1
13 years 2 months ago #171881 by sorozco
Replied by sorozco on topic Re: CBSubs 1.2.2 upgrade error with main file
Alright, we will look into that. Thanks!

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

Moderators: beatnantkrileon
Powered by Kunena Forum