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.The attachment view does not respect the "inherit exposed filter" setting. It inherits and displays them regardless.
In this test, the node ID is passed as an argument to the attachment display via the title as a link using the [nid] token so that a selected item in the page display filtered list will be shown as the full node in the attachment display.
In addition, after selecting one item in the page display list, the full node is displayed in the attachment display as expected, but the filtered page display is reset to the state without any filters applied. The desired result is that it keeps the same filtered result, so the user can select another item to be displayed as a full node in the attachment display without having to apply the filters again.
For this simple test I selected the node ID as the exposed filter just to be generic, but any filter will give the same result.
The query run is:
SELECT node.nid AS nid,
node.title AS node_title
FROM node node
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 535206-attachments-repeat-exposed-filters.patch | 2.93 KB | merlinofchaos |
| Inherit Test.txt | 5.59 KB | druplicate | |
Comments
Comment #1
druplicate CreditAttribution: druplicate commentedI can understand why the filters get reset in the page view because I think the view gets automatically rerun when the argument is passed to the attachment display and Views doesn't remember the exposed filter settings. Would using AJAX solve this?
But I can't understand why the exposed filters show up in the page and the attachment display. I'm hoping the fix for this takes care of both issues.
If it's not fixable directly, would a small Views plug-in do the trick? If so, what would that entail?
Comment #2
joachim CreditAttribution: joachim commentedConfirming.
With:
inherit: no
display: no
I still get filters twice.
First problem is that views_plugin_display_attachment displays_exposed() is never called.
The only thing that calls displays_exposed() is view.inc, and that calls in on the current display handler, which is the page.
Beyond that I'm rather baffled as render_exposed_form() is only called once, and the form it gets is correct.
The view's build() is only called once, calls render_exposed_form(), and if I comment out that line (578 in view.inc), then both copies of the filter form go.
Comment #3
bfr CreditAttribution: bfr commentedPut the same exposed filters to both attachment and it's parent display and set inherit to "yes" and it wont be shown twice anymore.
However, the attachment get's still filtered, so this solves only the the visual part of the problem.
Comment #4
jcarnett CreditAttribution: jcarnett commentedI ran into this same issue. A workaround is to put the exposed forms in blocks and only use one of them (or set the extra form to be in a block and just ignore it).
Comment #5
merlinofchaos CreditAttribution: merlinofchaos commentedAhh, this is a silly bug. The exposed form wasn't regenerated, it was just being rendered twice because the clone process did not actually clear the filters.
Fix committed to -dev. Patch attached.