Closed (fixed)
Project:
Views Field View
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Major
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
30 Oct 2012 at 17:05 UTC
Updated:
12 Jul 2013 at 19:06 UTC
Hey guys,
I've been having some issues with this module since I installed it, and I thought I'd ask if anyone else has come across this issue. Firstly, I'm using the latest dev version of this module and Views 6.x-3.0. Here are the PHP warnings:
warning: Invalid argument supplied for foreach() in /home/[site]/public_html/mc/sites/all/modules/views/plugins/views_plugin_query_default.inc on line 924.
warning: Invalid argument supplied for foreach() in /home/[site]/public_html/mc/sites/all/modules/views/plugins/views_plugin_query_default.inc on line 1000.
warning: Invalid argument supplied for foreach() in /home/[site]/public_html/mc/sites/all/modules/views/plugins/views_plugin_query_default.inc on line 924.
user warning: 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 drupal_node node' at line 2 query: SELECT DISTINCT FROM drupal_node node in /home/[site]/public_html/mc/sites/all/modules/views/plugins/views_plugin_query_default.inc on line 1153.
So what I've done is set up two brand new views - one of them has nothing out of default except for a 'Title' field. The other has the 'Global: View' field, referencing the other one. What this should do is output a list of all nodes (there are no filters or arguments) but what it does is output nothing with those messages above.
Any ideas? I'd really appreciate any help anyone could give!
Comments
Comment #1
damiankloip commentedAre you trying to use the aggregation setting? If so, you should turn this off, then try.
Comment #3
perfectcu.be commentedI'm getting this exact same error. It only occurs when viewing the view page as an anonymous user. When I'm logged in, it works as expected.
Comment #4
perfectcu.be commentedIn my particular case this turned out to be a permissions use on the CCK fields I was using in the query, and nothing wrong with this module at all.
For anyone else who comes across this problem, check out this post:
https://drupal.org/node/291840#comment-975829