Warning appears on site after enabling taxonomy_term view

For me critical is wsod.

+1
I have same problem when enabling taxonomy_term view.. Any ideas?

The error is in sites/all/modules/views/modules/taxonomy/views_plugin_argument_validate_taxonomy_term.inc in line 73.

        $tids = new stdClass();
        $tids->value = $argument;
        $tids = views_break_phrase($argument, $tids);

The given attribute “value” prevents views_break_phrase to recreate it. On the other hand views_break_prase will construct an stdClass() object if it is not given as second argument. So we can reduce this three lines to the following:

$tids = views_break_phrase($argument);

Somewhere thre should be another issue to exact this problem. There is a patch included for a simpletest for this.

I would be happy if this could be found and then be commited addtional.

Related issues contain
#319425 (won't fix)
#411566 (another patch and solution)
#407538
#327307

but I didn't find a test.

I am using views 6.x-2.10 and the problem still exists. Will this patch work for 2.10? What needs to happen to bring this into a release.

Try the patch. test the patch. And review the patch. Thats what you can do.

When I try the patch I get:

* warning: Missing argument 2 for views_break_phrase(), called in /home3/jewishmo/public_html/sites/all/modules/views/modules/taxonomy/views_plugin_argument_validate_taxonomy_term.inc on line 73 and defined in /home3/jewishmo/public_html/sites/all/modules/views/includes/handlers.inc on line 788.
* warning: Missing argument 2 for views_break_phrase(), called in /home3/jewishmo/public_html/sites/all/modules/views/modules/taxonomy/views_plugin_argument_validate_taxonomy_term.inc on line 73 and defined in /home3/jewishmo/public_html/sites/all/modules/views/includes/handlers.inc on line 788.
* warning: Missing argument 2 for views_break_phrase(), called in /home3/jewishmo/public_html/sites/all/modules/views/modules/taxonomy/views_plugin_argument_validate_taxonomy_term.inc on line 73 and defined in /home3/jewishmo/public_html/sites/all/modules/views/includes/handlers.inc on line 788.
* warning: Missing argument 2 for views_break_phrase(), called in /home3/jewishmo/public_html/sites/all/modules/views/modules/taxonomy/views_plugin_argument_validate_taxonomy_term.inc on line 73 and defined in /home3/jewishmo/public_html/sites/all/modules/views/includes/handlers.inc on line 788.

Thanks for the help.

can you tell, which views version you using?

In my installation the function views_break_phrase() is defined as

function views_break_phrase($str, $filter = NULL) {

I'm using Views 6.x-2.8
Update: The patch is for 6.x-2.10. My local copy of views was slightly outdated.

6.x-2.10

I'[m having the same problem as denverdataman in #10. after applying the patch I have even more error messages than before.

I read with taxanomy menu that it's enough to rebuild it but I couldn't find how to do it. I ran cron as well but that didn't help.

Any thoughts?

Views 6.x-2.10

You can rebuild menus by visiting the modules page and clicking the submit button.

I have the "Invalid argument ..." problem too, line 1651 (appears 4 times)
Tried to solve with the patch, but got the same error message as #10 (7 times)
Undid the patch, problem back of course

Drupal 6.17
views 6.x-2.11
taxonomy_term view enabled
not using Taxonomy Menu module

And yes, when not using the taxonomy_term block, error messages disappears!
Tried with a clone of this block just in case, but gives the messages too.

Has anyone ever been able to figure out issue? The error comes up "only" when enabling taxonomy_term view.

Drupal 6.19
views 6.x-2.11
taxonomy_term view enabled
taxonomy terms listed in a block by a *term* type view <- that's when the error appeared.
not using Taxonomy Menu module

There must be some incompatibility because I have this error only on one of my sites.

Well, the patch can't work the way views_break_phrase() is set up.

I'm unable to reproduce this, so without clear reproduction instructions (like, from a base Drupal install) I'm not sure what to suggest. There's clearly some other module interfering or othewise setting up the conditions for this, but I don't know what it might be.

unable to reproduce, no activity for 30 days