Router item 'features/ajaxcallback/%' has bogus title callback.

Why was ctools marked as component? nothing if this bug report indicates it's ctools intergration specific

On that line that is triggerring the warning,

if (is_array($that_variable) {
  some sort of print statement debug_backtrace(); 
}

I am getting this same message (repeatedly) in my dblog after creating new features. I actually turned the ctools dependency off for the last run to see if that had anything to do with it, but that did not change anything. I still got 29 lines of this error for one feature.

I tried creating a feature with no Field Instances (where the bulk of the html was in description fields) as well, but the warnings persist.

Location: http://~mysite~.com/features/ajaxcallback/*
Referrer: http://~mysite~.com/admin/structure/features/create
Message: Warning: htmlspecialchars() expects parameter 1 to be string, array given in check_plain() (line 1565 of /home/~path~/~to~/~mysite~/includes/bootstrap.inc).
Severity: Warning

The features appear to be created correctly. I can generate and/or download them, but with all these warnings, I would hesitate to use them anywhere.

Using Features 7.x-2.0-rc4 with Drupal 7.23 running on PHP 5.3.27

Please see the suggestion in #1 about using debug_backtrace. Showing an error from Drupal core (bootstrap.inc) doesn't help track down this problem. We need to see where in Features this is being called. I was not able to reproduce it in my test sites.

same issue here

Mensaje de error
Warning: htmlspecialchars() expects parameter 1 to be string, array given en check_plain() (línea 1565 de /home5/teleinfo/public_html/includes/bootstrap.inc).

any idea to solve this?

my dblog is filled with these too.

This problem is caused by the Features AJAX callback menu item having a title callback that doesn't always (/ever?) return a string.

The callback used is features_get_feature_components(). I have no idea why we need a title callback rather just a fixed menu item title - presumably not an accident. However, after switching from a title callback to a fixed title I didn't seem to have any problems with AJAX functionality.

Patch attached.

Wrong patch! Try this one.

Nice catch @David Sparks!
I think your patch makes sense.

Could you add steps to reproduce in the issue summary? I want to be able to compare before/after, before I commit this.

Sorry for the delay - done now.

It is funny, it was indeed statistics module that caused the drupal_get_title().

I checked other ajax router items like 'views/ajax' and 'system/ajax'.
I think the 'title' is not strictly necessary, but those also have it, so I think we are on the safe side by setting a fixed title.
(the default title callback is t(), so it will be translated, but that's ok)

Other ajax callbacks also use 'delivery callback', but we can do this later.

Nice job @David Sparks, thank you!

If anyone else still sees this message for some unrelated reason, please get a backtrace and open a new issue.