CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Issues with 4.0.8 - 4.1.3 Upgrade
Pages: [1]

Author Topic: Issues with 4.0.8 - 4.1.3 Upgrade  (Read 538 times)

Hershel

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4640
  • Karma: 176
    • CiviHosting
  • CiviCRM version: Latest
  • CMS version: Mostly WordPress and Drupal
Issues with 4.0.8 - 4.1.3 Upgrade
June 14, 2012, 08:45:47 am
With Drupal 7, I am running an 4.0.8 - 4.1.3 upgrade and first I had the issue described here http://forum.civicrm.org/index.php/topic,23920 but reply #6 there fixed it. Now I have an odd error:

Code: [Select]
DELETE g, v
  FROM civicrm_option_group g,
       civicrm_option_value v
 WHERE g.id = v.option_group_id
   AND g.name = 'directory_preferences' [nativecode=1054 ** Unknown column 'label' in 'OLD']

which I don't quite understand. If I change the first line of that query and run:

Code: [Select]
SELECT *
FROM civicrm_option_group g, civicrm_option_value v
WHERE g.id = v.option_group_id
AND g.name =  'directory_preferences'

it works fine and brings back 6 rows.

The error message on the DELETE query is a bit mysterious to me. Same error message if I run the SQL directly in MySQL as well.
CiviHosting and CiviOnline -- The CiviCRM hosting experts, since 2007

See here for the official: What to do if you think you've found a bug.

Hershel

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4640
  • Karma: 176
    • CiviHosting
  • CiviCRM version: Latest
  • CMS version: Mostly WordPress and Drupal
Re: Issues with 4.0.8 - 4.1.3 Upgrade
June 17, 2012, 07:23:01 am
The issue is the trigger. This code:

Code: [Select]
DROP TRIGGER IF EXISTS `civicrm_option_group_after_delete`//
CREATE TRIGGER `civicrm_option_group_after_delete` AFTER DELETE ON `civicrm_option_group`
 FOR EACH ROW INSERT INTO `ravsak_civicrm_backup_20120530`.log_civicrm_option_group (id, name, label, description, is_reserved, is_active, log_conn_id, log_user_id, log_action) VALUES (OLD.id, OLD.name, OLD.label, OLD.description, OLD.is_reserved, OLD.is_active, CONNECTION_ID(), @civicrm_user_id, 'Delete')
//

in particular, which has OLD.label and that column indeed no longer exists. So I ran

Code: [Select]
DROP TRIGGER IF EXISTS `civicrm_option_group_after_delete`;
to remove that trigger and then the upgrade ran.
CiviHosting and CiviOnline -- The CiviCRM hosting experts, since 2007

See here for the official: What to do if you think you've found a bug.

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Issues with 4.0.8 - 4.1.3 Upgrade

This forum was archived on 2017-11-26.