Posted by austintnacious on March 17, 2009 at 9:33am
Jump to:
| Project: | Content Construction Kit (CCK) |
| Version: | 7.x-2.x-dev |
| Component: | fieldgroup.module |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hi!
Appreciation in advance for any help I get here!
I've been playing with editablefields.module and popups_subedit.module.
Both are super cool tho', at least in the case of subedit, they might be a ways from prime-time uses yet.
In playing with these modules I notice that there is no way to configure the default Title and Body fields provided by CCK.
This means that
- I can't use editablefields.module to allow my users to edit the title or body content
- I can't add the title and body fields to a field group to allow popups_subedit.module to edit the content in these fields
This is really unfortunate!
The only solution I can think of is to create my own custom title and body fields and use these but that would probably mean updating all my nodes which would be a serious hassle.
Anyone have any ideas?
Should I make this a feature request for CCK?
Thanks again!
Comments
#1
CCK doesn't provide the title and body fields, the Node module does. You edit them on the Content type edit form (the 'Edit' tab right next to the 'Manage fields' tab).
#2
OK! So the Node module provides the title and body fields. Thanks!
And I know where to find them on the Content Type (CCK) edit form.
What I don't know and would like to know is where / how to include the node title and body fields in a fieldgroup to allow me to manipulate them in the same way I am able to use other modules to manipulate fields in fieldgroups. . . makesense!?
It doesn't seem right to me that I cannot deal with title and body in the same way as other fields in the context of CCK. . .
#3
CCK won't change the structure of the form for elements that are not its own. Too many thinks can break in too many subtle ways leading to painful bugfixes. Sorry.
#4
Not even given CCK's pending core integration?
Please don't summarily close this. Reassign this to where the ultimate problem lies.
#5
Well, it just happens that the approach for core D7's 'vertical tabs' does not seem to imply reshuffling the $form array.
If fieldgroup uses the same approach for its own groups (which would be a good move IMO), then possibly my argument in #3 becomes moot and fieldgroup can handle non-fields.
Also note that in D7, 'Body' has been moved to a 'field', will benefit of the same features than any other admin-defined fields.
#6
retitle
#7
Glad to see this back on the cards. I was about to raise it as a feature request but now I can +1 this. If it's *possible*, it would be amazing to be able to use fieldgroup.module to order your node form fields any old way you like. At the moment we have to use hook_form_alter(), which is fine for devs (I just wrote a blog post about it, which is why it's fresh in my mind) but leaves site admins and the general populous a bit stuck.
Fingers crossed this turns out to be a viable feature for D7 (or even D8). =)
#8
This is done. Fieldgroups in D7 are also for 'extra_fields' (node title, views_attach components, etc...)
See http://drupal.org/project/field_group (still in pre-alpha stage for now).
#9
#10
Automatically closed -- issue fixed for 2 weeks with no activity.