Node Reference broken when used with flexifield and selector

Is the issue with the Link field or the Node Reference field?

it happens when you have a nodereference field inside a node in a flexifield. The view to populate the selector is simply not called.

However it works with autocompletion fields so there is a workaround.

Moving to corrct place, changing title.

Actually, this is probably more of a flexifield issue.

It appears that this is so because $form['#field_info'][$field_name] is not set inside the process function. flexifield tris to do something about it in flexifield_setup_form_field_info_hack but that does not appear to work.

I've investigated this some more and I think the probkem is due to the fact that the nodereference field re-.uses the fields created the fields from the optionswidget module in its process function. This leads to the optionswidgets process function being called although not defined in the form and thus the tricks devised by the flexifield author don't work.

This is now fixed in 6.x-1.x-dev (you can grab it from cvs or you may need to wait 12 hours for the tarball to be regenerated). I will release a 6.x-1.0-alpha2 version by March 4, 2009 that will also contain this fix.

I believe this fix relies on a patch to form.inc, namely that you pass $complete_form by reference into form_builder_handle_input_element, is this correct?

Nope. The fix works without any patches to drupal core or to cck. I'm hooking into the #process array of the specific element, where I'm inserting a function that takes the form by reference and is able to add '#field_info' to it in a way that sticks when the element's normal #process function is called. A lot more code than if form_builder_handle_input_element() took $complete_form by reference, but it does work with a clean drupal install.

Alpha2 is released!

Automatically closed -- issue fixed for 2 weeks with no activity.