I don't have a problem, though, I am trying to avoid one.

I'm hoping to relate thousands of nodes to thousands of other nodes, and I imagine I expect to come up against the maximum more than once.

Specifically, I have a node type document and a node type url. Many urls show up in more than 50 documents. I could use a taxonomy for the URLs instead, but then I wouldn't be able to assign taxonomy terms to them :).

Why is there a maximum?

Comments

calebtr’s picture

calebtr commented
Title: 50 reference maximum » 50-line maximum not honored for select fields
Category: support » bug

Ok, it seems like the 50-maximum is on the number of lines returned by the auto complete field, not the number of references - is that correct?

If it is, there is a bug when the field is set as a 'select' - the 50 line maximum is not honored.

steve.m’s picture

steve.m commented

I arbitrary chose 50 as the maximum no. of elements/lines to be stored in one multireference field. That could quite easily be made user-configurable.

Are you saying that you have created a multireference field and used it to store more than 50 references?

Rosamunda’s picture

Rosamunda commented

suscribing.
I think that the admin should be able to set the max to infinite (something like "set 0 for no limit").

Amazing module, thanks!

calebtr’s picture

calebtr commented

I'm just looking over my old issues - yes, I had nodes that referenced 50 or more other nodes and was building the nodes programatically.

When I went to edit a node, the 10s of thousands of possible nodes in the multireference 'select' widget crashed my browser, which is why I was wondering about that.

I solved my problem when I realized I didn't need multireference at all - I reversed the direction of the references, so 50 nodes were referencing 1 instead of 1 referencing 50, and themed a node.tpl.php to display the references.