Warnings when I try to create constituant sumary report

[FastPhil]

Warning: htmlspecialchars() expects parameter 1 to be string, array given in HTML_Common->_getAttrString() (line 144 of /var/www/sites/all/modules/civicrm/packages/HTML/Common.php).

I get two of those in an orange box at the top of the page when I try to use the constituent summary report.  any thoughts on what is wrong.

[ddunn]

I'm also seeing this error offered, running 4.1.1 on Drupal 7. Would be grateful of any suggestions.

[britebyte]

I have the same error as well.

[Yashodha Chaku]

Can you replicate the same on demo.civicrm.org

-Yashodha

[britebyte]

Can you replicate the same on demo.civicrm.org

No, it works fine on the demo site for me.

[FastPhil]

I am sorry I might have helped with posting our findings.  My ISP switched servers to a new server with much tighter restrictions and they had to remove some of them for this to work.  I wish I had the technical details for you but it was done by the ISP.

[The Next Wave]

Getting same message with 4.3 Beta 5
2 lines- when trying to generate a report:

Warning: htmlspecialchars() expects parameter 1 to be string, array given in public_html/wp-content/plugins/civicrm/civicrm/packages/HTML/Common.php on line 144

[Donald Lobo]

What are the sequence of steps to get this error. I went to the constituent summary report and did not get this message with sample data

lobo

[adixon]

I get this error on some of my reports for a Drupal 6 - CiviCRM 4.2.9 installation (a moderate sized install that started life back in the 3.x series, a few years ago).

The argument to htmlspecialchars is an empty array, and the argument to the containing function _getAttrString is this:

Code: [Select]

Array  (
                    [name] => custom_10_value
                    [type] => text
                    [value] => Array
                        (
                        )

                    [id] => custom_10_value
                    [class] => form-text
)

So I'm guessing this comes up with custom fields, and that empty 'value' array that is getting left in somehow.

In this installation, custom_10 field is from a All Contact Types custom field group (a group called Legacy Import).

Does that help?

[moj0rising]

I am seeing the same warnings with a 4.3.3 install.

Does anyone have an update on the situation? Has anyone been able to work around it?

Thanks,
Mike

[dshong21]

I get this error when I make a custom field searchable. I want the custom field in my reports but I guess if you don't need it you can make your custom fields unsearchable. I don't have a real solution though unfortunately.