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 »
  • Using CiviCRM »
  • Using Profiles (Moderator: Dave Greenberg) »
  • Since upgrade to 4.3 phone fields on profile cause errors
Pages: [1]

Author Topic: Since upgrade to 4.3 phone fields on profile cause errors  (Read 4664 times)

jackrabbithanna

  • I post occasionally
  • **
  • Posts: 61
  • Karma: 3
  • Quick like bunny
    • http://www.skvare.com
  • CiviCRM version: 4.3.5
  • CMS version: Drupal 7.23
  • MySQL version: 5.1
  • PHP version: 5.3.3
Since upgrade to 4.3 phone fields on profile cause errors
May 13, 2013, 10:52:47 am
I had a join contribution page which has a profile with 2 phone fields, one for home and one for mobile.  The site got upgraded to 4.3 and now when anyone submits the form they get an unknown DB error and cannot contribute.

When I remove the phone fields from the profile, it all works smoothly. Bug in new version to do with the phone fields??

In the drupal log i see this:
$Fatal Error Details = Array ( [callback] => Array (
  • => CRM_Core_Error [1] => handle )
    Code: [Select]
    => -1 [message] => DB Error: unknown error [mode] => 16 [debug_info] => UPDATE civicrm_phone SET contact_id = 2272 , location_type_id = 2 , is_primary = 0 , is_billing = 0 , phone = '555-555-5555' , phone_type_id = 1 WHERE ( civicrm_phone.id = 3813 ) [nativecode=1305 ** FUNCTION skvare_awc_civicrm.civicrm_strip_non_numeric does not exist] [type] => DB_Error [user_info] => UPDATE civicrm_phone SET contact_id = 2272 , location_type_id = 2 , is_primary = 0 , is_billing = 0 , phone = '555-555-5555' , phone_type_id = 1 WHERE ( civicrm_phone.id = 3813 ) [nativecode=1305 ** FUNCTION skvare_awc_civicrm.civicrm_strip_non_numeric does not exist] [to_string] => [db_error: message="DB Error: unknown error" code=-1 mode=callback callback=CRM_Core_Error::handle prefix="" info="UPDATE civicrm_phone SET contact_id = 2272 , location_type_id = 2 , is_primary = 0 , is_billing = 0 , phone = '555-555-5555' , phone_type_id = 1 WHERE ( civicrm_phone.id = 3813 ) [nativecode=1305 ** FUNCTION skvare_awc_civicrm.civicrm_strip_non_numeric does not exist]"] )
« Last Edit: June 06, 2013, 06:42:55 am by jackrabbithanna »

Coleman Watts

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 2346
  • Karma: 183
  • CiviCRM version: The Bleeding Edge
  • CMS version: Various
Re: Since upgrade to 4.3 phone fields on profile cause errors
May 13, 2013, 11:02:22 am
The phone field has a db trigger attached to it, which seems to not exist on your site. The installer/upgrader normally takes care of this, however there was a bug in the 4.3.2 upgrade script that may have caused this trigger to not be built for you. Did you by any chance upgrade directly from 4.2 to 4.3.2? If so the fix would be upgrading to 4.3.3.
Try asking your question on the new CiviCRM help site.

jackrabbithanna

  • I post occasionally
  • **
  • Posts: 61
  • Karma: 3
  • Quick like bunny
    • http://www.skvare.com
  • CiviCRM version: 4.3.5
  • CMS version: Drupal 7.23
  • MySQL version: 5.1
  • PHP version: 5.3.3
Re: Since upgrade to 4.3 phone fields on profile cause errors
May 13, 2013, 11:45:31 am
No I believe the site was upgraded from 4.2 to 4.3.0 and then each minor upgrade done separately.  This makes sense though since it stopped working around the 4.3.2 upgrade..

What can I do now that I'm already to 4.3.3 and it is still broken?

jackrabbithanna

  • I post occasionally
  • **
  • Posts: 61
  • Karma: 3
  • Quick like bunny
    • http://www.skvare.com
  • CiviCRM version: 4.3.5
  • CMS version: Drupal 7.23
  • MySQL version: 5.1
  • PHP version: 5.3.3
Re: Since upgrade to 4.3 phone fields on profile cause errors
May 13, 2013, 05:00:47 pm
see this thread:http://forum.civicrm.org/index.php/topic,28751.0.html#msg123097

for the solution: go to path: civicrm/menu/rebuild&reset=1&triggerRebuild=1


jackrabbithanna

  • I post occasionally
  • **
  • Posts: 61
  • Karma: 3
  • Quick like bunny
    • http://www.skvare.com
  • CiviCRM version: 4.3.5
  • CMS version: Drupal 7.23
  • MySQL version: 5.1
  • PHP version: 5.3.3
Re:Since upgrade to 4.3 phone fields on profile cause errors
June 06, 2013, 06:38:35 am
This problem keeps re-occuring.  I can run the db-trigger solution and it fixes it for a few days...then somehow the problem crops up again. 

Why would that be?
« Last Edit: June 06, 2013, 06:43:09 am by jackrabbithanna »

jackrabbithanna

  • I post occasionally
  • **
  • Posts: 61
  • Karma: 3
  • Quick like bunny
    • http://www.skvare.com
  • CiviCRM version: 4.3.5
  • CMS version: Drupal 7.23
  • MySQL version: 5.1
  • PHP version: 5.3.3
Re: Since upgrade to 4.3 phone fields on profile cause errors
June 06, 2013, 11:54:02 am
Ok some new information on this issue....

It appears that enabling/disabling either Drupal modules or CiviCRM extensions is necessitating a trigger rebuild for us...

bcobin

  • I post frequently
  • ***
  • Posts: 337
  • Karma: 9
    • InterCreative Media
  • CiviCRM version: 4.3.3
  • CMS version: Drupal 7.22
  • MySQL version: 5.5.9
  • PHP version: 5.3
Re: UPDATE - Since upgrade to 4.3 phone fields on profile cause errors
October 18, 2013, 04:19:41 pm
I'm running into the same issue, but a trigger rebuild doesn't work for me. After migrating to a new VPS, contributions fail if there's a profile being used that includes a phone field. This is in 4.3.7 and a basically fresh installation.

Below is the backtrace - any ideas? Thanks...

Code: [Select]
backTrace

#0 /home/[site]/public_html/sites/all/modules/civicrm/CRM/Core/Error.php(148): CRM_Core_Error::backtrace()
#1 [internal function](): CRM_Core_Error::handle(Object(DB_Error))
#2 /home/[site]/public_html/sites/all/modules/civicrm/packages/PEAR.php(931): call_user_func((Array:2), Object(DB_Error))
#3 /home/[site]/public_html/sites/all/modules/civicrm/packages/DB.php(969): PEAR_Error->PEAR_Error("DB Error: unknown error", -1, 16, (Array:2), "UPDATE  civicrm_phone  SET is_primary = 0   WHERE (  civicrm_phone.id = 1 )  ...")
#4 /home/[site]/public_html/sites/all/modules/civicrm/packages/PEAR.php(564): DB_Error->DB_Error(-1, 16, (Array:2), "UPDATE  civicrm_phone  SET is_primary = 0   WHERE (  civicrm_phone.id = 1 )  ...")
#5 /home/[site]/public_html/sites/all/modules/civicrm/packages/DB/common.php(1905): PEAR->raiseError(NULL, -1, NULL, NULL, "UPDATE  civicrm_phone  SET is_primary = 0   WHERE (  civicrm_phone.id = 1 )  ...", "DB_Error", TRUE)
#6 /home/[site]/public_html/sites/all/modules/civicrm/packages/DB/mysql.php(898): DB_common->raiseError(-1, NULL, NULL, NULL, "1305 ** FUNCTION [site]_civi.civicrm_strip_non_numeric does not exist")
#7 /home/[site]/public_html/sites/all/modules/civicrm/packages/DB/mysql.php(327): DB_mysql->mysqlRaiseError()
#8 /home/[site]/public_html/sites/all/modules/civicrm/packages/DB/common.php(1216): DB_mysql->simpleQuery("UPDATE  civicrm_phone  SET is_primary = 0   WHERE (  civicrm_phone.id = 1 )  ")
#9 /home/[site]/public_html/sites/all/modules/civicrm/packages/DB/DataObject.php(2421): DB_common->query("UPDATE  civicrm_phone  SET is_primary = 0   WHERE (  civicrm_phone.id = 1 )  ")
#10 /home/[site]/public_html/sites/all/modules/civicrm/packages/DB/DataObject.php(1324): DB_DataObject->_query("UPDATE  civicrm_phone  SET is_primary = 0   WHERE (  civicrm_phone.id = 1 )  ")
#11 /home/[site]/public_html/sites/all/modules/civicrm/CRM/Core/DAO.php(284): DB_DataObject->update()
#12 /home/[site]/public_html/sites/all/modules/civicrm/CRM/Core/BAO/Block.php(268): CRM_Core_DAO->save()
#13 /home/[site]/public_html/sites/all/modules/civicrm/CRM/Core/BAO/Location.php(66) : eval()'d code(1): CRM_Core_BAO_Block::create("phone", (Array:36), NULL)
#14 /home/[site]/public_html/sites/all/modules/civicrm/CRM/Core/BAO/Location.php(66): eval()
#15 /home/[site]/public_html/sites/all/modules/civicrm/CRM/Contact/BAO/Contact.php(352): CRM_Core_BAO_Location::create((Array:36), TRUE)
#16 /home/[site]/public_html/sites/all/modules/civicrm/CRM/Contact/BAO/Contact.php(1699): CRM_Contact_BAO_Contact::create((Array:36))
#17 /home/[site]/public_html/sites/all/modules/civicrm/CRM/Contribute/Form/Contribution/Confirm.php(787): CRM_Contact_BAO_Contact::createProfileContact((Array:43), (Array:10), "2", (Array:0), NULL, "Individual", TRUE)
#18 /home/[site]/public_html/sites/all/modules/civicrm/CRM/Core/Form.php(246): CRM_Contribute_Form_Contribution_Confirm->postProcess()
#19 /home/[site]/public_html/sites/all/modules/civicrm/CRM/Core/StateMachine.php(160): CRM_Core_Form->mainProcess()
#20 /home/[site]/public_html/sites/all/modules/civicrm/CRM/Core/QuickForm/Action/Next.php(60): CRM_Core_StateMachine->perform(Object(CRM_Contribute_Form_Contribution_Confirm), "next", "Next")
#21 /home/[site]/public_html/sites/all/modules/civicrm/packages/HTML/QuickForm/Controller.php(203): CRM_Core_QuickForm_Action_Next->perform(Object(CRM_Contribute_Form_Contribution_Confirm), "next")
#22 /home/[site]/public_html/sites/all/modules/civicrm/packages/HTML/QuickForm/Page.php(103): HTML_QuickForm_Controller->handle(Object(CRM_Contribute_Form_Contribution_Confirm), "next")
#23 /home/[site]/public_html/sites/all/modules/civicrm/CRM/Core/Controller.php(316): HTML_QuickForm_Page->handle("next")
#24 /home/[site]/public_html/sites/all/modules/civicrm/CRM/Core/Invoke.php(292): CRM_Core_Controller->run((Array:3), NULL)
#25 /home/[site]/public_html/sites/all/modules/civicrm/CRM/Core/Invoke.php(70): CRM_Core_Invoke::runItem((Array:15))
#26 /home/[site]/public_html/sites/all/modules/civicrm/CRM/Core/Invoke.php(52): CRM_Core_Invoke::_invoke((Array:3))
#27 /home/[site]/public_html/sites/all/modules/civicrm/drupal/civicrm.module(436): CRM_Core_Invoke::invoke((Array:3))
#28 [internal function](): civicrm_invoke("contribute", "transact")
#29 /home/[site]/public_html/includes/menu.inc(517): call_user_func_array("civicrm_invoke", (Array:2))
#30 /home/[site]/public_html/index.php(21): menu_execute_active_handler()
#31 {main}

UPDATE: I believe I found the issue at http://forum.civicrm.org/index.php/topic,28652.0.html
« Last Edit: October 18, 2013, 04:38:06 pm by bcobin »

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Since upgrade to 4.3 phone fields on profile cause errors
October 20, 2013, 08:32:36 am

check your mysql query logs and see if the stored procedures / triggers are being rebuilt.

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

bcobin

  • I post frequently
  • ***
  • Posts: 337
  • Karma: 9
    • InterCreative Media
  • CiviCRM version: 4.3.3
  • CMS version: Drupal 7.22
  • MySQL version: 5.5.9
  • PHP version: 5.3
Re: Since upgrade to 4.3 phone fields on profile cause errors
October 20, 2013, 08:41:27 am
Thanks, Donald - the host migrated the site to a different VPS (using mysqldump, I presume) because of performance issues and that's when the problem arose. Once advised of the problem, they remigrated from a previous backup and now everything is performing as expected.

Punting here as the site will only be up until Election Day - about two weeks.

Thanks for the response!

bcobin

  • I post frequently
  • ***
  • Posts: 337
  • Karma: 9
    • InterCreative Media
  • CiviCRM version: 4.3.3
  • CMS version: Drupal 7.22
  • MySQL version: 5.5.9
  • PHP version: 5.3
Re: Since upgrade to 4.3 phone fields on profile cause errors
November 01, 2013, 02:44:33 pm
Following up here...

This is from the host:

Quote
For future reference problem was the innodb_file_per_table restriction in root mysql configuration of VPS which was preventing clean import.

I don't know how much this helps, but knowledge=power, right?

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Since upgrade to 4.3 phone fields on profile cause errors
November 01, 2013, 05:29:02 pm

can you ask the host to clarify and explain a bit more on what they mean and why that caused the issue?

thanx

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

bcobin

  • I post frequently
  • ***
  • Posts: 337
  • Karma: 9
    • InterCreative Media
  • CiviCRM version: 4.3.3
  • CMS version: Drupal 7.22
  • MySQL version: 5.5.9
  • PHP version: 5.3
Re: Since upgrade to 4.3 phone fields on profile cause errors
November 01, 2013, 05:44:30 pm
I've forwarded this thread to the host - Imageleet, BTW (they're terrific.)

I'm hoping they weigh in. We host all our sites with them and they've really come through for us on countless occasions.

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Profiles (Moderator: Dave Greenberg) »
  • Since upgrade to 4.3 phone fields on profile cause errors

This forum was archived on 2017-11-26.