Content Construction Kit (CCK)

I know that I will most likely be wrong about this, but with the advancement of CCK, Views, OG and Panels, is the forum module really necessary anymore? My idea being is that with all these "practically core" modules, isn't it feasible to create a forum with just these modules?

I can create a content type called "forum post" manually, set the taxonomy for the forums (granted containers would be an issue) and use views to custom tailor the data shown to the users. I can already create 8/10th's of the forum functionality with just that scenario. Unless I am missing something.

I have a custom module I inherited that implements its own CCK widgets to import videos, and the widget stores multiple columns in the database, but to the user, it all seems like one field.

I recently decided we needed to add a column to refer to the thumbnail, so I edited my 'database columns' operation in the hook_field_settings() function, and added a line in the hook_field() function, along with the logic I needed to fetch, display and validate the data.

Much has been said (http://groups.drupal.org/node/9297) about how fields should be structured in D7 core, what aspects of fields can be changed, and how those changes are implemented. It is (past) time to move forward on implementing fields in core and in this post I am proposing an answer.

Disclaimer: I make a lot of declarative statements in this post. Obviously I do not have unilateral authority; this is just a proposal.

Field storage

I have a CCK contentType who's fields don't correspond to the node/add form elements, so I want to put some code between the form submission and the the db INSERT.

This hack using hook_nodeapi doesn't work because $form isn't passed to nodeAPI, and CCK seems to insert the node regardless of, or before anything that happens through nodeAPI.

Having manipulated the form data, I also want a confirmation page. I already wrote a module to define the contentType, but stalled when I realised that my fields were not exposed to views.

What is the best way to break up a long single CCK form across several tabs? A recommendation of something not in DEV would be great. It is for a PROD site. Thanks.

Hi, this is, to be sure a simple question for anyone who knows even rudimentary .PHP, but even after most of an entire day, the solution continues to elude me.

I am building a custom content type in Drupal 6 where registered users can submit their events. Fields include event name, time & date, etc., as well as a e-mail field and the sponsoring organization’s URL(s). “field_email,” use the “Text Field” widget. “field_link”, logically uses “Text Fields for Title and URL.” These two are not required and both allow multiple values (unlimited).

Hello Everyone,
Is there a way (a view, an existing module, a swell hack), to limit the display of a vocabulary in a node editor?
For example:

Countries (Vocabulary)
- Africa
   - Kenya
   - South Africa
- Asia
   - Japan
   - Thailand

I am on project where i am using nodereference and while i was working on linking two node types, a question came into my mind : How does nodereference handle node revision ?
For instance when we link node A to node B and sometime later someone creates a revision for node B, does nodereference keep a reference to the old node or to the new revision ?

Moved to official ideas list at http://drupal.org/node/236469

I'm not a student, but I'm posting this idea as a project I'd like to see happen. The idea was inspired by Benjamin Keen's Really Simple Validation and PHP Validation pair of scripts. Those two scripts use identical rules to perform both client-side and server-side form validation using Javascript and PHP respectively.