Group items tagged

<?phpfunction themename_theme($existing, $type, $theme, $path) {  return array(    ...    // tell Drupal what template to use for the user register form    'user_register' => array(      'arguments' => array('form' => NULL),      'template' => 'user-register', // this is the name of the template    ),    ...  );}?>

<div id="registration_form">  <div class="field">    <?php      print drupal_render($form['account']['name']); // prints the username field    ?>  </div>  <div class="field">    <?php      print drupal_render($form['account']['pass']); // print the password field    ?>  </div>  <div class="field">    <?php        print drupal_render($form['submit']); // print the submit button      ?>    </div>  </div></div>

<?php  print '<pre>';  print var_export($form);  print '</pre>';?>

Method 1 : Printing your stuff and exit

Method 2 : Printing your stuff and returning NULL

Though one would think the $field object is what we wanted-- the actual object we needed is $row (even though we're only looking at one field in the row). Put the following into the field tpl file to see what the necessary info is: <?phpprint '<pre>';print_r($row);print '</pre>';?> Then, to actually make the link, put the following in your field tpl file: <?php$account = user_load($row->uid);print l($row->profile_values_profile_fullname_value, 'users/' . $account->name);?> Change 'profile_values_profile_fullname_value' to the proper field alias (based on the $row output). Also, be sure to change 'users' to whatever the path is for your user accounts. I also had another thought-- given your use case, you may want to consider the http://drupal.org/project/realname module as well. It will replace usernames with whatever field(s) you designate all over the site. EDIT: I had another thought. I'm not sure of the performance implications of doing a user_load in the template file. Another option is to add the 'User: name' field to the view but exclude it from display. Then you could avoid the user_load and change the code in the tpl file to: <?phpprint l($row->profile_values_profile_fullname_value, 'users/' . $row->users_name);?>

This helps to limit automated account creation attempts (by bots). This configuration can be accessed via the main Drupal navigation menu following the links for Administer -> User settings.

On the 'User settings' page you'll notice that some of the content of the e-mail templates are tokenized, including place holders such as "!username" and "!password." These tokens are replaced with user specific values before e-mails are sent. It is important to remove any occurrence of "!password" token to prevent user passwords being sent via e-mail. Without the password users must utilize a time sensitive link in order to activate their account or change their password.

You can install and utilize the Password Strength module (http://drupal.org/project/password_strength) in order to require that users select strong passwords

One issue that comes up from ApacheSolr being a separate search page is that the search form does not go to it by default. This is the $search_box in the page.tpl.php template. The way we change this behavior is to add a new submission handler to that form. You can create a custom module for this or put it in your custom theme. <?php/*** Implementation of hook_form_alter()*/function custommodule_form_alter(&$form, $form_state, $form_id) {  // Add submission handler to redirect to apachesolr  if ($form_id == 'search_theme_form') {    // Add a submit, because the search form redirects to a specific place    $form['#submit'][] = 'custommodule_search_submit';  }}/*** Implementation of form submit function*/function custommodule_search_submit($form, &$form_state) {  // Get form ID  $form_id = $form['form_id']['#value'];  // Create new redirect  $form_state['redirect'] = 'search/apachesolr_search/'. trim($form_state['values'][$form_id]);}?>

<?phpfunction garland_preprocess_views_view__my_view(&$variables) {  $variables['foo'] = 'some text';}?>