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) »
  • Discussion (deprecated) »
  • Alpha and Beta Release Testing »
  • 4.4 Release Testing »
  • CRM_Core_PseudoConstant warnings on clean 4.4a3 install
Pages: [1]

Author Topic: CRM_Core_PseudoConstant warnings on clean 4.4a3 install  (Read 778 times)

choster

  • I’m new here
  • *
  • Posts: 29
  • Karma: 2
    • Lattice Group
  • CiviCRM version: 4.3,4.4,4.5
  • CMS version: Drupal 7
  • MySQL version: 5.5.39
  • PHP version: 5.5.15
CRM_Core_PseudoConstant warnings on clean 4.4a3 install
September 03, 2013, 01:51:07 pm
I've just installed 4.4alpha3 to test a new site and want to first say kudos to the team for a very fine product overall.

This is a clean install; our environment is MySQL 5.1.69 and Apache 2.2.15 with PHP 5.3.3 on CentOS 6.4. On certain tasks, I get about 14 warnings, all complaining that CRM_Core_PseudoConstant does not have some method in civicrm_handler_filter_pseudo_constant->construct, called in civicrm/drupal/modules/views/civicrm/civicrm_handler_filter_pseudo_constant.inc , for example:

Code: [Select]
Warning: call_user_func_array() expects parameter 1 to be a valid callback, class 'CRM_Core_PseudoConstant' does not have a method 'locationType' in civicrm_handler_filter_pseudo_constant->construct() (line 54 of /var/www/sites/all/modules/civicrm/drupal/modules/views/civicrm/civicrm_handler_filter_pseudo_constant.inc).

Warning: call_user_func_array() expects parameter 1 to be a valid callback, class 'CRM_Core_PseudoConstant' does not have a method 'gender' in civicrm_handler_filter_pseudo_constant->construct() (line 54 of /var/www/sites/all/modules/civicrm/drupal/modules/views/civicrm/civicrm_handler_filter_pseudo_constant.inc).

Warning: call_user_func_array() expects parameter 1 to be a valid callback, class 'CRM_Core_PseudoConstant' does not have a method 'preferredLanguage' in civicrm_handler_filter_pseudo_constant->construct() (line 54 of/var/www/sites/all/modules/civicrm/drupal/modules/views/civicrm/civicrm_handler_filter_pseudo_constant.inc).

The screen appears after I do any of the following:

  • Modify a profile
  • Creating a new custom field
  • Run the Drupal database upgrade script

I have tried clearing the caches and rebuilding the menu several times, but the warnings continue to display after any of the above. They do not show on other types of tasks. Any insights would be greatly appreciated.

--
Added: I cannot reproduce the problem on the sandbox server.
« Last Edit: September 03, 2013, 01:57:07 pm by choster »

Yashodha Chaku

  • Forum Godess / God
  • Ask me questions
  • *****
  • Posts: 755
  • Karma: 57
    • CiviCRM
Re: CRM_Core_PseudoConstant warnings on clean 4.4a3 install
September 04, 2013, 01:08:48 am
Can you file an issue with our issue tracker JIRA
http://issues.civicrm.org
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.

choster

  • I’m new here
  • *
  • Posts: 29
  • Karma: 2
    • Lattice Group
  • CiviCRM version: 4.3,4.4,4.5
  • CMS version: Drupal 7
  • MySQL version: 5.5.39
  • PHP version: 5.5.15
Re: CRM_Core_PseudoConstant warnings on clean 4.4a3 install
September 04, 2013, 11:36:11 am
Since I couldn't reproduce it on the sandbox, I thought I would check here first in case anyone else had encountered it. On the other hand, our environment is pretty vanilla, and we've never seen these warnings before for any previous version, so here we go: :)  http://issues.civicrm.org/jira/browse/CRM-13339 .

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Alpha and Beta Release Testing »
  • 4.4 Release Testing »
  • CRM_Core_PseudoConstant warnings on clean 4.4a3 install

This forum was archived on 2017-11-26.