Jump to:
| Project: | Content Construction Kit (CCK) |
| Version: | 6.x-2.5 |
| Component: | Panels Integration |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
Issue Summary
Hey,
I've had a bit of experience with the wonders of the panels module but I'm having some trouble with the node edit form interface. I'm trying to redesign my node edit forms, and some of the form values aren't available as standalone options, namely some CCK fields and the location choosing interface.
With CCK fields: I have two imagefields (filefields) for a content type. One field, a preview image, is assigned to multiple content types, and the second, extra images, is only assigned to the content type in question (book). However, when I am trying to isolate the images from the form, the only cck imagefield I see is the extra images. The field which is available in multiple other content types is not shown as available to be placed in a panel. I'm trying very hard to find a solution to allow me to pull that field into a panel, along with the one I am able to use. Would you have any suggestions on how to go about this?
With Location chooser: Simply put, the location input with coordinate chooser is not available for input into panels. Is this by design? If not, how can I isolate that option?
Truthfully being able to isolate every specific instance of an edit form and configure it in panels would be a wondrous achievement with endless benefits.
I'm happy to provide screenshots if you think that would help in any capacity.
Thanks for your help and for this module!
Comments
#1
Ok, dumb question - but are you checking all the available content menus for the fields? Some stuff is on one menu, some (like some of the cck fields) are on other menus. I think there's plans to group everything together, but I know I've gotten into trouble trying to get all the fields I need into one place.
#2
It's impossible to understate how important and awesome panels is, but the d6 redesign is done in stages and by people who (I presume) don't get paid for their work. So, I figure that this functionality is just in starting stages and will grow into a more useful tool later down the line.
The problem is that the fields are grouped together - you really need to be able to separate each and every aspect of the $form array on a per form-id basis. So like, all CCK forms, the node taxonomy fields, the body fields, the authoring info, etc, etc, each should be it's own individual option, so you can design the form field at the smallest order of magnitude.
Panels takes a stab at this but it's not working well enough to have comprehensive, complex form layouts to the Nth degree. If/when each individual key in the $form array is available as a specific item in panels which can be dropped in and laid out, we can create the dynamic forms we need for any contingency.
In the mean time I've used hook_form_alter() to create and theme my forms as necessary. It's less than ideal, I'd rather run it through panels, but until I can really place each individual form item in a pane as a standalone item, I can't really use it to theme a form.
#3
Yeah - CCK has to make those fields available, and it doesn't necessarily do it as well. merlinofchaos suggests that fieldgroups are about the closest you're going to get at this point because the data just isn't available to Panels in a node context.
That said, I'm going to toss this over the fence to CCK as a feature request :}
#4
#253071: Panels integration for editing
#5
Sorry about that markus_petrux, I totally did not even go look for the issue that I should have known was there (since I've looked at it before :P )
#6
No problem.
PS: I think this is quite hard to do because it seems to me there are too many dependencies on the node form structure. If someone tries it, I would be happy to help.