CCK

I am creating - actually rebuilding from Coldfusion - an application that - among many other things - handles production work flow. Here is one scenario that is indicative of many more I will have to create:

User enters order for a product(in my case, a dress). Some of the details of this order that are captured are:

I have been developing two sites which revolve around the management and workflow of complex forms. On one of these sites, I created a content type using CCK. The content contains about 40 varied fields, some in groups. Some of the fields contain long text with complex medical terms. I loaded the database with 5000 forms and ran cron to get everything indexed.
The search results were incomplete. If I searched for a keyword that should find 13 documents, I might only find 7. If I touch the missing document (edit/save) and re-run cron. The search returns 13 documents.

Hello,

I've started using Views(6.x-2.11) with CCK(6.x-2.8) and recently I've add to the Page content type the text field Teaser (basically a small description).
Next I've created a view where one of the fields is the Teaser. In the view I've Title, Body and Path that are core fields of Page and teaser that is an additional field added using CCK.
When I do the preview of the view, the Teaser is displayed correctly. But when I go to the frontpage, the view displays all Node fields (Title, Body and Path) and the Content field (Teaser) is missing.

Over the last few days I have been trying to figure out how to properly use the services node.save function to save more than just a simple content type such as story which has just a title and a body. This I can do w/o any issues. The issues that im trying to figure out is when you have a content type lets just say only these fields right now

content type photo
* title
* body
* field_my_photo -- cck imagefield

--- fid i already had from file.save

I've recently been investigating the possibility of using Drupal for a simple LIMS for our lab. I've looked at the various open-source LIMS options, and everything seems like overkill for our purposes. All I need is simple job tracking as a sample moves between various stages of prep/analysis/QA/QC, and I thought Drupal might fit the bill nicely.

Currently, we rely on paper forms for tracking samples. Technicians fill out a "COC" (Chain of Custody), add samples to it, and the whole COC is moved about the lab.

Hello,
I recently finished my first build of my photo gallery on my website.
Take a gander here:
http://www.robertfoleyjr.com/gallery

I built it using:

CCK
Views
Lightbox2
ImageCache

I am interesting seeing solutions created by the community and discussing strategies. Provide links to galleries you have created and list what modules and or custom code you had to write to build it.

Peace out.

Hello

In my site nodes I include a views block wich provide a cck field_id value.

In the pages is included also a block containing a script;

I need to pass the field_id value to a string in the block, like

"<form action="http://example.jsp?ID=id method="POST" >"

where id should be replaced with field_id value

Thank you very much for any help!

Hello!

I am building a travel site; I am importing data from a hotel services provider through csv, and I have longitude and latitude fields for each article.
I wonder which is the simple way to provide map block for each hotel page, using the longitude and latitude fields.

Thank you very much!

Hi, love the module!

I was wondering if there was a known way to add a contact info collection form within the flow of the quiz or on the result page of a quiz? This is one of the only features missing in order to use the Quiz module as a contest/promotion engine on my site.

I'm used to creating custom node types with cck to achieve create contact info forms, but I'd like to blend that with the functionality of the Quiz module.

Hi all,

I've been wrestling with this for a while now, and read various conversations about why the Facebook-style Micropublisher module was designed the way it was, without using CCK and non-node based. But looking at the way Drupal is going and the modular approach it is taking, especially with fields being core in D7, I think that this type of functionality would be superb to be able to achieve using the various CCK modules.