Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
This issue is because the view condition doesn't respect the alias of the table. Attaching patch in the follow up comment.
Comment | File | Size | Author |
---|---|---|---|
#6 | feeds-views-alias.png | 71.68 KB | alan-ps |
#4 | feeds-views_alias-1829212-4.patch | 431 bytes | alan-ps |
Comments
Comment #1
agupta CreditAttribution: agupta commentedComment #2
acThis fixes the issue - can this be committed?
Comment #4
alan-ps CreditAttribution: alan-ps commentedI encountered with same problem. We can also remove operator element (by default =). Correct patch was attached.
Comment #5
MegaChriz CreditAttribution: MegaChriz commentedI'd like to test the patch. When does this problem occur?
Comment #6
alan-ps CreditAttribution: alan-ps commentedThis is occur when you are using relationship for the Feeds item. I've attached an image for check.
Comment #7
MegaChriz CreditAttribution: MegaChriz commented@alan-io1 Thanks for posting the image! That was very helpful.
I tested the patch. The issue seems to only arise when the feeds_item table is joined twice, for example when you want to show guids or import dates of both nodes and the attached taxonomy terms. Or, when using Commerce, guids/import dates from both the product displays as well as the products.
However, I didn't get the error message from the original poster (maybe due to changes in the Views module?).
I looked up in the Views documentation what that "extra" actually means (so I can verify if the patch in #4 fixes the issue in the right way). This from the Views advanced help:
I also tested if "extra" could be omitted completely, but that resulted into duplicate rows in my case, so the patch does the right thing.
RTBC.
Comment #9
twistor CreditAttribution: twistor commented