I tried to use this module a more advanced way :

A content type A have 3 cck field of type: date, text and taxonomy
Another content type B have 4 others cck field of type : date, text, number and flexifield of the content type A.
I did create another content type C which have the flexifield of content type B and other few cck fields.

When i create a new content of type C, the display is a total mess and no fields appears.

Is it possible to use this module this way ? should it be a new feature request ?

CommentFileSizeAuthor
#7 flexifield-fields-within-fields.patch3.41 KBzarexogre

Comments

PePiToO’s picture

I also forgot to say, when i create and submit a content type B and fill one or multiple flexi-field of content type A, the content type B will be create with success whereas none of the content type A will be create ( or at least nothing appear as content type A when i check the new content created page ).

Is it suposed to work this way as well or do i get it wrong ?

PePiToO’s picture

Title: Flexifield of a content type already including a flexifield » Add a flexifield
Version: 6.x-1.x-dev » 6.x-1.0-alpha1
Category: bug » support

Creating a flexifield in a node does not create a node for the flexifield, is it a functionality that will be added ?

effulgentsia’s picture

Title: Add a flexifield » Flexifield within flexifield
Version: 6.x-1.0-alpha1 » 6.x-1.0-alpha2
Category: support » bug

Saving flexifield items as separate nodes is not something I plan on adding yet, maybe some time in the future. See #368262: Request for configuration option to save flexifield items as nodes. However, having a flexifield within a flexifield seems like a reasonable thing to do, and is something I haven't tested yet, so I'm changing the status of this back to bug.

jonmc12’s picture

subscribing

semiaddict’s picture

subscribing

gregaltuna’s picture

Subscribing

zarexogre’s picture

StatusFileSize
new3.41 KB

I have a patch for this that seems to work. The url is not build correctly with the content type and field being populated wrong. Once these are correct it works perfect. I'm on dev version.