I'm not sure my request is even necessary, but it seems that since views and other modules can use nodereference, maybe a quick way to make this work with those modules is to have flexifield nodes automatically tie into nodereference. Then again, flexifield may already do all it needs to do with respect to views, etc. and making the related nodes known.

Comments

effulgentsia’s picture

effulgentsia commented
Status: Active » Closed (duplicate)

In regards to view integration, see #300668: Add views integration.
I don't think is what this issue relates to, but just in case, in regards to using nodereference within a flexifield, that does work and is covered in #357767: Node Reference broken when used with flexifield and selector.

While it's probably confusing (not helped by the lack of documentation), flexifield items are not saved as nodes: #290880: Document: how is this different from other node-link related projects. When I do work on documentation, I'll provide more of an explanation as to why. And if/when I work on views integration, #368262: Request for configuration option to save flexifield items as nodes, and/or #311413: Allow existing nodes to be added as flexifields, the item/node boundary may get blurrier.