Uploading files and managing them via a web browser has been a tricky task in traditional web development. Luckily Drupal gives us tools to streamline this feature.
Of course, in true Drupal form, Drupal gives us many ways of dealing with file uploads. In this tutorial video we review one of the most popular ways, the file field.
The file field allows you to attach files to nodes and other entities in Drupal. It provides a wealth of options to help you better manage what can be uploaded, where it is stored and how it is displayed.
Recently, a member of DrupalSN.com (a social community for Drupal users) posed a question, "Is there a way to remove the label for a field on a content type?". This question brings up an interesting feature of the CCK module in Drupal - the ability to style your content types on a field level. Here's how to do it:
Note: this tutorial assumes that you have the CCK module installed on your Drupal website, and you've already created a content type.
Step 1: Click on "Edit Content Type" in the Drupal Administration Menu
A recent upgrade of the ImageField module changes the way you add an Image CCK field. In the first drop-down list, select "File", and select "Image" in the second drop-down list.

Nodes fall into 3 categories:
1. Generated via a module, no CCK fields
2. Generated by CCK only
3. Created via a module with CCK fields added
For L10 projects, the CCK should not be used to create new content types (node type 2 from above). In instances where you may be tempted to create a node wholly by the CCK, create a node skeleton module and enable it first, then use CCK to add fields. A node skeleton does not add its own table.
No, unless you need extra or custom data. The CCK automatically handles loading of data for the fields created via the CCK. In general the CCK does a good job loading its data, however there are times where you might want additional data that is not automatically loaded.
Recipe for creating a node module skeleton:
1. Create three files using the code snippets at the bottom of this post
Note: replace foo with your module name. If this is for a specific project, use project codes in the format [pc][nodetype]
2. do the following search and replace on all three files
"[pc]foo" -> [pc][nodetype]
"foo" -> [nodetype]
foo.info code:
; $Id $ name = "Foo" description = "Foo posts." package = dependencies =
foo.module code: