Postponed
Project:
CCK Blocks
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
13 Feb 2008 at 12:27 UTC
Updated:
11 Apr 2011 at 15:50 UTC
Jump to comment: Most recent
This module is so close to what I want to achieve. But is it possible to view CCK groups as a block rather than individual fields?
Cheers
Matt
Comments
Comment #1
fokkezb commentedSure... let's put that down for the 6.x version OK?
If you want to help porting and adding this feature, be my guest!
Comment #2
fokkezb commentedThat would be a task now ;)
Comment #3
matthew_ellis24 commentedI'd love to help, but I wouldn't know where to start!
Comment #4
fokkezb commentedComment #5
Anonymous (not verified) commentedAnyone any ideas on that topic?
Comment #6
jonathan.kim commentedI'm very interested in helping, but I don't know the CCK well enough. Any info would be great.
Comment #7
jonathan.kim commentedI took a look at the CCK Blocks module, and it uses $field = module_invoke('content', 'fields'). Would it be possible to do something like...
$field .= module_invoke('fieldgroups', 'groups')
Any ideas? I'd really like to get this moving.
Comment #8
Anonymous (not verified) commentedCan you give some examples how you plan to use that feature?
Comment #9
ManyNancy commentedSubscribe.
Comment #10
shunting commentedTo get a number of fields into one block!
Comment #11
Boletus commentedYes it would be neat to be able to have a CCK group as a block, for instance lunches of the week: seven text fields where the user can add menu entries. :)
Comment #12
andrewtf commentedJust adding my opinion that this would be a really, really, really useful feature for CCK Blocks.
Comment #13
perke+1 I'm using multigroups from cck-6.x-3.x-dev and would love the option to show the group as one block
Comment #14
Dret commentedSuggestion or Dream? :)
Would be great to have a single block with all cck fields (and groups) avaiable inside, with possibility of integration with CCK Fieldgroup Tabs.
Final result: all cck informations for a node could be placed everywhere and not only inside $content, with easily navigation through tabs (optimizing spaces on page).
Comment #15
magpie5212 commentedSame needs here too. I have related fields which would be better in a single block. Aside from everything, it makes the block headings work correctly - all fields under a single <h2> instead of having two or three blank headings.
Comment #16
doublejosh commentedLooks like this is already being discussed and has working code: http://drupal.org/node/462924
Comment #17
magpie5212 commentedI decided that it was easier to use a custom PHP block than to try to patch the code to get a group showing. This also means I can format the information as needed.
Comment #18
jfall commentedThanks magpie5212 - you gave me an idea!
I don't like putting code directly into node bodies (can be maintenance headache during major version upgrades). But I documented how you could use that idea to put the code in a custom template file:
http://drupal.org/node/1078298
Works a charm!
Hope that helps someone.
Comment #19
Melissamcewen commentedsubscribe. Very interested!