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.Hi, I've been trying to find a solution for a frustrating views exposed filter conundrum and I wonder if anyone can help. Here is the rundown:
- Using Drupal 7.10, Views 3.0
- A content View that displays authors and their posts in a table format.
- There may be more than one author per post and this is displayed in the table in the same row (Multiple field settings > display all values in same row)
- Exposed filter operator for the author field is set to "is one of" a list of authors. These authors have a relationship with a node reference field in the post content type
Problem:
When filtering for an author, the results only display the posts for which he/she is the only author, or the first of multiple authors. If the author is listed as the second or third author of a post, the author is not displayed in the filter results. I think this is because even though the author column in the main view may contain multiple authors, these authors are technically in separate fields...but I am not 100% certain.
I have tried multiple exposed form settings and the Better Exposed Filters module. Looked at many forum posts hoping to find some clue. These were the closest, but still not quite my problem, I think: Apply One Exposed Filter to Multiple Fields Views Module Exposed Filter applied to multiple fields?.
Am I overlooking a simple obvious setting for either the exposed filter or the field that would give results that included the posts which list the author second or third?
Although I've added some php to views, I've never created a module and have very limited php skills.... however I am open to any solution or tips.
Thank you for any assistance,
Connie
Comments
Comment #1
Kars-T CreditAttribution: Kars-T commentedDear fellow Drupal enthusiasts,
this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not describe the problem comprehensibly.
But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.
Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.
Help can also be found for it on IRC and in the user groups.
In order to remove this issue, I have set this issue to "fixed"
If there is new information, please re-open the issue.