I have a large amount of data, one type of content has over 80k
nodes and is a node reference for other content types. When
conditional fields is enabled is pulls in all of that data and
runs the system out of memory (over 1G at times) when trying to
modify field settings or even add a new field. As soon as I
disable conditional fields the memory issue clears up.  The off-
the-top-of-my-head solution would be to use ajax to load the
conditional fields on the fly if they're required. No need to
load all that data if it's not being used, and no need to load
every field if it's not being used.   Status:Active» Needs
review new616 bytes  The attached patch excludes Node reference
fields. With a few thousands nodes, the page was simply not
loading because of the invocation of hook_allowed_values, which
produces drop-down lists containing thousands of elements.  I
ran into the same issue as beck24 and your patch helped
immensely.  The site I am working on needed to be able to
exclude node references for certain cont