Closed (works as designed)
Project:
Display Suite
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
12 Aug 2009 at 11:20 UTC
Updated:
29 Dec 2009 at 20:24 UTC
Firstly, I think this module is really interesting!
But I am curious to know how this module handles the following:
1) When you have a Group, will it display the fields together that are belonging to that group?
2) When you have a Multi-value field, does it allow you to seperate the multi-values and display then in different regions of the screen?
For example, display the first textfield_value in the footer and the second value of textfield_value in the header?
3) How does it handle grouped, multivalue fields?
Comments
Comment #1
andrewsuth commentedAlso, can this module be used to make changes to an individual node (such as
node/3or only an entire content-type?Comment #2
swentel commentedTo answer to your first 3 questions: we haven't tested that yet. The main reason is because we are using the node form colums module to alter the node edit screen to our likings. However we should look into that and see what happens when you defined groups. Rendering multiple values in different regions will be impossible afaik. However, we'll be checking that out!
At this point, the changes are applied to the entire content type. It's an interesting use case however and it shouldn't be that hard to implement. It's a low priority on the todo-list imo.
Comment #3
andrewsuth commentedHi swentel, thanks for your quick reply.
I have a fairly specific requirement for a module *like* this one but I do not know if it's on your development roadmap:
Basically, a module that gives users much more fine-grain control to customise the layouts of individual nodes, ie. choosing where each CCK field (both multi-valued and grouped fields) appear on each node to be rendered. As far as I have seen, you're module has the most potential for evolving into something along these lines.
Although my case is not for writing newspaper articles, I think they would also be very interested in such an idea for quickly laying out each news item, once the content has been created.
Andrew
Comment #4
swentel commentedMoving this to other queue, since this now belongs to the nd_cck package (except the individual node override, which I'll add the queue myself)
Comment #5
swentel commentedWe are working on patches to integrate with fieldgroups cf #582618: Incompatible with fieldgroups. Moving to node displays for the individual node request rendering.
Comment #6
swentel commentedBelongs to 6--2 branch also.
Comment #7
swentel commentedUpdating title, we are going to implement a cool feature, namely a property in the api which will define the extra field in the db with hook_schema_alter and the menu item, rock and roll! :)
Comment #8
swentel commentedThis also belongs to DS queue - and now for some actual coding .. :)
Comment #9
swentel commentedAnd after actual coding, we saw this is actually not possible - at least without any other storage mechanisms and certainly overriding how CCK is rendering it's output. So for now, by design. Maybe if someone comes up one day with a super patch :)