I posted this issue in the views-que ( #959668: Style Unformatted requires a row style but the row plugin is invalid ) but it seems that it is more ralated to panels.

I've been trying to migrate my site from one server to another. Everything seems to work fine, except that Views doesn't have any Style Plugins.

Style Unformatted requires a row style but the row plugin is invalid.
Style Grid requires a row style but the row plugin is invalid.

When I try to reimport the view I run into the same problem:

Row plugin fields is not available.
Unable to import view.

I didn't have skinnr installed, so it can't be related to this issue #921338: Uninstalling Skinr Breaks existing Views

Files: 

Comments

What leads you to believe Panels is involved in that at all?

... because disabling Panels is the only thing that makes it work ;-)

I am experiencing the same problem. I recently installed Panels 6.x-3.8.

After I created a panel, my other views content "disappeared" similar to the description in #2 #959668: Style Unformatted requires a row style but the row plugin is invalid.

In Views 6.x-2.11, I could no longer change the row style setting....it was set on "fields" but the fields selection area was grayed-out with "The style selected does not utilize fields." message. If I tried to select "node" style, I would get ".... the row plugin is invalid" error. This occurred on both view edits and when trying to create a new view.

Clearing cache did not help.

When I disabled Panels everything returned to normal.

Downgrading to Panels 3.7 fixed above related problems

Can downgrading to 3.7 be done even if the /update.php procedure has already been performed with 3.8 installed? Are the database tables' structure the same for 3.7 as 3.8?

If anyone could answer this soon, it would be a major help -- it will stop us from having to an elaborate rollback of our whole site this morning!

Downgrading to 3.7 worked fine for me (even I did the update.php after the 3.8 installation).
However, I guess it depends on your panels and views so .. no guaranty ;-)

I can't duplicate this. Using latest Views 2.x-dev and Panels 3.x-dev, this does not happen. There must be third component.

I can confirm that downgrading to Panels 3.7 solved the problem for me too.

Panels 6.x-3.7
CTools 6.x-1.8
Views Views 6.x-2.11

Hmmmmm, I did experience this initially, but now that I have upgraded Drupal to 6.19 from 6.15, I, like Merlin, can no longer produce the error. Can those with the error confirm they are on an earlier version of Drupal than 6.19?

CTools (6.x-1.8)
Views (6.x-2.11)

Using Drupal 6.19. All modules (except panels now that i've downgraded) are up to date.

Same for me as Jan Krummrey, I'm using Drupal 6.19. All modules (except panels now that i've downgraded) are up to date.

Ditto #10. Drupal 6.19. All modules up to date except panels. Had to roll panels back to 3.7.

As I stated earlier, I can't duplicate this. There must be a third component.

Please, those of you experiencing this, we need to figure out what the third component is. Just telling me you're also getting this won't help me reproduce it.

Status:Active» Postponed (maintainer needs more info)

Can you please check your apache/php/watchdog error logs and see what they say? Almost always when you see this kind of error, you'll see something there as well.

Another possibility might be extraneous whitespace added prior to the PHP opening tag in a theme or custom module file.

Ditto Ditto #10. Drupal 6.19. All modules up to date except panels. Had to roll panels back to 3.7.

What I did notice is that now with panels 3.7, the "panels field" row style is gone and everything is working ok.

I have also this error "requires a row style but the row plugin is invalid"

And in dblog I have these errors:

Invalid argument supplied for foreach() in /home/heyyoyo/sites/modules/acquia/views/plugins/views_plugin_query_default.inc on line 914.
Invalid argument supplied for foreach() in /home/heyyoyo/sites/modules/acquia/views/plugins/views_plugin_query_default.inc on line 990.

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'FROM node node INNER JOIN term_node term_node ON node.vid = term_node.vid WHE' at line 2 query: SELECT COUNT(*) FROM (SELECT FROM node node INNER JOIN term_node term_node ON node.vid = term_node.vid WHERE (node.status = 1 OR (node.uid = 1 AND 1 <> 0) OR 1 = 1) AND (node.type in ('site')) AND (node.language in ('en', '')) AND (term_node.tid = 6) ) count_alias in /home/heyyoyo/sites/modules/acquia/views/plugins/views_plugin_pager.inc on line 142.

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'FROM node node INNER JOIN term_node term_node ON node.vid = term_node.vid WHE' at line 2 query: SELECT FROM node node INNER JOIN term_node term_node ON node.vid = term_node.vid WHERE (node.status = 1 OR (node.uid = 1 AND 1 <> 0) OR 1 = 1) AND (node.type in ('site')) AND (node.language in ('en', '')) AND (term_node.tid = 6) LIMIT 0, 5 in /home/heyyoyo/sites/modules/acquia/views/plugins/views_plugin_query_default.inc on line 1134.

Status:Postponed (maintainer needs more info)» Active

Same problem here.
Happened right after I upgraded to ctools 1.8 and Panels 3.8.

Any help much appreciated.

Same problem here.
Happened right after I upgraded to ctools 1.8 and Panels 3.8.

Any help much appreciated.

I also have this problem, only I had upgraded ctools and panels some time ago and everything seemed to be fine. This problem was manifest after I moved my modules to a new contrib folder (as opposed to placing everything in modules alone). I disabled all the modules, moved the files, re-enabled the modules, cleared my caches, and all of my views had variations of this "...row plugin is invalid" error. The only view style that still worked was the table output.

After reverting the Panels module to 3.7, the error went away (initially, the views still didn't work, until I cleared my caches again). Swapping 3.8 back in and clearing my caches empties the view's results. Editing the view (and trying to preview it) is where I see the actual errors.

Hopefully, I can find some other clues after I fix unrelated issues.

Ok, found the problem. I need to roll a patch but can't just now. For reference, the problem is that there's some junk in the panels_views_plugins() function that's breaking all row styles except for Panels row styles.

In plugins/views/panels.views.inc the entire array 'parent' should be deleted.

The entire file should be:

<?php
/**
* Implementation of hook_views_plugins
*/
function panels_views_plugins() {
 
$plugins = array(
   
'row' => array(
     
'panels_fields' => array(
       
'title' => t('Panel fields'),
       
'help' => t('Displays the fields in a panel rather than using a template.'),
       
'handler' => 'panels_views_plugin_row_fields',
       
'path' => drupal_get_path('module', 'panels') . '/plugins/views',
       
'theme' => 'views_view_fields',
       
'uses fields' => TRUE,
       
'uses options' => TRUE,
       
'type' => 'normal',
       
'help topic' => 'style-row-panels-fields',
      ),
    ),
  );
  return
$plugins;
}
?>

Status:Active» Fixed
StatusFileSize
new2.22 KB

Ok, checked in a fix. Actual patch used is attached.

Yeah!!!

That did it for me. Thanks Merlin for staying on the case.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

This patch introduced a bug (#1025716: Empty fields when using Panel fields) in the Panel fields row style for Views.

If anyone can chip in over there, a few of us affected would be grateful.

Status:Closed (fixed)» Active

Core 6.20
Ctools 1.8
Panels 3.9
Views 2.12
Below is the error I get before applying the patch.

Unknown column 'node_data_field_watchstander_date.field_watchstander_date_value' in 'where clause' query: SELECT DISTINCT node.nid AS nid, node.type AS node_type FROM node node INNER JOIN node_access na ON na.nid = node.nid WHERE (na.grant_view >= 1 AND ((na.gid = 0 AND na.realm = 'all') OR (na.gid = 2 AND na.realm = 'node_privacy_byrole_role') OR (na.gid = 3 AND na.realm = 'node_privacy_byrole_role') OR (na.gid = 255 AND na.realm = 'node_privacy_byrole_user'))) AND ( ((node.status <> 0) AND (node.type in ('assign_duty'))) AND ((DATE_FORMAT(STR_TO_DATE(node_data_field_watchstander_date.field_watchstander_date_value, '%Y-%m-%dT%T'), '%Y-%m') <= '2011-02' AND DATE_FORMAT(STR_TO_DATE(node_data_field_watchstander_date.field_watchstander_date_value, '%Y-%m-%dT%T'), '%Y-%m') >= '2011-02')) ) in public_html/sites/all/modules/views/includes/view.inc on line 775.

The line referenced is

$result = db_query($query, $args);

I have applied the patch listed
http://drupal.org/files/issues/1025716-broke-empty-fields_0.patch

after all of this I still get the same message and the watchdog as listed
Unknown column 'node_data_field_watchstander_date.field_watchstander_date_value' in 'where clause' query: SELECT DISTINCT node.nid AS nid, node.type AS node_type FROM node node WHERE ((node.status <> 0) AND (node.type in ('assign_duty'))) AND ((DATE_FORMAT(STR_TO_DATE(node_data_field_watchstander_date.field_watchstander_date_value, '%Y-%m-%dT%T'), '%Y-%m') <= '2011-02' AND DATE_FORMAT(STR_TO_DATE(node_data_field_watchstander_date.field_watchstander_date_value, '%Y-%m-%dT%T'), '%Y-%m') >= '2011-02')) in /public_html/sites/all/modules/views/includes/view.inc on line 775.

Status:Active» Closed (fixed)

Do you often re-open random issues completely unrelated to bugs and apply patches that are already in released versions?

panel is the solution of this error?