No "Products Contributing to Goal" in panel or View

There isn't currently a Views field handler that displays the progress bar. To work around this, you could switch the view from from displaying Fields to Content, and then choose Teaser or some other view mode where the progress bar is present. You can create custom view modes using Display Suite, if needed.

You can use display suite which you can then create a content type grid to gain control over the teaser display.

I've added in this functionality in the simplest way possible:

- I have the formatter check to see if we're in a view with fields
- If we're in a view, pick up the product settings from the default field settings
- Unset the formatter's commerce product picker, because we aren't using it for the view

This would require the module to depend on the wee helper-module "field_formatter_settings" which adds a hook that didn't make it into core that allows us to intercept formatters.

Do we actually need to make field_formatter_settings a dependency? It seems like we can just make it optional for people who want to use this with views fields and panels. We can add a note in the README and on the module page about it.

Second thing: I haven't had time to test this yet, but this code looks like it would break the existing functionality of the module, wouldn't it?

<?php
function commerce_goal_field_formatter_settings_form_alter(array &$settings_form, array $context) {
  if(array_key_exists('commerce_goal_products_field',$settings_form)) {
    unset($settings_form['commerce_goal_products_field']);
  }
}
?>

I haven't used field_formatter_settings before, so I could be missing something, but shouldn't there be a check there to determine if we're actually in a panels or views field context?

hahahaha oh my goodness yes, lol, it totally does break the original formatter too. I will just toddle off and add that check. Thanks ;)

So, this does the trick:

  if(array_key_exists('commerce_goal_products_field',$settings_form) && $context['form_state']['form_id'] == 'views_ui_config_item_form') {
    unset($settings_form['commerce_goal_products_field']);
  }

Though if we're considering expanding it to panels, maybe it's better to check for the "_custom" view mode?

Okay, I spent some time looking at this today, and I decided to redo this patch in a different way. Rather than getting the default value (which doesn't always work), I'm checking to see if we're in an actual entity/bundle context, and if not, then pulling all the product reference fields from all the bundles that this field is assigned to. This makes the form work like it does on the Manage Display page. (except that it may have more options if the field is used on multiple content types)

I tested this with Views fields and it works. I'm not sure what people are doing with Panels exactly, so I'm not sure what to test. I suspect it may work with Panels, though, as well.

@Renee_S (and anyone else following this issue), please test the attached patch and let me know if it works. You'll need to back out your other patch. This patch does not require field_formatter_settings module.

Yes, zengenuity, this worked for me in Views, and in Panels (adding it as a field.)

Committed this patch. Will roll a new stable release momentarily.