Content Construction Kit (CCK)

I need a field module developed.

I'd like to define a field as being composed of multiple existing fields. Further, I want to make my new complex field "multiple". So each field instances inside the complex field are linked together persistently. I've exhausted my search, I don't think a solution exists.

A use-case is where you want to set up some micro-content, like an address form, and want this micro-content to be consistent across all nodes you use it in.

Hi,
I am digging deeper every day, but find it hard to translate the drupal and cck world into concepts I know from database applications and their toolkits, so I would like to ask, if maybe anyone would like to explain, how to create a master-detail view in a form?

I am trying to connect users, locations and events (I am not the only one, as you can see in the event group) and I guess the nodeprofile package might be helpful with this, but I really would appreciate a short explanation if this can be done with CCK only...

I've been thinking about some modules recently and about how to get the data they need. Looking at a general trend of "monolithic module" -> "individual CCK fields + helper modules + glue code" I'm curious how those "helper modules" can get the metadata they need to know how to interact with the CCK fields.

More specifically, we have the image module and then lots of helper modules image publisher which know how to interact the the image module because it's node type and data structures are set in stone.

So Drupal 6 has been the first release cycle I've been involved with on any level, did a few reviews and submitted some very small patches, and followed a lot more as they went in or didn't. The overriding feeling I've got from it is that the division in core between api and cms-type modules is causing problems that are increasingly hard to deal with.

The 6.x port will make some significant changes to the widget API, so it would be good for CCK module authors to take a look at the changes and let us know if they need to propose any adjustments. I have been trying to look at some of the most widely used CCK widgets to see how they will be affected and am pretty sure that the new methods will be flexible enough to handle their needs, but it would be good to have other eyes looking at this, so here is a summary of what is changing:

Looking for advice on when to use:

• http://drupal.org/project/taxonomy_fields
• http://drupal.org/project/cck_taxonomy
• http://drupal.org/project/content_taxonomy

They all seem confusingly similar.

Get release 5.2-1 here.

From the upgrade notes included in the release:

This upgrade is in response to the CCK security announcement.

While this security upgrade only affects a specific use of CCK that is not present in the DrupalEd configuration, anyone running DrupalEd is strongly advised to upgrade. A healthy dose of paranoia regarding security concerns can save you hours of time/emotional distress.

I'm new to CCK and have come across a problem when tryting to create a simple one to many relationship between 2 nodes.

I am able to create the nodes, one node is called company and the other programs. One company will have many programs. I have used the views module and can get some data out but it seems that something is going wrong in the table used to join the nodes together.

I currently have a widget that provides a textfield and that supports multiple values: when a user submits his node and edits it again, 3 extra text fields are presented. I based hook_widget on nodereference for this.

What I'm trying to accomplish now is to provide the extra fields after a user hits the Preview button, instead of having to Save and Edit. As far as I see the issue is that on $op == "form" the $items variable is empty or doesn't update with the new values unless you submit the form; it doesn't update on Preview. How is this normally handled? Is this possible?