Closed (fixed)
Project:
Views (for Drupal 7)
Version:
7.x-3.x-dev
Component:
Miscellaneous
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
3 Jul 2011 at 05:29 UTC
Updated:
11 Jul 2015 at 02:47 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dawehnerWhat kind of filters do you have configured?
Some of them, for example node:type might have items selected which doesn't exist anymore.
Comment #2
tommychrisIssue also active in 7.x-3.x-dev branch.
Comment #3
Anonymous (not verified) commentedyes one of them are based on node type, any workaround?
Comment #4
dawehnerConfigure your node type and save it, this should fix it.
Comment #5
Anonymous (not verified) commentedsorry for my stupid question, do I need to save it at
http://domain.ext/admin/content/types/[type_name]/edit
or
http://domain.ext/admin/build/views/edit/[view_name]
...or recreate the node type field in the view?
thanks
Comment #6
dawehner2)
Comment #7
mariagwyn commentedThis error started cropping up when I upgraded to the most recent version of 7.x-3.x-dev.
I tried to re-save the node type as recommended above, but it did not solve the error. The view itself mostly worked, except that it was not properly grouping values (i.e., if one user had multiple tags, the user was listed repeatedly, according to the number of tags).
In one case, I recreated the view from scratch, and it seems to be working fine. Note that this views DOES have an exposed filter based on a taxonomy field.
I then began to recreate another view. All was fine until I set an exposed filter (worked fine) and then I unchecked the "show error message" field on that filter. Suddenly, I have repeated listing of "No valid values found", no preview, and, I cannot save the view. I rechecked "show error message" but the error persists.
I went back to the view that I was trying to recreate, and removed the exposed filter since that caused the error in the recreated version. The error cleared. I then tried to add the filter, and the error reappeared. I am happy to share the view if it helps.
Thanks,
Maria
Comment #8
giorgoskworkaround mentioned in above
"Configure your node type" and save it
does not work
EDIT:
cleared all the filters and the errors are gone
tried to recreate the fitlers and seems the problem is with "taxonomy term id" filter (exposed or not exposed)
Comment #9
giorgoskPLEASE
if anybody has a views 6.x-3.x dev older than july 2nd I would appreciate if you send me a message
(I erased it thinking that new dev would be working fine - usually it does)
Comment #10
giorgoskHere is a previously working view that I can't change anything to after updating to the latest dev
if I erase the 2 exposed term filter then I can modify the view but I can't add any term ID or term ID with depth filter
Comment #11
robertom commentedI have the same problem.
I think that this is "introduced" with this commit:
6c1cbd0ac4c6edae29b90563e8270cdeff5496aa
in my case $this->value_options is empty and the foreach unset all my value
if I uncomment the unset, the filter works well.
I don't know why my $this->value_options is empty
Comment #12
cutmedia commentedHave the same issue on 7.x-3.x-dev comment #4 from dereine doesnt work
Update. The views give the error when applying any taxonomy filter, as stated above. When filter is applied any View becomes unusable/editable.
Comment #13
giorgoskDoes it deserve a priority: major ?
since there is no workaround
its probably going to affect a lot of people going to try the latest dev
Comment #14
giorgosk@robertom
can you try to elaborate a little on your fix ?
I could not apply your workaround
Comment #15
mandreato commented+1
Comment #16
robertom commentedHi GiorgosK, I have this error with 7.x-3.x
For 6.x-3.x the commit that introduce this validation behavior is:
600c7ff1acdc7cb456d69ae888eea1a4c9fe4fe8
you could try to open:
/sites/all/modules/views/handlers/views_handler_filter_in_operator.inc
and comment line n° 382 (add a // before: unset($this->value[$value]); )
now will vanish the purpose of patch #1205570: The IN operator is not validated, but is a quick workaround (at least in my case)
P.S. for 7.x-3.x the row to comment is n° 367
Comment #17
giorgosk@robertom
I did just that and it does not work in my case (6.x)
but I thought I was not doing it right
Comment #18
spacereactor commented#16 doesn't work for me in drupal 7. change unset($this->value[$value]); to
Anyway I upload a old views, date at (2011-Jun-29) before the taxonomy filter bug is introduce. Replace the views should remove the problem til there is a fix.
Comment #19
aristeides commentedI posted a few hours ago this issue http://drupal.org/node/1209192 and have the same problem on 7.x-3.x-dev
I localized the terms and upgraded views so I guess localization is of no importance since you guys have that issue too.
Marking the other post as duplicate and appending my issue here:
Comment #20
acbramley commentedI'm having this issue, I've removed all of the taxonomy filters from a view and I'm getting errors on other random views (e.g Calendar). This is very frustrating as it's even stopping me from saving the views.
Comment #21
giorgoskShould we upgrade this to critical so the maintainers take a note
as it might affect lots of people downloading the dev version
Comment #22
aristeides commentedUpgraded as suggested by GiorgosK.
it IS critical since taxonomy is one of the most used things in views.
Comment #23
robertom commented@spacereactor and GiorgosK
I have searched 'No valid values found.' into views
seems to me that this error is only rised by validate function inside
./handlers/views_handler_filter_in_operator.inc
this is the function introduced for fix #1205570: The IN operator is not validated.
You could try to comment at all this new function, or comment the line that populate $errors array (return a not empty $errors cause the "stop").
Obviously this isn't a fix.
Comment #24
dawehnerI don't see why this is critical, it's just a message in the admin interface produced by views itself.
Can someone explain how to reproduce this problem?
Comment #25
giorgosk@dereine
on any working view
try to add "taxonomy term id" filter (exposed or not exposed)
Comment #26
mariagwyn commentedThis is at least major because
1. Many views with an exposed filter are no longer editable.
2. The view display seems to show repeats on the filter.
I say "many" because when I rebuilt a view from scratch, which includes an exposed filter on a term reference field (I am using 7.x), the view worked. However, on another view, an attempt to rebuild from scratch broke at adding the same type of term reference field. I am frankly not sure the difference. See #7 above for the process. I have included both the working and non-working views as attachements. The broken view does display, but it also shows multiple values, which it did not do before the upgrade.
Comment #27
mariagwyn commentedI took a closer look in my logs, and I have the following errors, which is different than simply "no valid values found":
PHP error:
Notice: Undefined index: vid in views_handler_filter_term_node_tid->extra_options_form() (line 47 of /local/drupal-7.2/sites/all/modules/views/modules/taxonomy/views_handler_filter_term_node_tid.inc).Form error, in ajax:
Illegal choice in field_tax_news_tid element.Comment #28
mikeker commentedI agree with Priority == Major mostly because I cannot save changes to a view (7.x-3.x) after adding a filter that triggers this issue. I haven't verified that in the 6.x branch.
A workaround I've found, at least for List:Integer filters, is to set a default value. But, I haven't done any testing outside of the very narrow constraints of my test case...
Comment #29
dawehnerI agree this is really really annoying.
This is a quick fix to get it working again, with a todo.
Comment #30
giorgosk@dereine
great works as expected
trivial fix so I mark reviewed and tested
Comment #31
mikeker commentedThanks, dereine.
But, is there a 7.x-3.x solution? And wouldn't this be better placed in
views_handler_filter_in_operatorto cover all integer filters?Comment #32
dawehnerApply the patch to 7.x-3.x works as well. Not really hard.
Placing it in views_handler_filter_in_operator would basically revert the patch which was created for this, which doesn't make sense for me
Comment #33
SeeWatson commentedApplied the patch. While it fixed the validation error from popping up as it was, now I can't add a new display field to the view. I got the following error (with the tilda replacing my site root for safety):
An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: ~/admin/structure/views/ajax/config-item/interns/page/field/field_user_fullname
StatusText: OK
ResponseText:
Fatal error: Call to a member function options_validate() on a non-object in ~/sites/all/modules/views/includes/admin.inc on line 4127
Comment #34
dawehnerDoes this happens if you remove and readd the feld?
Comment #35
mariagwyn commentedI applied the patch in #29 to 7.x-3.x-dev, error gone. No problems so far and I have been playing with views all afternoon to be sure.
Comment #36
james.bowling commentedThe patch didn't seem to fix it for me. 7.x-3.x-dev
Comment #37
dawehner@james.bowling
On which filter does this error appear for you?
Please if you test a patch and it fails report what you did.
Comment #38
SeeWatson commentedI tested this again from a different box when I got home. I'm not getting that ajax error anymore.
However, I was getting the following notices up top upon initially opening the view again:
Notice: Undefined index: allowed_values_function in list_allowed_values() (line 233 of ~/modules/field/modules/list/list.module).
Notice: Undefined index: value in list_field_formatter_view() (line 452 of ~/modules/field/modules/list/list.module).
Notice: Undefined index: value in list_field_formatter_view() (line 457 of ~/modules/field/modules/list/list.module).
Notice: Undefined index: value in list_field_formatter_view() (line 452 of ~/modules/field/modules/list/list.module).
Notice: Undefined index: value in list_field_formatter_view() (line 457 of ~/modules/field/modules/list/list.module).
I assume they're related, but I'm not sure. I removed all the display fields, added them back again, and now I'm not getting those notices either. So, for the moment, that patch seems like it'll work for me.
(Oh, I'm 7.x.3.x, btw)
Comment #40
craspouille commentedHi Dereine,
is the problem supposed to be fixed in the latest version (july6th)?
Because it still dos not work :-(
Comment #41
giorgoskSIDENOTE for applying patches (I was asked on email)
--------------------------------------------------------------------------
you have to learn to read and apply patches
you can read more here http://drupal.org/node/707484
but this one is really easy to apply by hand
http://drupal.org/files/issues/1207680-get_value_options-fix.patch
basically it says open
/views/modules/taxonomy/views_handler_filter_term_node_tid.inc
and insert lines that start with + signs
4 lines after 177 line
Comment #42
zabelc commentedI'm afraid the patch doesn't completely fix the issue. I applied the patch, and then cleared my cache several times, and I'm still getting the error repeated at least once on *most* of my views. I'm also getting "The operator is invalid" repeated on a few views.
FWIW, the only views that don't seem to have errors are the ones that have no filter criteria or context filters. I've tried removing these filters, but that doesn't seem to affect the errors.
I hate to say it, but this is at least a major priority as it's basically stopped my work pretty completely (even if testers can't see the errors on the views, I can't modify them in the admin screens). I would expect that others are in the same boat.
Comment #43
dawehner@craspouille
No the patch isn't applied yet.
@zabelc
Can you please please please describe which filter you have added? It's really important to know this.
Comment #44
robertom commented@zabelc and other people that have applied the patch without results
go to admin/structure/views/settings and check "Always show the master display", after that go to the master display of the "problematic" views and see if there is a unwanted "unknown" filter, if there is remove it.
Comment #45
zabelc commented@dereine, I'm afraid that I've got lots of filters on my views (and displays), so it's hard to narrow down which filter might be the cause. I've even tried removing all filters from all displays, but the errors remain. I can't save my changes because of the errors, so I'm not sure if the changes are having any effect (it's a bit of a Catch 22)
@robertom, I've been showing the master views and I've tried removing filters from it, but as I say, I'm not sure if that has any effect.
FWIW, when I get errors in one display, I seem to get the same errors (or at least the same number of errors) on every display (e.g. if there are two errors shown on the master display, there are two errors shown on every other display).
Below is my list of views & filters (I didn't break it down by display but I could).
Calendar View:
Filter Criteria:
- Content: Published (Yes)
- Content: Type (= Event)
Contextual Filters:
- Date: Date (node) (Content: Date (field_event_date))
User View:
Filter Criteria:
- User: Roles (= Member)
- User: Full Name (exposed)
- Field: Taxonomy Term Ref Field (exposed) | Settings
- User: Text Field (not empty)
- User: Name (exposed)
Contextual Filters:
- User: Roles
Recent Content View:
Filter Criteria:
- Content: Published (Yes)
- Field: Taxonomy Term Ref (exposed) | Settings
- Content: Type (exposed)
Contextual Filters:
- Content Type Machine Name
- Content: Has taxonomy term ID (with depth)
- Content: Has taxonomy term ID
Gear View:
(This view also has "The operator is invalud [sic]" messages.)
Filter Criteria:
- Content: Type (in Club Gear, ...)
- Content: Loaned to (not empty)
- Content: Requesting Member (empty)
Comment #46
vthirteen commentedapplied patch to 7.x-3.x-dev (EDIT: not yesterday's dev though, the previous one), error persists when adding a Taxonomy:field filter, set as a dropdown list with hierarchy. filter value is "empty" or "not empty", indifferently.
the same happens with "Content: Has taxonomy term" filter.
view cannot be saved unless the taxonomy filter is removed.
Comment #47
EndEd commentedsubscribe (The patch works for me here, last dev)
Comment #48
khanshakeeb commentedI have fixed this issue in views_handler_filter_in_operator.inc on line no. 378
I have change // if condition
if (is_array($this->value) ){
// Remove every element which is not known.
$watch_dog_count = 'Array is there = '. serialize($this->value);
watchdog('views3 dev',t($watch_dog_count));
foreach ($this->value as $value) {
if (!isset($this->value_options[$value])) {
//unset($this->value[$value]);
}
}
// Choose different kind of ouput for 0, a single and multiple values.
if (count($this->value) == 0) {
$errors[] = t('No valid values found.');
}
}
To:
this by removing is_array() function and it works fine for me
if ($this->value) {
// Remove every element which is not known.
$watch_dog_count = 'Array is there = '. serialize($this->value);
watchdog('views3 dev',t($watch_dog_count));
foreach ($this->value as $value) {
if (!isset($this->value_options[$value])) {
//unset($this->value[$value]);
}
}
// Choose different kind of ouput for 0, a single and multiple values.
if (count($this->value) == 0) {
$errors[] = t('No valid values found.');
}
}
Comment #49
craspouille commentedHi!
Can you tell me where is views_handler_filter_in_operator.inc ?
are you using 6.x-3.x-dev or 7.x-3.x-dev ?
thanks!
Comment #50
cyberwolf commentedSubscribing.
Comment #51
mariagwyn commentedI am pretty sure I did not accidentally update views dev version, so the patch should still hold. And, as it turns out, it has not fixed all my views. Attached is a view that when opened displays two lines "No valid values found." When I eliminate the exposed filter Content: Status (referring to a checkbox field) and Content: Track (referring to a tax_ref field), I can get rid of ONE error line. No matter how many filters, fields and relationships I eliminate, I cannot get rid of the second error line.
Hope this helps in drilling down on the problem.
Comment #52
dawehnerCommited this patch for d6 and d7, so at least quite some of the existing problems get fixed.
@all
Please describe which filter causes the view not to save.
Comment #53
mariagwyn commented@dereine:
1. Is this committed to the July 6 dev (only ask b/c today is july 7, not sure when you committed).
2. As far as I can tell, the exposed filter which most consistently causes the problem is on a TERM//TAX REFERENCE field.
However, I am not sure of this. In the view atttached to #51, I tried deleting two of the displays. The error went down to one line as opposed to two, but deleting the remaining exposed filter on the single page view left did not fix the problem. I am finding it very difficult to drill-down on the actual offending filter.
Comment #54
dawehnerIt will be part of the dev release of tomorrow.
Thanks for telling the filter.
Comment #55
anouHello,
I have views 7.x-3.x-dev installed. I've just upgrade to the last version. After that I still had the problem of multiple "No valid values" displaying in error type message and I wasn't able to save any of my changes...
For your information my view, beside "publish (or not)" and "content type" filters, all display pages (6) have the taxonomy term filter.
So I applied #29 dereine's patch and the error has gone and I finally could save my changes.
Thanks
Comment #56
NaX commentedI just ran into this same problem using the latest 6.x-3.x-dev with an exposed CCK node reference field.
The reason this seem to be happening is because I did not select a default value. When I select a default value the error goes away, but I want the default value to be
<Any>.I changed the
validate()function inviews_handler_filter_in_operator.incto check$this->value_optionsas well. I don't know if this is correct but it seems to work.So I wonder how do you setup a view with this kind of validation when you have no content to populate the filter, EG: you imported your field and views definitions. In my opinion the view should still work regardless if their are any nodes or terms to populate a filter. If their are no valid options the field should just render empty or disappear. Just my 2 cents.
Hope it helps.
Comment #57
Anonymous (not verified) commentedI did the hack #56 over 6.x-3.x-dev of today and the issue has gone away
Comment #58
dawehnerOkay here is a patch which is basically based on the idea of #56
It doesn't run validation if there are not options availible at all.
It's for the dev version so please test it.
Comment #59
Anonymous (not verified) commentedpatch applies successfully and solve the issue. Tested against 6.x-3.x-dev
Comment #60
spacereactor commentedusing 7.x-3.x-dev 2011-Jul-09 working without the patch.
These are the step i need to take.
1.) First make should the master and page have the same setting.
At FILTER CRITERIA
Change For => This page (Orride) to For => All Displays
2.) Change the setting for expose taxonomy filter under FILTER CRITERIA
Click on the expose taxonomy filter At the option area choose "Select all" in the listing and enable "Limit list to selected items"
3.) Apply the Save
If it still doesn't fix your problem, Test out patch #58.
Comment #61
mariagwyn commentedHm. I applied patch in #58 to 7.x-3.x (most recent), it failed to apply. Thinking that perhaps it was meant for 6.x, I re-uploaded 7.x, and applied the patch in #29. That failed as well.
Perhaps I misunderstood what the most recent patch is for? Or the most recent dev doesn't like either patch?
I will grab the dev of tomorrow (well, later today) and see how it does.
Comment #62
dawehnerThe patches are ALWAYS against the git version of views.
The git version might be the same as the DEV version, but this is not true for most of the time, because the dev version is just built every few hours.
@spacereactor
Can you please try out the patch?
Comment #63
spacereactor commented#62 i try to run the patch but i think /modules/user.views.inc already have
So i manually patch /handlers/views_handler_filter_in_operator.inc & /modules/taxonomy/views_handler_filter_term_node_tid.inc
and after clean my cache. I getting alot of error now mostly No valid values found. & The value array( something => 'something', ) is not an array for in
Example of error is
No valid values found.
The value array( 'support_ticket' => 'support_ticket', ) is not an array for in
The value array( 'support_ticket' => 'support_ticket', ) is not an array for in
No valid values found.
No valid values found.
The value array( 'support_ticket' => 'support_ticket', ) is not an array for in
No valid values found.
No valid values found.
The value array( 'support_ticket' => 'support_ticket', ) is not an array for in
The value array( 1 => '1', ) is not an array for in
P.S i using manually patch on 7.x-3.x-dev 2011-Jul-09
Comment #64
dawehnerOh you are true, here is a patch without this change(was another issue)
Comment #65
mariagwyn commented@dereine:
1. Pulled the git version 7.x-3.x (as of 5 minutes ago)
2. applied patch in #64, clean.
3. Got these errors on the 'member-schedule' view which I attached above:
Comment #66
jarush commented@mariagwyn
Same as mine...
Comment #67
ShadowMonster commentedsubscribe
Comment #68
demonrage commentedthe patches not working for me, instead it givces another error:
The value array( 'ipaper' => 'ipaper', ) is not an array for in
Comment #69
designar commentedI think we need a solution for the filter_in_operator, taxonomy problems seems to be fixed.
Comment #70
cartagena commentedThanks for all the work on this...I'm having the same issue.
Comment #71
dawehner@demonrage
Which one?
Can't you all update to the latest dev, test, apply the patch and test?
Comment #72
mariagwyn commentedDereine, I know you are working hard on this, so please don't consider this pestering:
I am getting some version of "The value array( ... ) is not an array for in" in ALL of my views, even in the most simple of views (a few fields based on a type). The views themselves work but I am unable to save any views at all. I have temporarily gone back to the dev without patch so I can modify a few views.
Comment #73
demonrage commentedthis is really annoying i can't resume my work, we need a patch or a fix for this big error!!!
Comment #74
robertom commentedHi dereine, I don't have tested the patch, but it seems a bit strange to me...
in this snippet:
really you intend
!isset($this->value_options)?This probably solve my problem on #11, because my
$this->value_optionsis an "isset" empty array, but I think this isn't what you wantComment #75
james.bowling commentedUpdated to latest 7.x dev as of a few minutes ago, applied the patch and I am receiving the same type of return in #65 and #68.
Comment #76
bojanz commentedRan into this myself.
Downloaded the latest -dev, (VBO default content) view says "No valid values found", Save doesn't work.
dereine's patch fixed it for me.
Comment #77
cartagena commentedI guess I should have been more specific. I did update, applied test and am getting the same message as #65. Thanks.
Comment #78
damien tournoud commentedActually, I think that the problem most people are bumping into is that optional exposed filters fail validation if no default value is provided. This is just wrong.
Here is a patch adding this case.
Comment #79
damien tournoud commentedFunny, I mixed up Git commands.
Comment #80
radiomurf commentedI was previously able to reproduce the original errors using the default calendar module view. I was unable to save edits made to two of the displays provided.
After patching the July 8th 7.x dev (using dereine's patch in #64), the original "No values found." errors are gone, and one of the displays has corrected. The other display now generates "The value array( 'event' => 'event', ) is not an array for in" when applying a Content: Type filter (filtering for content type 'event'). This error also prevents the view from being saved (as with the previous error).
As an aside I experienced these errors (both original and new) WITHOUT having any taxonomy filters in the effected view (or it's various displays).
Comment #81
dawehnerCommited to 6.x-3.x and 7.x-3.x
Comment #82
demonrage commentedi applied the patch in #79, nothing happened, same error (No valid values found.)
Comment #83
cartagena commentedIs this correct for line 25: class views_handler_filter_term_node_tid extends views_handler_filter_many_to_on
or should it be many_to_one? Maybe it doesn't matter, I'm not a programmer but I do notice typos. (I'm referring to 1207680.patch)
There is also one in line 6 --The operator is invalud
thanks
Comment #84
zabelc commentedI just applied deriene's #64 patch *may* remove the "No valid values" error (though I've seen a couple of them crop up). BUT, like others I'm now seeing the errors below (with notes about the state views' filters)
Are we tracking this new error as a separate bug?
Comment #85
dawehner@zabelc
Please update to the latest dev and see whether it's fixed there for you?
@ cartagena
The patch file just truncates the output.
Comment #86
demonrage commentedwhy this issue marked as fixed, i didn't see any patch that really fix this issue ??
Comment #87
mariagwyn commentedI uploaded the most recent git version (dev version is a few days old), seems that problem is solved. Will get back if it is not.
Comment #88
demonrage commentedi downloaded the two files in the last commit for views 3.x dev, uploaded them and still nothing changes, same error same manner
:(
Comment #89
acbramley commentedAre people clearing their caches before re-testing?
Comment #90
demonrage commentedi have cleared both db cache (cache_views) and browser cache.
Comment #91
clashar commentedI tested with today 13 july dev. release, seems it was fixed.
Comment #92
kthullPulled latest 7.x.-3.x branch from git and it's working for me too. Many thanks!
Comment #93
zabelc commentedI'm happy to report that everything appears to be working well with the 7/13 build of 7.x-3.x-dev!
Many thanks dereine et. al for ironing out such a difficult little bug.
Comment #94
cartagena commentedIt's all working for me, too. Thank you all very much!
Comment #95
damien tournoud commented@demonrage: could you please upload the export of a view that causes you trouble? Most likely one of your filter is actually invalid.
Comment #96
jarush commentedThank you so much.
It works fine now when I updated it to latest 7.x.-3.x(7.13)
Thanks!
Comment #97
jarush commentedoh no...
In my calendar view. the "no valid values found" error occur..
I'm using the 2-dev of calendar..
Comment #98
cartagena commentedI also have calendar module enabled and I updated yesterday to the latest dev version of both calendar and views. I just checked and I didn't get the "No valid values found error" but I got a calendar invalid style plugin error that I'll post where it belongs. So I went back to the previous calendar version I had installed (jul 2 dev version) and it is now fine, I didn't get any errors. I made a change to the view and all saved fine.
Comment #99
james.bowling commentedI am still getting the error. This is ridiculous, someone must have it out for me! :) I have updated to the latest dev and I have cleared and cleared caches...same thing over and over again.
Comment #100
james.bowling commentedSee attached.
Comment #101
james.bowling commentedOk, the above posted errors in #100 were resolved. The wrong branch of Calendar suddenly found its way in. Although, I am still having the issues with the View module as stated above.
Comment #102
james.bowling commentedSo it seems that it has something to do with my calendar view. The other views seem to be fine. The odd thing is I never changed anything only upgraded Views, Calendar, and Date modules. Can someone point me in the right direction to get this resolved please?
Comment #103
james.bowling commentedOk, I am not 100% sure what I did but the error has gone away and I am able to edit the view now. Now I get a new error from time to time regarding field_ui but will take that up elsewhere. Thanks guys!
Comment #104
majdi commentedThis error happen when one of your display has filter with no value
Comment #105
Anonymous (not verified) commentedthe only chance to save a views is to delete those filter, not a good workaround at all.
Comment #106
bojanz commentedA fix for this was committed to 7.x-3.x. If there's still a problem when testing with Views 7.x-3.x-dev, open a new issue with an exported view attached.
Just dropping by to say "but it fails for me" without providing the version tested or the exported view is fine if you're bored, but nobody can help you that way.
Comment #107
Anonymous (not verified) commentedI'm referring to 6.x-3.x-dev, how can I export the views if I can't save it because the error?
If I use Views 6.x-3.x-dev (2011-Jul-09) I got "No valid values found"
If I use Views 6.x-3.x-dev (2011-Jul-13) I got "Call to a member function override_option() on a non-object" as reported at http://drupal.org/node/1217718
Thanks for your work
Comment #108
bojanz commentedThen debug the new error in the issue you opened. You're not even getting the old error.
Comment #109
jarush commentedThe "No valid values found" still there(just in the calendar view)...
I'm using the latest dev views and the latest dev calendar(7.x-2.x-dev).
I cant save / clone the calendar view..
Any suggestions?
Comment #110
dawehnerOpen a new issue, and try to report it as usefull as possible.
Comment #111
tommychris(Try to) Use calendar 7.x-3.x-dev.
Comment #112
tim.plunkettSee #1227628: No valid values found (Calendar module).
Comment #113
acbramley commentedI'm still getting these errors! Running the latest dev version. My view has 3 block displays, all pulling through a different field with a contextual filter of content: nid.
The filter is a simple Field: Not empty, and Content: Published.
Comment #114
acbramley commentedProbably worth noting that even after removing the filters I can't save the view, although the errors go from:
to
I need to be using the latest dev version for another fix but this is a show stopper for me.
Comment #115
dawehnerThis issue is so full already, please create a new issue WITH informations.
Comment #116
waltf commentedProblem still occurs with 7.x-3.x-dev, using 7.x-3.0-rc1 made the error go away.
Comment #117
dawehner@waltf
Please create a sane new issue, with good informations.
Comment #118
vinoth.3v commentedI got the error "No valid values found" in my "custom" views if any of the filter has no value selected.
Comment #119
masterperoo commentedI have spent over 40 minutes trying different options/workarounds
UI wouldn't let me to even delete/save a view.
it turned out that Master display had a broken filter handler. (why or how - I don't know...- used to be valid)
my advice: check filters in all displays
Comment #120
acbramley commented@masterperoo that also happened to me!
Comment #121
dawehnerWow, that's really helpful...
If you still have problems, please create a new issue with a useful bug report, without it noone can help you,
and that's not what you want :)
In general therefore please read http://drupal.org/node/571990 once and try to follow the steps explained there.
That's one big thing you can do from your site to fix the bug.
Comment #122
acbramley commented@dereine I was simply commenting how the master display was what broke mine and agreeing that people should check filters in all displays....
Comment #123
dawehner@ZOmbienaute
My answer was just a general answer, because there are still quite some people which comment here.
Comment #126
estnyboer commentedI see that this is closed but I have another fix. I disabled "views bulk operations" and it solved the problem.