What is the cause of this? Have posted two other times before and appears another user posted on 03/20/07 with no follow-up. Can anyone assist?

Thanks.

warning: Invalid argument supplied for foreach() in /home/domain/public_html/subdomain/modules/views/views_query.inc on line 81.
warning: Invalid argument supplied for foreach() in /home/domain/public_html/subdomain/modules/views/views_query.inc on line 16.
warning: Invalid argument supplied for foreach() in /home/domain/public_html/subdomain/modules/views/views_query.inc on line 189.
warning: Invalid argument supplied for foreach() in /home/domain/public_html/subdomain/modules/views/views_rss.module on line 55.

CommentFileSizeAuthor
#2 views_query.inc_.txt20.67 KBdrupalgirl

Comments

moshe weitzman’s picture

Priority: Critical » Minor
Status: Active » Postponed (maintainer needs more info)

you don't give nearly enough info.

what URL
what perms do you have. are you logged in?
what modules are you running

drupalgirl’s picture

Priority: Minor » Critical
StatusFileSize
new20.67 KB

Thanks for replying. Hope all this helps. I don't want to be a nuisance. This has been an unresolved issue for me since installing the Drupal core 5.1 and adding Organic groups latest ver. module and required Views and Views RSS on March 8th. Let me know if you need anything further.

ANSWERS TO YOUR QUESTIONS:

- This is at the top of a group page. Appears on any group page no matter how many I create and post contenty to.

- Yes. I am logged in for testing while logged in. As admin in Firefox and as a test user in EI. Logged in or not gets this error. Also tested both while not logged in.

- Using Organic Groups module. Was first posted to support forums 3 weeks ago in detail with no follow up. Then posted in Organic Views 2 weeks ago and it was closed by someone saying it was off topic so I posted here.

- Perms? What's that? See attached views_query.inc v 1.51.2.5 2007/01/21 23:17:38 merlinofchaos

http://drupal.org/node/125737 Forum » Support » Post installation 03/7/2007

http://drupal.org/node/129915 Content display » Views » Issues 03/21/2007

Referenced third party issue post. Same situation as mine here: http://drupal.org/node/129599 Community » Organic groups » Issues 03/20/2007

petrescs’s picture

Please see if this helps http://drupal.org/node/129599#comment-227820
In which folder is your og module installed?

drupalgirl’s picture

Folder OG module is installed is in root/modules/. Only Views whose names start with og_ghp_ are eligible.

I have posted for help in Views project too and still awaiting support there 6 weeks later. OG homepage view must be created in Views module. Views module ADD view returns a blank page so can't create the required og_ghp_ View. Impacts OG teampage in the way indicated with errors. OG home page returns "Page not found". Until I can create a required OG view this problem will continue to occur unresolved. Increasing memory does not help. Hope this helps.

Have lastest OG, OG teampage and Views versions installed.

moshe weitzman’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

i can't really see any actionable item here. please reopen with more info if still a problem.

drupalgirl’s picture

Title: Organic Groups issue with Views » Organic Groups issue with Views CRITICAL
Status: Closed (fixed) » Active

RE-OPENED. Problem still exists! How could there be no actionable items? People are asking for help all over the place regarding this issue. I provided all the information I could and answered your questions. It didn't just fix itself while awaiting help all these weeks.

Please provide a workable solutions not just close it without assistance. I have already posted and reposted this issue since March 23, 2007 and no one seems to be interested in fixing or seriously addressing or providing real answers to fixing the problem.

I'm not the only person with this problem. What more do you need to help get to the heart of the problem? Blood and Guts?????

There is a legitimate issue between OG module and Views since OG mod now requires Views module to properly function. What is the correct directory path structure for views module? I heard that it was changed from what it once was and that OG module might have problems with the new structure.

The bottom line is that Views module installed directory structure might be off. It doesn't list available views even though they are inside of the Views module folder as views_xxx.inc. like this root/modules/views/views_forum.inc, views_book.inc and so on.

FOR EXAMPLE:
views.pot for book doesn't list as modules/views/view_book.inc but instead lists like this. The include files are all installed inside of modules/views/ AND NOT modules/

#: modules/views_book.inc:23
msgid "Book: Parent Node"
msgstr ""

#: modules/views_book.inc:26
msgid "This allows you to filter books based on parent node."
msgstr ""
----------------------------------------------

Further complicating issue, installed Views module Admin user cannot "Add" a "View" because Add action returns a blank page. I've posted this elsewhere too with no workable solution from Views team.

Are these not actionable items? One need only look at the code and structure. Please provide a workable solution or assign it to someone who cares. But please don't close this CRITICAL ISSUE. Leave it to someone who is willing to offer a workable solution.

Sheeesh!

skor’s picture

Title: Organic Groups issue with Views CRITICAL » Organic Groups issue with Views
Priority: Critical » Normal

drupalgirl,
I understand your frustration, sometimes issues go weeks without being responded to. Often you need it fixed before the module author does. Particularly when the issue involves two or three modules, it it difficult to for module authors to get together to investigate the issue.

But it seems to me that you've lost sight of a very important fact. These developers of drupal core and contributed modules do not OWE you anything. Only they can decide if it is more important to investigate your issue, someone else's (maybe thier own) issue, work on another module, or spend time working on new features, (Drupal 6 code freeze coming up July 1). Your priorities are not theirs and normally, you cannot decide their priorities for them.

There is, however one way that you could influence their priorities. If this issue is truly CRITICAL to you and perhaps others, consider pooling your re$ources with others who are seeing the same problem, and offer a bounty for a fix. That, after all, is a true measure of how critical this issue is.

skor’s picture

Version: 5.x-2.2 » 5.x-3.1

Here's are my configs:

I had an old test site using Drupal 5.1, OG 5.x-2.2, views 5.x-1.6-beta5 (see note below)
No error message.

I updated OG to 5.x-2.4 and ran update.php. no error messages.

Then I upgrading to OG 5.x-3.1, ran update.php (though it didn't appear to be necessary) and most of my views are fine. but I have a calendar view with a filter on "Og: Post in specified group". When I try to edit that view, or go to it's url, I get:

warning: Invalid argument supplied for foreach() in /var/www/html/drupal-5.1/includes/form.inc on line 945.

and when I am editing the view, in the filter section, I there are no longer any options under "Og: Post in specified group" (used to say "equal to /not equal to").

Tried downgrading to OG 5.x-2.4, but the condition persists.

When I delete that filter, the message goes away, and re-appears when I add that filter again.

** note on my Views module version. I upgraded this site from 5.x-1.5 to 5.x-1.6-beta5 several weeks ago and ran update.php. But for some reason it still shows 5.x-1.5 on admin/build/modules and on the update status page. Not sure why that is.

ddyrr’s picture

I used to get the same error as Skor when one of my select boxes was empty. In my case, it was for any user that was not a member of at least one group. I had the Author group module, and the author would be empty. I did a patch to only show the select box when the user was a member of a group. I have a feeling one of those select boxes must be empty, and that's what is causing your error.

drupalgirl’s picture

Skor,

Is it Skor of Scold? I give up. I was introduced to Drupal 3 months ago. I really love with the exception of OG's new dependence on Views module. If I had known that a Drupal 6 was being releases on July 1st I wouldn't have bothered installing 5.1 in March let alone ask for help.

I surely didn't imply that I was OWED anything. It's not a comfort to have someone randomly "close" your posted issue so that others would think it resolved. The ability to set priorities is accessible and opened to the poster. Would I set it to normal if it is critical to me? It didn't feel fine to have someone decide to change the priority of my post from Critical to Minor to Normal. That would have others who might be able to help assume it's really no big deal to the original poster. It doesn't help matters either to have someone appearing to assist ask questions and then close the post after you have provided answers to those questions.

Regarding pooling resources I have received numerous other tips and ideas from other users in my same situation, but they were not pertinent to resolving my issue. Hence, I contunue to await a kind soul to offer assistance. I have also offered up solutions to help others in need. moshe weitzman asked specific questions on March 30, 2007, which I promptly answered on April 2, 2007. What set me off was the closing of my issue on May 23, 2007 after I had respectfully provided the requested information. Closing my issue would result in no one bothering to look at it.

I could very well resolve my own issue if someone could answer the question: What it the correct directory structure of Views Module posted above on May 30, 2007? I had heard that the views module dir install structure had changed critically impacting dependent modules like OG, and that the views .inc files shouldn't have installed directly into the /modules/ folder but in modules/views/, which could be the problem.

Thanks anyway for at least playing around with other versions. I had already upgraded up to 3 views since first installing in March with the same problems. I had hoped someone had found a solution to the missing Views List and Blank Add page though.

ezra-g’s picture

Title: Organic Groups issue with Views » og_view_group generates views errors

I'm having this problem too and I think I've found the source: In og_view_group on line 1050 $view = views_get_view(variable_get('og_home_page_view', 'og_ghp_ron')); it seems that variable_get is not returning any value -- neither the value of the requested variable nor the value of the second parameter which it is supposed to return in case the requested variable has been set.

To troubleshoot, I've tried a drupal_set_message("test " . variable_get('og_home_page_view', 'og_ghp_ron')); and see only "test". That seems bizarre to me. Shouldn't that be impossible? When I modified line 1050 to be $view = 'og_ghp_ron;, the views errors went away.

I'll hold off on submitting a patch supplementing the conditional check on line 1052 if ($views_available[$view->name] == "disabled") { with a check to see if $views_available[$view->name] has been set.

ezra-g’s picture

I should probably say more than "I'm having this error, too." When I browse the page view of an OG homepage node, I receive the following views errors. A debug_backtrace() pointed me towards the og_view_group function. Hope that's helpful :-).

* warning: Invalid argument supplied for foreach() in /Users/ezra/Documents/Developer/htdocs/dev/cr/sites/all/modules/views/views_query.inc on line 85.
* warning: Invalid argument supplied for foreach() in /Users/ezra/Documents/Developer/htdocs/dev/cr/sites/all/modules/views/views_query.inc on line 16.
* warning: Invalid argument supplied for foreach() in /Users/ezra/Documents/Developer/htdocs/dev/cr/sites/all/modules/views/views_query.inc on line 201.
* warning: Invalid argument supplied for foreach() in /Users/ezra/Documents/Developer/htdocs/dev/cr/sites/all/modules/location/contrib/location_views/location_views.module on line 1051.
* warning: Invalid argument supplied for foreach() in /Users/ezra/Documents/Developer/htdocs/dev/cr/sites/all/modules/views/modules/views_node.inc on line 785.
* warning: Invalid argument supplied for foreach() in /Users/ezra/Documents/Developer/htdocs/dev/cr/sites/all/modules/views/views_rss.module on line 56.

moshe weitzman’s picture

Status: Active » Closed (fixed)

i've never seen variable_get() ignore the default value. please dive in. anyway, that would be a core bug.

bsuttis’s picture

Status: Closed (fixed) » Active

I'm getting very similar errors (line numbers are off by 1-5), but I'm not using OG at all, the module doesn't exist in my installation.

I seem to random get the errors when uploading images (via cck imagefield) to my cck node types. To make matters more confusing, the same field in some node types doesn't rhow back the errors, while others do.

Apologies if I shouldn't reopen this, and I'm aware the above doesn't give much to go on, but I'm mentioning this because perhaps it's not an OG problem? Maybe it's Views?

moshe weitzman’s picture

Status: Active » Closed (fixed)
rlavigne99’s picture

Easy buddy, this is open source not slave labor. These guys are creating this stuff for your use for free. I am sure someone will get to fixing it soon.

dugh’s picture

I see this error too.

I don't see the og_ghp_ron view anymore. I think that's the problem. But even completely uninstalling organic groups and reinstalling, the og_ghp_ron view is not re-created.

Is there a way to fix this?