Cannot save existing view: "The operator is invalid"

Is this http://drupal.org/node/1207680 ?

I don't know where that string is coming from:

[merlin@furor views (7.x-3.x)]$ grep -R invalud *
[merlin@furor views (7.x-3.x)]$

Same error. Helped rollback to rc1.

I have had this same problem and it is not the same issue as being discussed in the other thread. Similar, but not the same.

I have had a look at the latest copy of Views dev (released today) and the misspelled string can be found.

[root@www views]# grep -Rn "invalud" *
handlers/views_handler_filter_in_operator.inc:362:      $errors[] = t('The operator is invalud');

In my case this error only appears on Views where I am using the IS NULL operator. The function causing the issue is as follows (handlers/views_handler_filter_in_operator.inc line 360)

 if (!in_array($this->operator, $this->operator_values(1))) {
      $errors[] = t('The operator is invalud');
    }

In my case $this->operator contains empty and $this->operator_values(1) contains Array ( [0] => in [1] => not in ).

The function $this->operator_values(1) only returns operators which require values. The empty and not empty operators don't and so it fails validation. If this line is changed so it includes a check against $this->operator_values(0) as well, then the validation fails further down with No valid values found (Line 384).

Looking at this validate function, there seems to be no support at all for the empty and not empty operators. Would it be best to just validate them at the start with a simple check and then leave the rest to those operators with values?

Adding in the following lines to handlers/views_handler_filter_in_operator.inc:, before the other operator check, has solved this issue for me.

if (in_array($this->operator, $this->operator_values(0))) {
      return $errors;
    }

This way if the operator is valid and does not require a value then no further validation is required. Does this sound like a good solution to the problem.

comment removed

+1

Please always write a proper patch, it's much easier to review.

For me error occurs only when I add "Location:Country" to Fliter Views.
No problem if it's "Location:City", "Location:Province", "Location:Phone"

Should it be another issue?

Hi dareine,

As requested, here is a patch file for those 3 lines. I have made it against the latest dev version which was released today (one with the spelling error corrected).

I've applied patch but it didn't help me

Yep, your issue is different to mine so most likely a different cause :)

#10 worked for me, no errors!

Rewrote the comment and commited the patch to both version. Thanks!