Many instances of the same node, if files attached

Have you tried the distinct filter? Are you showing fields or filters from the files table?

Also, with what attachment module did this happen exactly? (upload, upload_image, image_attach, imagefield,...)

I encountered the same problem listing CCK nodes with multiple images attached to them with imagefield.module (filed a related issue on that mod's project page here on #3)

I am having the same problem, whether I am using list view or table view.

At present, the 'file name' field isn't able to collapse ALL the files on a node into a single entry. Because of that, adding the 'file: name' field will cause an entry for EACH file. If it's more important to have one line item ofr each node, add the 'distinct' filter.

I am not even using the file name field. I am using the "node:Author Name" field with "node:distinct" as a filter and yet I am still getting it displaying multiples. What it displays is this:

admin
admin
admin
admin
xamox
admin

I am logged in as admin, and xamox is a standard user on the install. Not quite sure why this is happening. Doesn't matter for what node type I add either still displaying multiples.

I'm encountering this same issue but with multiple node references.

I've created a view that has shows a list of nodes, each of these nodes has *multiple* nodereferences. For each node reference the item shows up in the view, with each item showing only *1* reference. It'll show each item, with each nodereference.

So if I have a node with node references A, B, C and I want to show a view of all nodes, in my view, it's going to list my node with A, same node with B, and same node with C.

It does not seem to just show the node with A, B, and C

Sounds like the same problem as files.

Also, as mentioned, if I turn off my nodereference field as a displayed field, only one node shows up, as it should.

Sounds like the query logic that builds the list of nodes with references is wrong... it shows each node with each reference (or file), instead of, in these cases, looping through the node and all of it's references and aggregating them together.

Yeah mine fuctions the same way(multiples of nodes), only when I use node references such as "Node:Title", "Node:Type", etc. But if I used something else it displays how it should

Yup. This is an issue with SQL more than it is with Views.

Let's say I have two tables.

NODE
nid title
1 'Hello there, here are some files for you'

FILES
nid file
1 'foo.zip'
1 'bar.zip'

Because Views wants to get every node in a single record, it uses your basic JOIN, which WILL result in:

1 'Hello...' 'foo.zip'
1 'Hello...' 'bar.zip'

With the current setup, that's what you can get. Possibly I can add an 'all files' field like the taxonomy: all terms. Not sure. That creates an extra query per record.

Hmmm, in terms of performance, this would only affect people showing listing of files. Seems to me that an extra query would be worth the hit, consolidating the view so it makes more sense.

Want to write a patch? =)

*runs*

Not familar enough with Views to do that--yet. I wouldn't hold your breath waiting on me though :-p

Sorry, my above statement was wrong. I didn't really understand how to use views when I first started using it and this is no longer a problem for me.

m3avrck: Here's a start

'all_files' => array(
'name' => t('File: All Attached Files'),
'notafield' => true,
'handler' => 'views_handler_file_all_files',
'sortable' => false,
'help' => t('Display all attached files as one field),
),

Then the above handler runs a query to determine the files that are attached. See, easy!

This feature will appear in Views 1.1

I have a standard list view with half a dozen filters. One is Taxonomy: Vocabulary Name. When I choose operator "Is One Of" and select multiple vocabularies, my list view displays multiple nodes - as many multiples as the node has vocabulary terms. Example: if three vocabularies are chosen in the filter, a node with terms in all three vocabularies will display three times while a node with only two terms selected will show up only twice. (Fortunately, for now I am able to set up my vocabularies so that I can choose just one for my filter and get the results I'm after.)

I have no coding experience, so will not be able to help troubleshoot and fix. But thought you should hear about it.

Here's the export:

$view = new stdClass();   $view->name = 'mapview';   $view->description = 'View maps every which way';   $view->access = array ( );   $view->view_args_php = '';   $view->page = TRUE;   $view->page_title = 'Browse Multiple Maps';   $view->page_header = '';   $view->page_header_format = '3';   $view->page_footer = '';   $view->page_footer_format = '3';   $view->page_empty = '';   $view->page_empty_format = '3';   $view->page_type = 'teaser';   $view->url = 'browsemaps';   $view->use_pager = TRUE;   $view->nodes_per_page = '20';   $view->sort = array (     array (       'tablename' => 'term_data',       'field' => 'weight',       'sortorder' => 'ASC',       'options' => '',     ),     array (       'tablename' => 'book',       'field' => 'weight',       'sortorder' => 'ASC',       'options' => '',     ),   );   $view->argument = array (   );   $view->field = array (     array (       'tablename' => 'node',       'field' => 'title',       'label' => '',       'handler' => 'views_handler_field_nodelink',       'defaultsort' => 'ASC',       'options' => 'link',     ),     array (       'tablename' => 'node',       'field' => 'body',       'label' => '',       'handler' => 'views_handler_field_teaser',     ),   );   $view->filter = array (     array (       'tablename' => 'node',       'field' => 'status',       'operator' => '=',       'options' => '',       'value' => '1',     ),     array (       'tablename' => 'term_data',       'field' => 'vid',       'operator' => 'OR',       'options' => '',       'value' => array (   0 => '5',   1 => '13',   2 => '8', ),     ),     array (       'tablename' => 'node',       'field' => 'distinct',       'operator' => '=',       'options' => '',       'value' => array ( ),     ),     array (       'tablename' => 'term_node_11',       'field' => 'tid',       'operator' => 'OR',       'options' => '',       'value' => array ( ),     ),     array (       'tablename' => 'term_node_5',       'field' => 'tid',       'operator' => 'OR',       'options' => '',       'value' => array ( ),     ),     array (       'tablename' => 'term_node_13',       'field' => 'tid',       'operator' => 'OR',       'options' => '',       'value' => array ( ),     ),     array (       'tablename' => 'term_node_8',       'field' => 'tid',       'operator' => 'OR',       'options' => '',       'value' => array (   0 => '79', ),     ),   );   $view->exposed_filter = array (     array (       'tablename' => 'term_node_11',       'field' => 'tid',       'label' => 'Whose Maps?',       'optional' => '1',       'is_default' => '0',       'operator' => '1',       'single' => '0',     ),     array (       'tablename' => 'term_node_5',       'field' => 'tid',       'label' => 'What Level?',       'optional' => '1',       'is_default' => '0',       'operator' => '1',       'single' => '0',     ),     array (       'tablename' => 'term_node_13',       'field' => 'tid',       'label' => 'Which Parts?',       'optional' => '1',       'is_default' => '0',       'operator' => '1',       'single' => '0',     ),     array (       'tablename' => 'term_node_8',       'field' => 'tid',       'label' => 'What Stage?',       'optional' => '1',       'is_default' => '0',       'operator' => '1',       'single' => '0',     ),   );   $view->requires = array(term_data, book, node, term_node_11, term_node_5, term_node_13, term_node_8);   $views[$view->name] = $view;

By the way, I absolutely love the module - am using it for the first time.

One more note: I did try the Node: Distinct filter to no avail.

Please don't take over semi-related issues. This one was about files, yours is about taxonomy. The behavior is similar but this is a different issue.

My apologies. This is my first attempt submitting bug reports etc, so would like to try to contribute. Thanks for your input. Should I submit a new issue?

Yes, please do so. The issue is valid, I think, though may be somewhat difficult to fix properly.