Flexifield simplification

ndm - September 1, 2009 - 23:25
Project:Flexifield
Version:6.x-1.0-alpha5
Component:Code
Category:feature request
Priority:normal
Assigned:Unassigned
Status:active
Description

I love this module, very powerfull, very beautiful. But the possibility to have the content in another presentation are not simple.

So i have this idea :

-can flexifield have the possibility (by a checkbox in the content type, or in the node edit form) to store data in a node and not just in a table, is make as a node type, it's should be easy.

#1

crea - September 9, 2009 - 13:18
Status:active» won't fix

And then you will need to connect another node to your main node, and ask yourself:
Why am I using flexifield instead of nodereference or any other solution that connects different nodes together ?

Flexifield needs to store its own data inside the node, that way data integrity is no problem and all node properties (such as revisions) apply to flexifield data too.

#2

ndm - September 18, 2009 - 23:54

So on the question why i'm using flexifield?
- i use flexifield to have complex data group
- i use flexifield because this group his editable in the same place that the node
- but for me it's like a node reference that i can edit without open another windows or popup or what you want

In addition, the revisions apply too to nodereferences fields. To have a flexifield you must define a content type, so if you have a content type, you have a node representation. The only good reason i see to store flexifield in the base is to have less sql query, and to don't have comments and all properties like this.

For me a good composite field is like flexifield in form (edit and view) but node reference in store (with a possibility of reuse it in another place).

So maybe, do you know how i can use a flexifield in another node? Because this is my start idea.

#3

ndm - September 18, 2009 - 23:57
Status:won't fix» active

Another possible idea is to design a flexifield in another place than the content type because if flexifield is not a content type with node representation, why design it here? It's a confusing choice.

As i don't know if the maintainer is agree with crea speach i reopen this issue.

#4

ndwilliams3 - December 2, 2009 - 01:50

That functionality would be great. I want to add multiple images to a node, with the ability to to use taxonomy to tag the images. I want it to be easy to upload the images, but also want to use the images in galleries based on taxonomy. I don't want to create an image node and use node reference, because it makes adding the images much more labor intensive. I am looking at using flexifield for this purpose, since I can use views to create the galleries. Creating actual nodes would be excellent! Using popups works, but it sucks!

 
 

Drupal is a registered trademark of Dries Buytaert.