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) »
  • upgrade 1.9 -> 2.0.7: Fatal error: getConfigObject() (custom fields?) - solved!
Pages: [1]

Author Topic: upgrade 1.9 -> 2.0.7: Fatal error: getConfigObject() (custom fields?) - solved!  (Read 1958 times)

fen

  • I post frequently
  • ***
  • Posts: 216
  • Karma: 13
    • CivicActions
  • CiviCRM version: 3.3-4.3
  • CMS version: Drupal 6/7
  • MySQL version: 5.1/5.5
  • PHP version: 5.3/5.4
upgrade 1.9 -> 2.0.7: Fatal error: getConfigObject() (custom fields?) - solved!
December 10, 2008, 07:24:14 am
I did the schema-integrity steps and got through the six-step upgrade but then whenever I try to get to any of the sub-pages under /civicrm/admin/setting I get:
Code: [Select]
Fatal error: Call to a member function getConfigObject() on a non-object in /home/fen/workspace/civicrm/v2.0-trunk-ca/CRM/Core/Config/Defaults.php on line 205Could this have something to do with custom tables?  In v1.9 I had 7 rows in civicrm_custom_group and the name field has been turned into tables for the form civicrm_value_1_NAME...
« Last Edit: December 10, 2008, 12:56:34 pm by fen »

fen

  • I post frequently
  • ***
  • Posts: 216
  • Karma: 13
    • CivicActions
  • CiviCRM version: 3.3-4.3
  • CMS version: Drupal 6/7
  • MySQL version: 5.1/5.5
  • PHP version: 5.3/5.4
Re: upgrade 1.9 -> 2.0.7: Fatal error: getConfigObject() (custom fields?)
December 10, 2008, 11:36:04 am
I saw from another post that the issue could be with not having assured DB schema integrity in v1.9, so I re-did those steps and still get the problem.  The only links I have found that don't work are:

  • /civicrm/admin/setting/component?reset=1
  • /civicrm/admin/setting/path?reset=1
  • /civicrm/admin/setting/url?reset=1
  • /civicrm/admin/setting/smtp?reset=1
  • /civicrm/admin/setting/mapping?reset=1
  • /civicrm/admin/setting/localization?reset=1
  • /civicrm/admin/setting/date?reset=1
  • /civicrm/admin/setting/uf?reset=1
  • /civicrm/admin/setting/misc?reset=1
  • /civicrm/admin/setting/debug?reset=1

That is, Site Preferences, Payment Processors and Address Settings work, as do all other links I have tried.  BTW. the custom data (civicrm/admin/custom/group) that I previously suspected looks fine.  Still checking...

fen

  • I post frequently
  • ***
  • Posts: 216
  • Karma: 13
    • CivicActions
  • CiviCRM version: 3.3-4.3
  • CMS version: Drupal 6/7
  • MySQL version: 5.1/5.5
  • PHP version: 5.3/5.4
Re: upgrade 1.9 -> 2.0.7: Fatal error: getConfigObject() (custom fields?) - solved!
December 10, 2008, 12:58:02 pm
Solved!

The problem was that a custom component had been introduced and was not found in the componentRegistry.

Sorry for any time that anyone put in to looking at this.

Thanks!
=Fen
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • upgrade 1.9 -> 2.0.7: Fatal error: getConfigObject() (custom fields?) - solved!

This forum was archived on 2017-11-26.