2 different things seem to be going on with the Views upgrade to 7.x-3.4:

  1. This issue, Update to 7.x-3.4 un-sets the boolean operator in filters seems to be solved with manually re-setting the boolean operators, which can be done from the UI. This problem is based on updates implemented from this issue Why is there no "is all of" operator for select list filters?
  2. Several of us are experiencing the loss of Views with the 3.4 upgrade and our operators are remaining checked in the UI, however. We finally found out (reference comment #44 below) that the upgrade to 3.4 also made the time-based cache in Advanced options under Views break the views if it was activated. A new issue for that has been opened here: Upgrade from 7.x-3.3 to 3.4 makes time-based cache break Views. This can be helped manually in 3.4 by setting the cache to "none," although you will lose caching features and may slow down your site.

Views maintainer dawehner asked me (couturier) to write a warning message for the Views 7.x-3.4 release page to be posted until this bug is fixed, and this is what I submitted to him:

WARNING: Maintainers are working to fix a bug that was found after the 7.x-3.4 release that causes some Views pages, blocks, attachments and feeds to disappear after upgrading from 3.3 to 3.4. Stay informed of progress at the following link: 7.x-3.4 Upgrade is cancelling boolean operator settings. It is recommended to wait to upgrade until this bug has been fixed.

Here's the original message that initiated this issue:

Just updated to 7.3.4 and got this error message on a previously working views

Notice: Undefined index: in in views_handler_filter_in_operator->admin_summary() (line 307 of /home/engworld/public_html/bibleandwomen/sites/all/modules/views/handlers/views_handler_filter_in_operator.inc).

seems like an old bug comes back.

#45 cache-issue-3.jpg31.79 KBcouturier
#44 cache-issue.jpg0 bytescouturier
#36 views-1742942-36.patch7.43 KBtim.plunkett
FAILED: [[SimpleTest]]: [MySQL] 1,556 pass(es), 1 fail(s), and 0 exception(s).
[ View ]
#36 interdiff.txt2.49 KBtim.plunkett
#34 1742942-filter_list-test.patch6.48 KBdawehner
FAILED: [[SimpleTest]]: [MySQL] 1,556 pass(es), 1 fail(s), and 0 exception(s).
[ View ]
#32 1742942.patch978 bytesdawehner
PASSED: [[SimpleTest]]: [MySQL] 1,555 pass(es).
[ View ]
#27 1742942.patch639 bytesdawehner
PASSED: [[SimpleTest]]: [MySQL] 1,555 pass(es).
[ View ]
#25 view.txt18.57 KBluisasasi
#17 Broken 3.4 View code10.91 KBcouturier
#17 Screenshot 3.4, broken18.67 KBcouturier
#17 Screenshot 3.3, working54.76 KBcouturier
#15 1742942-filter_list-in-operator.patch926 bytesdawehner
PASSED: [[SimpleTest]]: [MySQL] 1,555 pass(es).
[ View ]
#4 Views-7x_3_3.jpg66.1 KBluisasasi
#4 Views-7x_3_4.jpg55.17 KBluisasasi


Title:7.x-3.4 Upgrade is cancelling boolean operator settingsNotice: Undefined index: in in views_handler_filter_in_operator
Component:page displays» Views Data
Status:Needs work» Active

same here... plus my view suddenly has a pager where it is set to not use one (see: http://drupal.org/node/1744300)

when i try to save the view i get this error:
Notice: Undefined index: not in in views_handler_filter_in_operator->admin_summary() (line 307 of /sites/all/modules/views/handlers/views_handler_filter_in_operator.inc).

The operator is invalid on filter: Content: Status.

Where "Status" is a field i've created on a node type. When I try to remove the field by clicking "Remove", it doesn't actually get removed from the list of filters and i can't save the view, because the error keeps on keepin' on.

same here..reverting back to previous version.

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

@kitling55 when do you see that message?

@aaron schachter seems two different issues, could you open a new bug describing the problem?

Priority:Normal» Critical
Status:Postponed (maintainer needs more info)» Active
new55.17 KB
new66.1 KB

After upgrade from 3.3 to 3.4
Undefined index: field_anno_scolastico_value in views_handler_filter->accept_exposed_input() (linea 1260 di /web/htdocs/www.xxxxxxxx.com/home/sites/all/modules/views/handlers/views_handler_fil...).
If I return to 3.3 everything OK.
I put the image filter with views 3.3 and 3.4 views
Thank you for your attention

You know what, I just filed a similar issue separately, but I think my problem might be the filters with the 7.x-3.4 upgrade, just like most of the previous comments. I have a lot of Views on my site that depend on filters. I'll work with this. For now, my pages preview just fine in the Views UI, but they disappear when you go to the pages. All was working fine with 3.3. I filed my issue here: http://drupal.org/node/1743424

Okay, I've done everything I know how to do. Some of the Views still work, but most don't. It doesn't matter whether they are blocks or pages. I have a few of both blocks and pages that are working, and most of both blocks and pages that aren't. I have learned my lesson to save a copy of the old version of a module before upgrading. My whole site is basically down now. Can anyone please post 7.x-3.3 somewhere so I can restore my site until we figure this out? I'm so sorry. Truly, I've learned my lesson to back up modules before an upgrade.

im in the same boat right now. Once you have the 3.3 version how do you downgrade without loosing all your views?

Hadn't thought of that. I don't think it will be a problem, will it? I don't even have 3.3 to try. To repeat the request, can someone please post 3.3 for those of us whose sites are now down with the 3.4 upgrade? We promise to back up our code base in the future. Thanks.

Please check your filters like this: http://drupal.org/node/1743064#comment-6375620

Works for me (need to resave almost 80 views, but now works...)

For the people wanting the 7.x.3.3: http://drupal.org/node/1451068

Thank you so much for the link, PedroMiguel and 15handsmedia. My site is back up now with 3.3. I'll wait to hear what support says on this upgrade before trying again.

I think the problem is here: http://drupal.org/node/1494884 with this patch: http://drupal.org/files/1494884_0.patch

As the "in_operator" was "gone".

-class views_handler_filter_field_list extends views_handler_filter_in_operator {
+class views_handler_filter_field_list extends views_handler_filter_many_to_one {
   function get_value_options() {
     $field = field_info_field($this->definition['field_name']);
     $this->value_options = list_allowed_values($field);

Title:Notice: Undefined index: in in views_handler_filter_in_operator 7.x-3.4 Upgrade is cancelling boolean operator settings
Component:Views Data» page displays

4 things are going on with the upgrade to 7.x-3.4 during the first few hours post-release:

  1. This related issue at http://drupal.org/node/1743064 seems to be solved with some manual fixes.
  2. And, #1 above seems to be unrelated to this particular issue (thus he was asked to file a separate issue).
  3. So, I think what we have here at this issue is something in the 7.x-3.4 upgrade that is cancelling the boolean operator settings, causing Views to disappear from some people's sites. PedroMiguel is working on a way to fix that in the code (#12).
  4. Several of us are experiencing the loss of Views with the 3.4 upgrade and our operators are remaining checked in the UI, however, so there is something else going on, too. I've filed a separate issue on that here: Upgrade to Views 7.x-3.4 makes some pages disappear and I've also sent a private message to dawehner who seems to be the most active maintainer for Views. I've given him an admin password to a test site with 7.x-3.4 installed so he can see the problems (or forward the pw on to someone else who can look at it). My feeling is that a lot of people are going to be commenting on this. I've already closed as duplicates and re-directed a couple of other issues people have filed just tonight.

Issue summary:View changes

Summarizing issue.

Can someone please attach an export of a view that is breaking? It might be better to do this when testing a fix.

Status:Active» Needs review
new926 bytes
PASSED: [[SimpleTest]]: [MySQL] 1,555 pass(es).
[ View ]

So the actual problem is that the value didn't got updated, so let's do that.

I would be really happy if people would actually test the patch

Hi dawehner, thanks for the patch but that didn't work for me.

What I did:

- Drush up views
- Appy patch
(- update.php)
(- Clear all caches)

All views continues with the mention problems

Status:Needs work» Needs review
new54.76 KB
new18.67 KB
new10.91 KB

This patch did not fix my problem. I manually applied the patch. dawehner, I am replying to your email here. You said,

It would be cool if you could test at least the in-operator issue, as this would probably fix the issue.

I do not program much, and I do not understand what it means, "test the in-operator issue." I did try to change operator values in the Views UI, but that did not work.

Also, you said at Upgrade to Views 7.x-3.4 makes some pages disappear:

People asked for a release all the time but at the same time if you change things you can never be sure everything is still working.

At the same time people don't test before doing an update, i fear there is no good solution for all of that.

In the future, I will test a module before upgrading my production site. Thanks for your help. I appreciate all your work on Views. I have attached the files you wanted.

Status:Needs review» Needs work

Status:Needs review» Needs work

Uh oh, next time I'll be sure to wait a while before upgrading to new version. :/

@ -Mania-
The right approach would be to test before update.

@dawenher could you link the issue that you think caused this problem?

@dawehner: The right approach is to check the forums first. ;) It's only my dev site though.

Title:Notice: Undefined index: in in views_handler_filter_in_operator 7.x-3.4 Upgrade is cancelling boolean operator settings
Component:Views Data» page displays
Status:Active» Needs work

Just a quick update about #13 statement, I'm not working on a fix. (due de lack of my knowledge about views code, and this will need some time before check and learning the code).

I think a fair warning about this issue on project page should be made (the need to resave views containing the missing operators) as this affect several site builders.

new18.57 KB

I tried but #15 1742942-filter_list-in-operator.patch doesn't work for me.
I still read:
•Notice: Undefined index: field_mese_value in views_handler_filter->accept_exposed_input() (linea 1260 di /web/htdocs/www.xxxxxxx.it/home/xxxxx_xxxxxx.inc)/sites/all/modules/views/handlers/views_handler_filter.inc).

and the school year and month there are not

When I opened the views that no longer works.

The site is in Chinese so I just describe the problem. Some more message when I clicked on update preview. "The operator is invalid on filter: 内容: 菜单类." The filter is a field. All the views that have problem rely on using a field as filter.

Status:Needs work» Needs review
new639 bytes
PASSED: [[SimpleTest]]: [MySQL] 1,555 pass(es).
[ View ]

We would really like to have a copy of a database/code which would allow us to reproduce the problem.
Someone gave us some admin rights, so we saw the problem live but playing with the code at the same time could also improve the situation.

This patch reverts the other patch, so maybe applying that will help you.

Issue summary:View changes

Corrected wording.

dawehner, I am happy to give you FTP access. I'll personally email you the access.

Okay, I just sent you the FTP access. I installed Views 7.x-3.4 fresh so you have a new start.

Status:Needs work» Needs review

dawehner, I just realized you wanted database access also. I cannot access my database directly, but you can get access through my hosts, [update: content deleted when it was no longer needed because it refers to a specific site].

Status:Needs review» Needs work

dawehner, I applied the patch in #27 manually, and it did not work.

So, I put everything on my BIZ site back to original 3.4 release. You can work with my test site using the info I sent you by email if you want.

This is an interesting comment from someone who said his problem was the same as this issue. He explains it like this:

On our homepage is a "Views" block which grabs Ubercart products (nodes) which have been marked as featured (simple tick box on the node edit page).

The problem was, we have over 1000 nodes, there was no limit set on the Featured Product block, so after the upgrade, as the "Is Featured Product" Filter got broken by the above bug, the query was then pulling in EVERY product on our site.

After checking through each "View" in the admin config, I found that Views was complaining about an invalid boolean operator for the featured products block, once I manually resaved it with the correct setting again (and also set a limit of 10 items incase we have the same problem again), everything was fine.

So basically, the above bug broke the filter and caused a MASSIVE query to be run, resulting in the SQL server timing out.

I just received a personal email from dawehner who is actively working to resolve this bug. He wrote:

I'm sorry for what happend.
I'm really wondering in general about a better/good release managment. We waited for a quite long time, asked on twitter multiple
times etc, but basically noone provided feedback. On the other hand we saw quite some people actually using the DEV version
so it seems to be fine to release a version, but yeah things are going on wrong.

I will work now hard on the stuff.

I think the better/good release is a great idea. Also, dawehner asked me to write a warning message about this bug to be posted on the Views 7.x-3.4 release page, which I have done and emailed to him for posting, recommending that people wait to upgrade until this bug has been fixed.

Issue summary:View changes

Updating information to match progress on the issue.

Status:Needs work» Needs review
new978 bytes
PASSED: [[SimpleTest]]: [MySQL] 1,555 pass(es).
[ View ]

Thanks to people i was able to reproduce the problem on a local system
and i figured out that #15 was somehow right but not 100 percent.

Here is a patch which fixes the issue for me.

Status:Needs review» Reviewed & tested by the community

I Test the patch on 7 production sites and all working ok.

Thanks a lot for the patch.

new6.48 KB
FAILED: [[SimpleTest]]: [MySQL] 1,556 pass(es), 1 fail(s), and 0 exception(s).
[ View ]

Okay here is a test which should fail without the patch.

Status:Reviewed & tested by the community» Needs work

The last submitted patch, 1742942-filter_list-test.patch, failed testing.

Status:Needs work» Needs review
new2.49 KB
new7.43 KB
FAILED: [[SimpleTest]]: [MySQL] 1,556 pass(es), 1 fail(s), and 0 exception(s).
[ View ]

Here's a combined patch of the test and fix.
I also cleaned up some code style.

Wait for green, then commit!


Status:Needs review» Needs work

The last submitted patch, views-1742942-36.patch, failed testing.

Okay, I double-checked that I'd applied the above patch from tim.plunkett manually, and it's still not working. Here's what I wrote earlier and it still applies:

dawehner, I just looked at my test site that you had access to, http://fashionbelle.biz, and it appeared that the patch had not been applied because the Views were still disappearing, so I applied it myself manually, and it did not fix the problem. I'm not a programmer, so you are welcome to check my work of applying the patch, but because the upper test failed, I thought you would like to know I'm still having problems, also.

couturier sorry for my question, but you are applying against 3.3 or 3.4? I'm asking because i made that mistake, on 3.4 was applied clean.

It failed applying against 3.4. Did I do that right? I'm not a programmer, just trying to help as much as I can.

You should try with https://drupal.org/node/1742942#comment-6383470 (32) patch.


Looking at your view export seems your problem is not related with this issue... but if someone could recheck...

Yes, I've wondered that myself, if my problems are related to this. My Views crashed instantly upon upgrade from 3.3 to 3.4, though, and this is the closest issue that seems to relate.

The comment #36 patch from tim.plunkett includes those changes from the comment #32 patch. I just checked. The problem still exists. Some Views pages and blocks are disappearing, but others are still there. I have checked to see if changing the operator settings in the UI helps after applying the patch. It does not. Again, having applied the patch manually myself, there is room for possible error in the way I applied the patch. dawehner has access to my test site if he still wants to work on it, and it's fine with me if he passes on the access to tim.plunkett if they want it. My site is definitely a case study in this problem since I have so many Views dependent on filters.

After review the #42 site appears we have a new problem, time based cache is not working on that site... if someone who have some installation who use that and could test, we can confirm and open a new issue.

new0 bytes

Like PedroMiguel said, it was the time-based cache that caused problems in the 7.x-3.3 to 3.4 upgrade. (Thanks so much for helping me find this!) I've attached a screenshot of the option under "Advanced" where the time-based cache needs to be set to "none." This allows all the Views to re-appear.

Just to make sure, I tested whether this would fix the problem both with and without the latest patch from tim.plunkett installed, and does. The boolean operator patch had nothing to do with my problem. I've opened a new issue here: Upgrade from 7.x-3.3 to 3.4 makes time-based cache break Views.

If anyone else has a site with a problem with boolean operators that can be replicated for tim.plunkett and dawehner as they work on this issue, please let them know, since we see now that my site had nothing to do with this.

Issue summary:View changes

Updated information regarding warning message on Views release page.

Issue summary:View changes

Updated the status, adding new information.

new31.79 KB

Attachment above didn't work. Here it is again. Most people should know how to set time-based cache to "none" under "Advanced."

Please don't post the caching issue here, because it is separated.

Regarding the operator issue, is this actually fixed by the previous patch?

dawehner, this is weird, but my boolean operators became unset for one View when I re-set my time-based cache after applying the patch at http://drupal.org/node/1748526

No valid values found on filter: Content: Blog Tags.

I manually re-set the operator and the View worked again. So, I don't know if they are related since the operator was working before I adjusted the cache. I tried to duplicate the error on other Views, but I could not. It only happened one time. Maybe it is nothing, but I thought I should report it.

Status:Needs review» Needs work

I have tried the patch # 32 1742942.patch in 25 sites and now exposed filters work well in all views.Thanks for the help

Committed the fix without the test. This patch needs backport to 8.x-3.x

I can confirm that all my troubles with exposed filter in Views 7.x-3.4 is gone in 7.x-3.5. Thanks for committing the fix (and making a quick new release).

Just adding a tag

Updating tags

Is #1781744: Draft and Needs review pages are broken also an effect of these bugs? The views debug message is shown since the upgrade from 3.3.

Status:Needs work» Closed (fixed)

Please correct if I am wrong, but this issue is obsolete since the release of 7.x-3.5, right?

Issue summary:View changes

Punctuation correction.