I'm creating a View that provides an argument summary based on a CCK field. I do not want the "" entry to appear in the summary for nodes that have no value for the field, so I checked the "Do not display items with no value in summary" in the argument. However, the "" item still appears. It is like this option is being totally disregarded.
I have tried clearing the Views cache. Also, I have duplicated the View, but created a summary based on taxonomy term rather than a CCK field, and the same thing happens (though it displays "Uncategorized" instead of "", of course). I have also disabled all other modules that extend Views. So I'm pretty sure the problem is not with CCK or any other module incompatibility, but rather with Views itself.
I'm including the preview query and the exported View in a comment below.
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | views_no-value-in-summary.txt | 15.06 KB | FeG |
Comments
Comment #1
theunraveler commentedComment #2
theunraveler commentedI'm having trouble getting the exported View to appear correctly, so here's a link to it in a pastebin.
http://drupal.pastebin.com/f260f42e5
Comment #3
merlinofchaos commentedAS per the submission guidelines, this should be filed against CCK (or the module that provides the CCK field if it's not a core CCK field).
Comment #4
theunraveler commentedI did read the submission guidelines. This, however, seems like it is not a CCK issue, since the same thing is happening with a view based on taxonomy term. The part of the view that is based on a CCK field is at line 1058 of the pastebin, and the one based on taxonomy term is at line 817. If you still think that it's a CCK issue, I'll gladly move the issue to their queue.
Comment #5
theunraveler commentedHere's the preview query for the taxonomy-based argument:
and here is the one for the CCK-based argument:
Hope that helps.
Comment #6
adpo commentedSubscribing the same problem. Do not display items with no value in summary is turned off.
I want change existing view from:
Argument 1 (3)
Argument 2 (5)
to
Argument 1 (3)
Argument 2 (5)
Argument 3 (0)
Comment #7
Letharion commentedThis bug report is made against a very old version of Views.
If this is still a problem, please test against the latest.
If the problem persists, then please re-open the bug, and we will take a look at it.
Comment #9
FeG commentedI currently have the same problem in version 7.x-3.0-rc1 with the summary of taxonomy terms in a view: Allthough I selected "Do not display items with no value in summary", the item "Uncategorized" shows up.
This must have been introduced in this version, since in an earlier 7.x version (don't know exactly which one), the view worked fine.
Not tested in 7.x-3.x-dev.
Comment #10
dawehnerCan you please provide a view export which allows to reproduce the problem? This really really helps to fix the issue.
Comment #11
kars-t commentedClosing this due to long inactivity. Feel free to reopen the issue and provide more information.
Comment #13
FeG commentedAs the problem still remains in version 7.x-3.1, I attached the exported view where it occurs. The affected display is "Page (Tags)" where the name of the taxonomy terms shall be displayed as summarized links. On the page using this view, all tag names occur but also the link "Uncategorized", although "Do not display items with no value in summary" is checked in the settings of the according contextual filter.
Comment #14
kars-t commentedDon't forget to reopen the issue ;)
Comment #15
clevername commentedSeems this option has been removed with the most recent version of Views. My solution was to simply create a filter to weed out any content that had an empty CCK value for the contextual filter. May not work for taxonomy terms and tags though.
Comment #16
FeG commentedI finally "solved" the problem by using the contextual filter "Content: Has taxonomy term ID" instead of the combination of contextfilter "Content: Tag" and relationship "Taxonomy terms on node". With the "Has tax. term ID", the setting "Do not display items with no value in summary" (which still exists in the version Views version 7.x-3.3 I use) seems to work properly.
So maybe this was a weird problem due to the combination I used. I'm not sure whether this is worthy to be examined further.
Nevertheless, thanks for your responses.
Comment #17
kars-t commentedThe last comment from FeG seems like we can close this :)