I've enabled Administration Views to get an improved way of finding content, but am seeing many duplicate rows for each node, with identical content in each.

A quick check tells me that there's an extra duplicate for each taxonomy term that a node refers to (I have product nodes that have "taxonomy reference" fields.)
So for a product with one taxonomy checked, it shows up twice.
For a product with 11 taxonomy terms checked, it shows up 12 times.

Something wrong with the SQL that's generating the view...

Comments

zambrey’s picture

Status: Active » Needs review
StatusFileSize
new859 bytes

Here's the patch. For quick fix you can go to view edit page and check Distinct under Query settings.

EvanDonovan’s picture

I would agree that this is the resolution, though I did not test the patch, only configured in the interface.

kristen pol’s picture

I ran into this problem independently and set the distinct checkbox and it worked for me. I didn't try the patch though.

Kristen

sun’s picture

Title: Duplicate nodes listed in admin/content with Administration Views enabled (taxonomy-related) » Duplicate nodes listed on admin/content (taxonomy-related)
Project: Administration menu » Administration Views
Version: 7.x-3.x-dev » 7.x-1.x-dev
Status: Needs review » Needs work

Needs to be re-rolled against admin_views.

dawehner’s picture

Status: Needs work » Needs review
StatusFileSize
new811 bytes

Here is a rerole for 7.x-1.x

This indeed fixes the problem of the "one to many"-join

sun’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: +Needs backport to D6

Thanks!

IIRC, a similar option existed in D6

dawehner’s picture

Status: Reviewed & tested by the community » Patch (to be ported)

Thanks for the review.

Committed to 7.x-1.x

To be able to backport it to d6 a 6.x branch is required. I will do this this evening.

sun’s picture

Version: 7.x-1.x-dev » 6.x-1.x-dev

What's wrong this existing branch though? ;)

fizk’s picture

Status: Patch (to be ported) » Needs review
StatusFileSize
new469 bytes

Re-rolled for D6. Will commit to D6 branch if it looks good.

sun’s picture

Is that patch based on a re-export or is that manually edited in? We should always base patches on re-exports, so an earlier change from a different issue does not pop up in a later patch that re-exports a view.

If it's based on a re-export, then it's good to go.

fizk’s picture

Status: Needs review » Fixed

Automatically closed -- issue fixed for 2 weeks with no activity.