Content tagged with: profile

Creating a Google Map showing user locations using the Content Profile, Location, and GMap modules

Submitted by Eric on Sat, 09/26/2009 - 23:32

In this blog entry I'll show how you can create a Google map showing where your users are located using CCK, Content Profile, Views, GMap, and Location modules. Once you've downloaded and extracted those modules, enable the following modules (and set permissions accordingly):

Content
Location
Location CCK
Content Profile
GMap
GMap Location
Views
Views UI

Next you'll need to configure these new modules. On the GMap settings page (admin/settings/gmap) you'll need to add your API Key and enable the setting to Use AutoZoom. On the Location settings page (admin/settings/location) enable the checkbox to use a Google Map to set latitude and longitude and enable JIT geocoding. On the geocoding settings page (admin/settings/location/geocoding), you'll have to enable Google Maps for the desired countries.

The Content Profile module creates a new content type called "Profile". You'll need to add a new field to this content type for the user's location (admin/content/node-type/profile/fields). Enter a label for the node type (Location), enter a field name (field_location), choose "Location" for the field type, and choose "Location Field" for the widget.

On the next screen edit the Locative information sections (Collection and Display) to your liking, and save the field settings. For my example, I enabled Street location, Additional, City, State, Postal code, Country, and Coordinate Chooser.

Now if you create your profile node (node/add/profile) you can enter your location information and save the new node. If all is working at this point, if you return to the profile node edit screen and scroll down to the location information, you should now see a marker on map for your location and the geocoded information will be shown.

Now you can add a new view (admin/build/views/add) to show the user's profile locations. Enter a name for your view, choose node for the view type, and click the next button. Add a new filter for "Node: Published" is true and "Node: Type" is one of "Profile". Add a new relationship for Content: Location (field_location). Add fields for "Location: Latitude" (using the Location relationship), "Location: Longitude" (using the Location relationship), and any additional fields you'd like to display in the GMap marker (title, parts of the address, etc). For the Style of the view choose "GMap". For the GMap style settings, select "Choose latitude and longitude fields" for the Data Source and ensure the Latitude and Longitude fields as set.

Lastly, I added a page view so I could see the results in action..

ps> special thanks to everyone at CommonPlaces for their great technical discussions about these modules!

8 comments

Adding functionality to allow users to select different profile themes

Submitted by Eric on Wed, 08/19/2009 - 11:13

In this blog entry, I'll show you how you can add some module code to allow users to select different themes for their profile page. I decided to use the standard user-profile.tpl.php as the base template. I copied this file into my theme folder and replicated it a few times. I named the files:

user-profile-version-1.tpl.php
user-profile-version-2.tpl.php

For my example, I simply added the text "Version 1" and "Version 2" to the top of these files to show it's working, but you could revise the layout, add CSS, etc.

Next, I created a module to contain all the following code. I defined a hook_perm() and hook_menu() function to add a menu local task (tab) to the user page.

<?php
function MYMODULE_perm() {
  return array(
    'choose profile theme'
  );
}

function MYMODULE_menu() {
  
  $items = array();
  
  $items['user/%user/choose-profile-them'] = array(
    'title' => 'Choose Profile Theme',
    'page callback' => '_MYMODULE_callback_choose_profile_theme',
    'page arguments' => array(1),
    'access callback' => 'user_access',
    'access arguments' => array('choose profile theme'),
    'type' => MENU_LOCAL_TASK,
  );
  
  return $items;
  
}
?>

Next, I defined the page callback to create a list of available templates for the user to choose from.

<?php
function _MYMODULE_callback_choose_profile_theme($user) {

  // create an empty strong variable for page html
  $html = "";

  // define a list of available profile templates
  $profileTemplates = array(
    'user-profile-version-1' => 'Version 1',
    'user-profile-version-2' => 'Version 2'
  );
  
  // loop through templates and ensure they exist
  foreach ($profileTemplates as $template => $name) {
    if (!file_exists(path_to_theme() . '/' . $template . '.tpl.php')) {
      unset($profileTemplates[$name]);  
    }
  }
  
  if (count($profileTemplates)) {
    $html .= drupal_get_form('_MYMODULE_callback_choose_profile_theme_form', $user, $profileTemplates);
  } else {
    $html .= "No profile themes currently exist.";
  }
  
  return $html;
  
}
?>

The following functions define the form array, and validation and submit handlers. When the form is submitted, the template option is saved to the user account variables using the user_save() function.

<?php
function _MYMODULE_callback_choose_profile_theme_form($form_state, $user, $profileTemplates) {

  $form = array();
  
  // add a select input element
  $form['profileTemplate'] = array(
    '#type' => 'select',
    '#title' => t('Profile Template'),
    '#options' => $profileTemplates,
    '#default_value' => $GLOBALS['user']->profileTemplate
  );
  
  // add a submit button
  $form['submit'] = array(
    '#type' => 'submit',
    '#value' => t('Submit')
  );
  
  // add hidden element for userID
  $form['userID'] = array(
    '#type' => 'hidden',
    '#value' => $user->uid
  );
  
  return $form;
}

function _MYMODULE_callback_choose_profile_theme_form_validate($form, &$form_state) {
  // TODO: add your additional form validation here
  
  // ensure userID submitted matches current user
  if ($form_state['values']['userID']!=$GLOBALS['user']->uid) {
    form_set_error('', t('Error processing form.'));  
  }
  
}

function _MYMODULE_callback_choose_profile_theme_form_submit($form, &$form_state) {

  // load user object
  $user = user_load($form_state['values']['userID']);
  
  // save profile template to user variables
  user_save($user, array('profileTemplate' => $form_state['values']['profileTemplate'])); 
  
  // set a message
  drupal_set_message('Your profile template has been set.');
  
}
?>

Last, I defined the preprocess function to see if a template has been set in the user variables, and add the templates suggestion to change the user profile template.

<?php
function MYMODULE_preprocess_user_profile(&$variables) {

  // ensure the template file exists, and is set in the user object
  if (file_exists(path_to_theme() . '/' . $variables['user']->profileTemplate . '.tpl.php') && $variables['user']->profileTemplate) {

    // set a templates suggestion
    $variables['template_files'][] = $variables['user']->profileTemplate;
  }
  
}
?>

As you can see below, when I choose the "Version 2" template option, the file "user-profile-version-2.tpl.php" is being loaded, and the text "Version 2" is displayed at the top of the page.

4 comments

Removing the history section from the user profile view

Submitted by Eric on Fri, 02/20/2009 - 12:23

Here's a quick snippet on how you can remove the History section from a user's profile using hook_user():

<?php
function MYMODULE_user($type, &$edit, &$account, $category = NULL) {
  // remove history from user profile view
  if ($type == 'view') {
    unset($account->content['summary']);
  }
}
?>

Add new comment

Adding validation to the user edit form to ensure username is a valid email address

Submitted by Eric on Fri, 02/20/2009 - 11:54

At some point you might want add validation to the user edit form to ensure username is a valid email address. You can accomplish this by adding a form_alter hook, testing for the user profile form, and adding a validation handler to the $form object.

<?php
function MYMODULE_form_alter(&$form, $form_state, $form_id) {
  // test for the user profile edit form
  if ($form_id == 'user_profile_form') {
    // add another validation function to the list
    $form['#validate'][] = '_MYMODULE_form_alter_user_profile_validate';
  }
}

// define the validation function
function _MYMODULE_form_alter_user_profile_validate($form, &$form_state) {
  // validate the username and set a form error as necessary
  if (!valid_email_address($form_state['values']['name']))
    form_set_error('name', 'Username must be a valid email address.');
}
?>

Add new comment

Overriding the node profile form and automatically creating your own title

Submitted by Eric on Wed, 02/18/2009 - 13:26

In a recent project I used the content profile module to improve flexibility in creating user profiles. This module replaces the regular profile creation with a CCK node type. One of the requested profile fields was job title, which is confusing since title is already a required field of a node. In most cases, I would use first and last name as the title, but in this case those fields were required to be separate. Since the node title did not fit into the list of requested fields, I decided to remove it from the form and dynamically generate a node title from the user's first and last name. Here's how this can be accomplished:

<?php
// create a form_alter hook to remove the field from the form:
function MYMODULE_form_alter(&$form, $form_state, $form_id) {

  if ($form_id == 'profile_node_form') {
    // remove title from view
    $form['title']['#access'] = false;
  }
    
}

// create a nodeapi function to create the node title when the node is created
function MYMODULE_nodeapi(&$node, $op, $a3=NULL, $a4=NULL) {
  if ($node->type =='profile' && $op=='insert') {
    $node->title = $node->field_profile_name_first[0]['value'] . " " . $node->field_profile_name_last[0]['value'];
    node_save($node);       
  }
}
?>

5 comments