This commit was manufactured as part of Drupal's Great Git Migration to

create tag 'DRUPAL-6--2-0-RC9'.

Sprout from DRUPAL-6--2 2008-10-06 20:03:12 UTC Karen Stevenson <karens@45874.no-reply.drupal.org> 'Change update instructions to recommend leaving CCK modules out of the modules folder until they're enabled.'
Delete:
    help/add-existing-field.html
    help/add-existing-field.png
    help/add-new-field.html
    help/add-new-field.png
    help/add-new-group.html
    help/add-new-group.png
    help/add-new.png
    help/add.html
    help/content.help.ini
    help/drag-groups.png
    help/drag-new.png
    help/draggable.png
    help/group-node-display.png
    help/group-node-edit-form.png
    help/manage-fields.html
    help/rearrange.html
    help/remove.html
parent d9c1e408
<p>Using a field across several content type can be handy if a piece of data
is relevant for several content types. A typical use case is a 'Phone number'
field, used in both 'Restaurant' and 'Hotel' content types, even if hotels
and restaurants are different enough to deserve their own specific set of
fields and thus their own dedicated content types.</p>
<p>When a field has been added to more than one content type, we also say it is
"shared", and that it as "several instances".</p>
<p>At the bottom of the <strong>Manage fields</strong> page for a content type,
you'll find this:</p>
<img src="path:add-existing-field.png">
<p>In order to add a new instance of an existing field to a content type, you
need to provide the following information:</p>
<dl>
<dt><strong>Label</strong></dt>
<dd>
A human-readable name for the field. It will be used in input forms and
on displayed content.<br/>
All characters are allowed, including spaces, accentuated or non-european
characters.<br/>
</dd>
<dt><strong>Field:</strong></dt>
<dd>
The field to be shared.<br/>
A field cannot appear more than once in each content type. Thus, only
fields that are not already present in the current content type will be
proposed as "shareable". If none, the <strong>Add existing field</strong>
option is not available on the <strong>Manage fields</strong> page for
this content type.<br/>
Selecting a field automatically populates the <strong>Label</strong> and
<strong>Widget</strong> values with the ones used by the previous field
instance, but you can change them if needed before submitting the form.
</dd>
<dt><strong>Widget:</strong></dt>
<dd>
The form element that will be used to input data for this field on
content forms : text input, select list, etc...<br/>
Each field type has its own list of available widgets. When selecting a
field to share, the list of widgets you can select is automatically updated.
</dd>
</dl>
\ No newline at end of file
<p>At the bottom of the <strong>Manage fields</strong> page for a content type,
you'll find this:</p>
<img src="path:add-new-field.png">
<p>In order to add a new field to a content type, you need to provide the
following information:</p>
<dl>
<dt>Label:</dt>
<dd>
A human-readable name for the field. It will be used in input forms and
on displayed content.<br/>
All characters are allowed, including spaces, accentuated or non-european
characters.
</dd>
<dt>Field name:</dt>
<dd>
A machine-readable name for the field. It is used internally to identify
the field and handle database storage. When doing custom theming, it is
this identifier that you'll use to refer to that field.<br/>
<strong>Important:</strong> The field name cannot be changed once the field has been
created.<br/>
Allowed characters: a-z (unaccentuated), 0-9 and the underscore (_).<br/>
The length of the field name cannot exceed 32 characters (including the
'field_' prefix that gets added automatically - that is, 26 free characters)<br/>
</dd>
<dt>Field type:</dt>
<dd>
The type of data to be stored in that field.<br/>
<strong>Important:</strong> The field type cannot be changed once the field has been
created.<br/>
The available field types depend on the modules you have enabled on your site. CCK comes with 6
basic field types :
<ul>
<li>Text</li>
<li>Integer</li>
<li>Float</li>
<li>Decimal</li>
<li>Node reference</li>
<li>User reference</li>
</ul>
Additional modules can be downloaded to handle other field types such as
dates, files, images... Look at the
<a href="http://www.drupal.org/project/cck" target="_blank"> CCK project page</a>
and the <a href="http://drupal.org/project/Modules/category/88" target="_blank">complete list of CCK-related modules</a>.
</dd>
<dt>Widget:</dt>
<dd>
The form element that will be used to input data for this field on
content forms : text input, select list, etc...<br/>
Each field type has its own list of available widgets. When selecting a
field type, the list of widgets you can select is automatically updated.
</dd>
</dl>
\ No newline at end of file
<p>Field groups are used to visually gather several fields that are associated
by some sort of logic, for instance several text fields that hold the different
parts of an 'Adress'. On input forms and displayed content, the corresponding
fields are enclosed inside an HTML fieldset.</p>
<img style="vertical-align:top" src="path:group-node-edit-form.png">
<img style="vertical-align:top" src="path:group-node-display.png">
<p>At the bottom of the <strong>Manage fields</strong> page for a content type,
you'll find this:</p>
<img src="path:add-new-group.png">
<p>In order to add a new group to a content type, you need to provide the
following information:</p>
<dl>
<dt><strong>Label</strong></dt>
<dd>
A human-readable name for the group. It will be used in input forms and
on displayed content.<br/>
All characters are allowed, including spaces, accentuated or non-european
characters.<br/>
</dd>
<dt>Group name:</dt>
<dd>
A machine-readable name for the group. It is used internally to identify
the group. When doing custom theming, it is this identifier that you'll use
to refer to that group.<br/>
<strong>Important:</strong> The group name cannot be changed once the group has been
created.<br/>
Allowed characters: a-z (unaccentuated), 0-9 and the underscore (_).<br/>
The length of the group name cannot exceed 32 characters (including the
'group_' prefix that gets added automatically - that is, 26 free characters)<br/>
</dd>
</dl>
<p>Once a group has been created, you can define what fields it will enclose by
<a href="topic:content/rearrange">rearranging fields and groups</a>.</p>
\ No newline at end of file
<p>The form elements at the bottom of the <strong>Manage fields</strong> page
let you add fields and groups to your content types.</p>
TODO : new image
<img src="path:add-new.png">
<p style="font-size:smaller">(The <strong>Add existing field</strong> row is
displayed only if there are fields available in other content types.
The <strong>Add new group</strong> rows is displayed only if Fieldgroup module
is enabled.)</p>
<p>Your fields and groups will be created after you click the <strong>Save</strong>
button at the bottom of the page. In subsequent pages you will be presented
with the settings form for each field you added.</p>
<p>You will find more details on the required informations in the
following pages:</p>
\ No newline at end of file
; $Id$
[advanced help settings]
name = CCK
index name = "CCK (Content Construction Kit)"
[manage-fields]
title = 'Manage fields' tab
[add]
title = Add fields and groups
parent = manage-fields
weight = 1
[add-new-field]
title = Add a new field
parent = add
weight = 1
[add-existing-field]
title = Add an existing field : share a field across content types
parent = add
weight = 2
[add-new-group]
title = Add a new group
parent = add
weight = 3
[rearrange]
title = Rearrange fields and groups
parent = manage-fields
weight = 2
[remove-field]
title = Remove a field from a content type
parent = manage-fields
weight = 3
<p>This page lets you manage the CCK fields in your content type : add fields and
groups, rearrange them, access their configuration pages, remove them from the
content type.</p>
\ No newline at end of file
<p>To change the order of fields, grab a drag-and-drop handle
<img src="path:draggable.png"> and drag the field to a new location in the list
(grab a handle by clicking and holding the mouse while hovering over a handle
icon). Remember that your changes will not be saved until you click the
<strong>Save</strong> button at the bottom of the page.</p>
<p>The order you define will be used both on input forms (when creating or
editing a post), and on content display (teasers, content page, RSS items...)</p>
<p>You can also change the order of non-CCK 'fields' like <strong>Title</strong>
or <strong>File attachments</strong>. Depending on the 'field', this will
affect input forms and/or content display (some of those 'fields' are not
displayed in both contexts).</p>
<p>If your content type has groups (requires the Fieldgroup module), you can
move a field inside a group by dragging it below the row of the group, and
then slightly to the right before dropping it. Note that groups can also be
reordered, but can currently not be nested inside other groups.</p>
<img src="path:drag-groups.png">
<p>When adding a field or a group, you can drag them directly to the
intended spot in the list of fields and groups that are already present in your
content type, before clicking <strong>Save</strong>:</p>
<img src="path:drag-new.png">
\ No newline at end of file
<p>When you remove a field from a content type, the data it holds are
<strong>permanently</strong> erased. You will be asked to confirm this action</p>
<p>>You will have to manually update your Views, pathauto settings, etc... if
needed.</p>
<p>Note : if the field is shared across several content types, removing it from
one content type does <strong>not</strong> affect the data for the other content
types.</p>
\ No newline at end of file
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment