Hello,
I am enjoying your module, it works great,
I have searched for a while and trying to get it work with flexifield, but I can't find a way to do it,
I have copied the jquery code into a block and put this block on the new node/add page.
to make it clear an example.
Node type A Playground element (swing, slide etc) this is the element 'idea'
Title
Product code
creation set number
certificate
Photo of the 3d Render
Node type B playground element in situation
Nodereference field to node type A (here I use the module)
Date of putting in the the playground
Quality of the product under the circumstances of playground
Node type C Playground log
Flexifield nodetype B
I want to see the buttons of node relationships inside nodetype C
If I am not clear enough please ask for details,
I will be really grateful if someone could help me with this,
and sorry for my bad enlish
Greetings Daniel, At the Rise of Day
Comments
Comment #1
danielbeeke2 commentedI found a solution
don't know if its really safe
but I downloaded an old cck-6-3 and I copied the multigroup module over to my up to date cck module
than I used this multigroup to do what I needed
so.. I don't need an other solution anymore
greetings
Comment #2
markus_petrux commentedYes, the problem is not in Node Relationships module, but in the way Flexifield is coded internally. Instead, you can use CCK3 that includes the Multigroup module.
Comment #4
thommyboy commentedis there any way to make it work with flexifield? we want to use the module on a site that already has thousands of nodes with flexifields so switching to a multigroup solution is not possible... @markus_petrux i understand it's a flexifield issue but could you possibly shine some light on what would be needed to be done?
Comment #5
markus_petrux commentedPlease, do not re-open unless something needs to be adapted here to make things easier for Flexifield. Sadly, I do not have the time to look at it again now.
Note that NR is fully compatible with Multigroup, which is included in CCK. That's the way to go, IMHO.
Comment #6
dagomar commentedChanging the status because this clearly is not "fixed", but won't fix.