|
1 <?php |
|
2 |
|
3 /** |
|
4 * @file |
|
5 * Default theme implementation to present all user profile data. |
|
6 * |
|
7 * This template is used when viewing a registered member's profile page, |
|
8 * e.g., example.com/user/123. 123 being the users ID. |
|
9 * |
|
10 * Use render($user_profile) to print all profile items, or print a subset |
|
11 * such as render($user_profile['user_picture']). Always call |
|
12 * render($user_profile) at the end in order to print all remaining items. If |
|
13 * the item is a category, it will contain all its profile items. By default, |
|
14 * $user_profile['summary'] is provided, which contains data on the user's |
|
15 * history. Other data can be included by modules. $user_profile['user_picture'] |
|
16 * is available for showing the account picture. |
|
17 * |
|
18 * Available variables: |
|
19 * - $user_profile: An array of profile items. Use render() to print them. |
|
20 * - Field variables: for each field instance attached to the user a |
|
21 * corresponding variable is defined; e.g., $account->field_example has a |
|
22 * variable $field_example defined. When needing to access a field's raw |
|
23 * values, developers/themers are strongly encouraged to use these |
|
24 * variables. Otherwise they will have to explicitly specify the desired |
|
25 * field language, e.g. $account->field_example['en'], thus overriding any |
|
26 * language negotiation rule that was previously applied. |
|
27 * |
|
28 * @see user-profile-category.tpl.php |
|
29 * Where the html is handled for the group. |
|
30 * @see user-profile-item.tpl.php |
|
31 * Where the html is handled for each item in the group. |
|
32 * @see template_preprocess_user_profile() |
|
33 * |
|
34 * @ingroup themeable |
|
35 */ |
|
36 ?> |
|
37 <div class="profile"<?php print $attributes; ?>> |
|
38 <?php print render($user_profile); ?> |
|
39 </div> |