I am having an issue with this module. It is exactly what I am looking for to search and reference.

The problem that I am having is that the exposed filter doesn't have any effect on the section below. I have gone to a base install to test for conflicts and it still persists.

I have tested a bunch of different options, but I can't seem to get it to work. It isn't a fancy sort or anything, a simple title and taxonomy drop down.

This may be related as well, but if I were to click on a sort within the table view it opens the view in a new window.

Ay help would be greatly appreciated.

Drupal 6.19
Node Relationships 6.x-1.6
jquery update 6.x-2.0-alpha1
jquery ui 6.x-1.3
- jquery ui 1.7.3
modalframe 6.x-1.7

Comments

seb7’s picture

neither did i manage. (you can delete this comment, i thought i found a solution but no)

markus_petrux’s picture

Category: bug » support
Status: Active » Closed (duplicate)

Please, see #634620: Search and Reference views filter not working

To re-open that issue, it would be necessary to provide more information so that it can be reproduced, analyzed and fixed. The last user though, points out that the cause of his troubles was an overridden views template.

rohnjeynolds’s picture

Category: support » bug
Status: Closed (duplicate) » Active

I'm experiencing the issue of a new window opening when trying to sort a table view on noderef search in the modal window. Also, exposed filters on the top of the view disappear when sorting the table. Possibly significantly, I'm using Views 3.

I don't think this is a dupe with #634620. Also, I'm suggesting that this is a bug report and not a support request, because there is reproduceable, undesired behavior.

  • Node Relationships 6.x-1.6
  • Modal Frame API 6.x-1.7
  • Views 6.x-3.0-alpha3

Steps to reproduce:

  1. Enable a content type to use Node Relationships search and set view to Table Style. (In my case, I've cloned the default noderef view, but I can reproduce the issue with the default view, as well.)
  2. Create content and use the search button to find a node to reference.
  3. In modal frame, click the Title column header ONCE to sort on title desc. Notice the exposed filters on top of the table disappear.
  4. Click the Title column header AGAIN to sort on title asc. The table view now opens in a new window. Notice the exposed filters on top of the table reappear.

I've tracked a piece of this to Modalframe API, which has this swatch of code in its child.js file that adds "target=_new" to any link it perceives as external:

/**
 * Add target="_new" to all external URLs.
 */
Drupal.modalFrameChild.behaviors.parseLinks = function(context) {
  $('a:not(.modalframe-processed)', context).addClass('modalframe-processed').each(function() {
    // Do not process links that have the class "modalframe-exclude".
    if ($(this).hasClass('modalframe-exclude')) {
      return;
    }
    // Obtain the href attribute of the link.
    var href = $(this).attr('href');
    // Do not process links with an empty href, or that only have the fragment.
    if (!href || href.length <= 0 || href.charAt(0) == '#') {
      return;
    }
    $(this).attr('target', '_new');
  });
};

I've followed the instruction of trying to add 'modalframe-exclude' to the list of classes on each column header's link tag -- both via PHP (theming) and jQuery -- but I can't make the class stick to the link after a column has been clicked to sort descending. It reappears when sorted ascending.

This could be strictly a Modalframe API issue but I'm having the problem specifically with Node Relationships' implementation of it, so I thought I'd start here.

markus_petrux’s picture

Category: bug » support
Status: Active » Closed (duplicate)

The Node Relationships module enables Views Ajax internally, see function noderelationships_get_noderef_view_overrides(), so these links should not trigger a page refresh, nor open on separate windows.

If yours is an issue related to Views 3, then please open a separate issue, because Views 3 could have been changed there, and that's a different story.

fuzzyjared’s picture

In my case the reason why it was not working was due to a template issue in which my view template lacked the proper id to be target within the ajax event