Hello.

I have just downloaded the latest Version of the Views module for Drupal 6, I am new to this so I have probably made a big BOO BOO.

I enabled the taxonomy_term example and tried to test the FAQ taxonomy term that exists on my site and when I click Preview I get a lovely warning:

* warning: Invalid argument supplied for foreach() in /home/ucanukor/public_html/sites/all/modules/views/includes/handlers.inc on line 628.
* warning: Invalid argument supplied for foreach() in /home/ucanukor/public_html/includes/common.inc on line 1489.
* warning: Invalid argument supplied for foreach() in /home/ucanukor/public_html/sites/all/modules/views/includes/handlers.inc on line 628.

Yikes! what have I done wrong ..any ideas?

I've tried asking the question in the support forums, only to find that somebody else has the same problem. They suggested I post it here.

I have one other question: Drupal is free, the modules and themes are free...eh...em.... how does anybody pay the bills doing this?

I'll take a guess at the answer: The idea is that we all contribute and in return we all benefit!

Is that right?

Kind regards,

Cliff...

Thanks merlinofchaos and all the other contibutors

Comments

merlinofchaos’s picture

Title: Basic Problem...I think! » taxonomy term argument can cause warnings with invalid input
Category: support » bug

Oh yes, this is a bug. I see the basic problem, will get a fix in shortly.

merlinofchaos’s picture

Priority: Minor » Normal

A couple of points: If Views spits a warning, it's almost certainly a bug somewhere. It may not be Views' fault, but it's definitely a bug. In this case, it's Views' fault.

Second, the money, for me, comes from the fact that my contributions are so noticeable and valuable that I am considered a top tier Drupal guy and since good Drupal guys are always in short supply, it's easy for me to find employment. And I gravitate toward employers that want me to work on this, because it helps them.

ludo1960’s picture

OK thanks again merlinofchaos,

both for your answers and your contributions to Drupal...........Hmmm..... a "top tier Drupal guy", what method would you suggest for a middle tier Drupal guy to approach aforementioned top tier Drupal guy for advice on a project?

merlinofchaos’s picture

Status: Active » Fixed

Fixed in CVS.

(Sorry, I don't often have time to give advice on projects).

ludo1960’s picture

Nice one, thanks again!
I know you don't have time to spare for advice but as we say in Scotland "A shy bairn gets nowt!"

shedevches’s picture

I feel like a goose, but I see the new CVS.. backed up views_ui.module, copied the new CVS into a file called views_ui.module, overwrote the file on my server. I still get similar errors as ludo1960 - am I right in thinking that I had the same problem as he did?

* warning: Invalid argument supplied for foreach() in /home/storefin/public_html/sites/all/modules/Content/views-6.x-2.0-beta3/views/includes/handlers.inc on line 628.
* warning: Invalid argument supplied for foreach() in /home/storefin/public_html/includes/common.inc on line 1489.
* warning: Invalid argument supplied for foreach() in /home/storefin/public_html/sites/all/modules/Content/views-6.x-2.0-beta3/views/includes/handlers.inc on line 628.

I get this error when clicking on any "tag" on my site.

Is there something else that I'm supposed to do?

Sorry.. thought that doing the above seemed the most logical to try (although none of it is really that logical to me) but now I'm stumped.

merlinofchaos’s picture

Umm. You must not upgrade just part of Views, that's going to cause all kinds of nasty problems.

shedevches’s picture

I was getting the same error before I uploaded that.. so is the CVS just for the next release then?
Or can I implement it now? I don't "get" the CVS thing obviously.. sorry Merlin.. it's so crap not knowing where to ask about this stuff.

merlinofchaos’s picture

You can run out of CVS but you have to update the entire module. The files are synchronized with each other.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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