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.
I am using NodeReference Explorer on a production site, and have just noticed this bug.
Reproduce-able by the following steps:
- 1. from a Content 'Edit' page, pick a NodeReference field, choose 'Browse'
- 2. NodeReference Explorer pops up, displaying filter options followed by first page of results (nothing surprising so far)
- 3. Choose a filter. Let's go with 'Node: Type'
- 4. Click 'Apply'
- 5. the first page of results is now replaced by the filtered results, however
- listed rows are no longer selectable - you can click them, but they don't get highlighted
- each row, under the 'Node ID' column, now contains a radio button - which is selectable
- even if the radio button is selected and submitted, no results appear in the NodeReference field on the Content 'Edit' page
I'm sure this is probably a quick fix, and would love to see a quick solution!
Thanks for your help,
Adam
Comments
Comment #1
rcross CreditAttribution: rcross commentedditto
Comment #2
rcross CreditAttribution: rcross commentedThere seems to be a related issue where sometimes when filtering the listing will send the user off to a different page (outside the modal) which lists the results, but without any clear way of getting back to the content or selecting/submitting a choice.
Comment #3
sitron2 CreditAttribution: sitron2 commented+1
Comment #4
gnindl CreditAttribution: gnindl commentedPlease proceed on issue #842248: Any one have an redirect issues after a filter? as it concerns exactly the same problems
Comment #5
gnindl CreditAttribution: gnindl commentedEmbedded Views might not be unique. Therefore this issue is Views related and is blocked until this issue #655002: 2 separate ajax views on a page => results updated in both places. is solved.
Try out the patch supplied in http://drupal.org/node/655002#comment-3195720.
Comment #6
gnindl CreditAttribution: gnindl commentedA fix has been included in the current dev snapshot. The patch from http://drupal.org/node/655002#comment-3200430 has been included in the hook_views_pre_render() generating a unique view dom id.