Allow to use fields on style plugins/row plugins without fields

+++ b/plugins/views_plugin_style.incundefined
@@ -88,11 +88,15 @@ class views_plugin_style extends views_plugin {
+    return $row_uses_fields
+      ||!empty($this->definition['uses fields'])
+      || !empty($this->options['uses_fields']);

This could probably be one line, I think its more confusing this way. Also, there is a missing space between ||!empty

+++ b/plugins/views_plugin_style.incundefined
@@ -166,6 +170,7 @@ class views_plugin_style extends views_plugin {
+    $options['uses_fields'] = array('default' => FALSE);

Doesn't this need a 'bool' => TRUE for proper exporting? Though I notice from the patch context that others are missing it, perhaps that just needs a cleanup?

I think the "force fields" checkbox should only be shown when valid. It will just be confusing if the style or row plugin use fields.

When will this fix be released?

I'm interested in this.
I'll have to test if it needs a re-roll?

So, this fix has been modified in 7.x-3.x-dev, when will it be released as 7.x-3.4? It seems that the patch has already been written and committed to the codeline. Just trying to understand the process.

There's no commit link, but based on the dates, with 7.x-3.3 = 2012-Feb-22 and no releases since then ... I guess yeah - we should be waiting on the next version number and it should be there.
My misunderstanding (re the re-roll) above was just confusion by me - I thought there had been a views release more recently than Feb.

An alternate to using the "Content" row plugin is to use fields with the "Content: Rendered Node". Within the Rendered Node field settings, you can choose Display = "Show complete entity" and then choose a View Mode. The output provides the similar results to using the Content format. (Thanks to pixelwhip from http://drupal.org/node/1619340)