Invalid argument supplied for foreach() in feature module

All of these warnings look like a case of a badly declare hook_features_api() somewhere in your codebase. Do you want to do some debugging and track down where that declaration is?

I get these errors when using this patch: https://drupal.org/node/624018#comment-3270940 with wysiwyg untill I enable exportables... then they go away.

I'm seeing the same issue:

It seems to be related to this commit: http://drupal.org/node/884624#comment-3349396

-    $export_key = $schema['export']['key'];
-    // If a list callback is available use it, otherwise fallback to generating
-    // options from ctools_export_load_object().
-    if (function_exists($schema['export']['list callback'])) {
-      $objects = $schema['export']['list callback']();
-      $options = drupal_map_assoc(array_keys($objects));
+    if (!empty($schema['export']['list callback']) && function_exists($schema['export']['list callback'])) {
+      $options = $schema['export']['list callback']();
     }
-    else if ($objects = ctools_export_load_object($component, 'all')) {
-      $options = drupal_map_assoc(array_keys($objects));
+    else {
+      $options = _ctools_features_export_default_list($component, $schema);

Before this commit, list_callback function should return a list of objects. After the commit, list_callback have to return an array.

I'm using the 'old' method in Input Formats module and in the Wysiwyg Ctools patch. My question is: we have to modify Features module? or I have to modify input formats module and the wysiwyg patch?

IMO this patch will be enough and is compatible with both kinds of list_callbacks returns, objects and keys.

@dagmar: Nope, the list callback should provide an array of machine_name => human readable for each exportable object. The patch uses array_keys() which basically throws out the human readable names -- not good.

My suggestion is to make a fix upstream to your list callback in Input Formats.

So, assuming input formats is the raise of this issue. I have committed a patch to fix the problem. http://drupal.org/cvs?commit=414114

Please re-open if this issue persist.