3

I have a Civi implementation that uses a custom activity type in which I have - amongst others - four custom fields of the field type "File".

These custom fields work fine in all but one situation. If I view an activity record of this type the pop-up does not display the fields or the links to the files. If I force the activity view to display in a new browser window/tab then the following warnings get thrown up:

Warning: strtolower() expects parameter 1 to be string, array given in CRM_Core_DAO::getFieldValue() (line 1004 of /data/www/html/sites/all/modules/civicrm/CRM/Core/DAO.php).
Warning: strtolower() expects parameter 1 to be string, array given in CRM_Core_DAO::getFieldValue() (line 1004 of /data/www/html/sites/all/modules/civicrm/CRM/Core/DAO.php).
Warning: strtolower() expects parameter 1 to be string, array given in CRM_Core_DAO::getFieldValue() (line 1004 of /data/www/html/sites/all/modules/civicrm/CRM/Core/DAO.php).
Warning: strtolower() expects parameter 1 to be string, array given in CRM_Core_DAO::getFieldValue() (line 1004 of /data/www/html/sites/all/modules/civicrm/CRM/Core/DAO.php).

My guess being that the four repeated PHP warnings relate to the four custom file fields, and give a clue as to why they aren't getting displayed in the activity view pop-up. The current workaround is to edit the activity record, where the four fields and the links to files are displayed.

It would be really good to fix this. Any pointers most welcome. Currently using CiviCRM version 4.6.18 on Drupal 7.

4

It sounds like you're encountering CRM-17791. This bug was discovered and fixed in CiviCRM 4.7. I would recommend upgrading a test copy of your site to 4.7 to see if that resolves the issue. If so, consider upgrading or funding the long-term support team to backport a fix to version 4.6.

  • I finally got round to upgrading the site where I'm seeing this issue. I upgraded in two stages and tested both at version 4.6.25 and 4.7.15. The issue remains for me, although I can't repeat it on dmaster.demo.civicrm.org which reports as 4.7.16. Issue posted at issues.civicrm.org/jira/browse/CRM-19870 – Graham Jan 12 '17 at 13:16
  • Although on demo site we see other undesirable behaviour. check the issue for the details. – Graham Jan 12 '17 at 13:22
  • 1
    @Graham - It sounds like you have a replicable bug then; I would file it on issues.civicrm.org. That doesn't guarantee it will get fixed, of course, unless you also submit it to the paid issue queue (civicrm.org/paid-issue-queue), but it's a first step. – Jon G - Megaphone Tech Jan 12 '17 at 14:16
  • My client has already paid to get one bug fixed. They won't be at all keen to fork out again as they are only a small organisation with a modest budget. The issue has been filed nonetheless, and I'll keep my fingers crossed that it gets fixed. – Graham Jan 13 '17 at 16:34
0

Looks like this was fixed here: https://github.com/civicrm/civicrm-core/commit/f3ceb1120bd50a5ac830ba405b3c6f72144480cb#diff-33ffa83cfb2fd90a56c6f258f36062a0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.