Make exposed form available as extra field

Thanks for the patch. But I have problem that exposed filters field rendered on top of the page regardless of the weight of this field. Any ideas?

Nevermind, it is fixed in the dev branch.

Patch works, though I ad to clear my cache to see the effects.

Perhaps this should have a hook_update_N() to take care of that?

Also, the exposed form is showing above other (real) fields even though display settings have those higher up.

Here's a reroll with a fix for the problem with the exposed form weight -- the key in the build array needs to match what is set in hook_field_extra_fields().

Regarding the hook_update_N() -- it would actually mean adding a whole install file for just that (for now). Is it worth it? Should users expect to clear their cache on a version update anyway?

I've recently become a maintainer of this module...this seems like a great patch, let's all take another look and mark it RTBC. I'll handle the hook_update_N piece. EVA's caching issues need a lot of attention anyway.

Please find an updated patch attached.

Regarding flushing the caches: that is not an issue of hook_update(), but eva_field_extra_fields(). It is not called every time you add/remove an exposed form.
I tried to set the exposed form field ALWAYS, and adding a 'visible' value:

//        if ($view['exposed form']) {
          $extras[$entity][$bundle]['display'][$view['name'] . '_' . $view['display'] . '_' . 'form'] = array(
            'label' => ((empty($view['title'])) ? $view['name'] : $view['title']) . ' (' . t('Exposed form') . ')', 
            'description' => t('The exposed filter form of the view.'),
            'weight' => 9,
            'visible'=> $view['exposed form'],
          );
//        }

That works (also, you don't need the update_N anymore), but the 'apply' is still visible (in my bartik theme). Therefor, it is not included in the attached patch.

(PS. It was nice testing this feature, but it doesn't help my use case. I want an exposed form in a Node edit page, and save the values together with the node.)

This looks good. I'm testing it now, others should do the same!

New patch attached.

Added a form alter to the views ui that clears the field cache when you save a view. This solves the problem of making sure that the exposed form field only shows when an exposed form exists for the view since after a view is changed and saved, field information will be rebuilt.

It solves the bigger cache problem as well: EVA views don't show up when first created unless the cache is cleared. This will clear the cache when the EVA view is initially saved.

Also a few small changes to the way the field is labelled on the 'Manage Display' tab.

Anyone want to give it a test / a look?

And here's the actual patch from #11. It mostly comes from #9 and before. The technique for the form_alter on views save came from here: #974576: Is there a technique (hook?) To intercept the view when i'm saving it ?.

This has been committed to the dev branch. New release coming soon.