I'm using nodereference explorer on a site with several million nodes. It works fine on the front end, but on the backend I can't access configuration settings for any of the fields for the content type that I have the node reference attached to. I can't add new fields either. Because the page just sits there forever trying to execute the default view query, apparently trying to load all of the several million nodes before it'll do anything else.

I have basically two content types - "item" and "review". There are millions of items. Reviews can be submitted for any item. The "review" content type has the node reference field linking it to the "item" content type.

On the "manage fields" page for the "review" content type, I can enter into the configuration settings for the node reference field type... but if I click on configuration for any of the other existing fields, the site just hangs. Slow query log indicates it's hanging on a query that starts with "SELECT node.nid AS nid, node.title AS node_title..." and then has all the rest of the fields from the "item" content type that are set up in the view for the node selection.

I've tried various adjustments to the view that's being used to selected the nodes. If for example I set up a global:null argument in the view default, and tell it to either "hide view/page not found" or "display empty text", then I can access all of the content type fields fine... but I can't submit the node on the front end. I get a "the post can't be referenced" error.

Is there some way that I can stop the module from loading the default view when I'm trying to manage fields? I mean... why would it be doing anything anyway? Why would it the nodereference_explorer module be getting called on when I'm trying to manage other fields on the same content type, or add new fields? Shouldn't it only be loading when I'm either editing the configuration settings on the existing node reference field, or adding a new node reference field?

Note: I also tried more recent versions of the module, but ran into the same issue. And a couple of other problems that the older version didn't have, so I rolled back.

Comments

reallyordinary’s picture

Status: Active » Closed (fixed)

Actually - I'm dumb; there's an easy workaround for this. Whenever I need to change or add fields on the "review" content type I can just set up the global:null argument as above and make the changes and then remove it when done. The front end won't work temporarily, but it'd just be for a couple of minutes, and it's not like I'm going to be changing the content type fields constantly anyway.

Okay, so sort of a non-issue.