ID #9 (Previous | Next)

GET request to: admin/config/people/profile/edit/1

Ending URL: http://www.candidity.co.uk/drupal/tb_sirate/admin/config/people/profile/edit/1

Skip to main content

# Edit rjrF2p9S

Category *
The category the new field should be part of. Categories are used to group fields logically. An example category is "Personal information".
Title *
The title of the new field. The title will be shown to the user. An example title is "Favorite color".
Form name *
The name of the field. The form name is not shown to the user but used internally in the HTML code and URLs. Unless you know what you are doing, it is highly recommended that you prefix the form name with `profile_` to avoid name clashes with other fields. Spaces or any other special characters except dash (-) and underscore (_) are not allowed. An example name is "profile_favorite_color" or perhaps just "profile_color".
Explanation
clv12nWcn0FlqGzLdGMTWZt35o9OHykb2zteJ6dfC1UppYuQdO
An optional explanation to go with the new field. The explanation will be shown to the user.
Visibility
Hidden profile field, only accessible by administrators, modules and themes.
Private field, content only available to privileged users.
Public field, content shown on profile page but not used on member list pages.
Public field, content shown on profile page and on member list pages.
Page title
To enable browsing this field by value, enter a title for the resulting page. The word `%value` will be substituted with the corresponding value. An example page title is "People whose favorite color is %value" . This is only applicable for a public field.
Weight
The weights define the order in which the form fields are shown. Lighter fields "float up" towards the top of the category.
Form will auto-complete while user is typing.
For security, auto-complete will be disabled if the user does not have access to user profiles.
The user must enter a value.
Visible in user registration form.