me aliases

ahoeben - November 11, 2006 - 18:30

Provides shortcut paths to current user's pages, eg user/me, blog/me, user/me/edit, tracker/me etc.

This means logged in users no longer have to know/remember their uid, and it makes it easier to link to user-specific pages from a site help page (without resorting to using php to put $user->uid in the link).

Drupal 5
After installing and enabling the module, site administrators can specify any number of aliases containing the fragment 'me'. The module uses the menu system to replace /me/ in a request with the user's uid, and forwards the request to the newly formed url. Making an alias for user/me also enables user/me/edit, user/me/edit/Personal+information, etc.

Drupal 6:
In Drupal 6, site administrators no longer need to specify their aliases. The me module will find most places where a user id can be passed via the menu, and will allow those menus to work properly with the 'me' alias in place of the user id. Site admins can alter how me handles these paths on the me settings page. Available options are:

  • Provide the ability for admins to control if links for tabs etc.. are rewritten with the 'me' alias.
  • Provide the ability for users to choose if they want 'me' alias on their account (Provided the admins turn on the option).
  • Allow admins to choose if 'me' should redirect to the path with the uid, and not stay on the 'me' aliased path.
  • Provide the ability to allow admins to redirect anonymous users to a path of their choosing.
  • Provide the ability for admins to use an include/exclude path filter for the list of paths that are affected by me. This is almost identical to the block configuration settings. Admins with the appropriate permission can also use PHP for this list if they desire.
  • Ability to add a views argument validator which correctly checks and handles the me alias for arguments the "ME" validator is enabled for. (6.x-2.7 or greater only)
  • Ability to change the me alias, which includes the use of global tokens as provided by the Token module if it is installed. This includes the [user-name] token. Me does not depend on the token module, the tokens are an extra feature that is made available when the token module is installed.

** When upgrading, you will need to clear your caches and run update.php to avoid errors. **

You can clear your caches by going to admin/settings/performance and clicking the "Clear cached data" button at the bottom of the page.

Note: The 2.x branch requires Drupal 6.10 or greater to function correctly.

Releases

Official releasesDateSizeLinksStatus
6.x-2.72009-Jun-2614.49 KBRecommended for 6.xThis is currently the recommended release for 6.x.
6.x-1.102009-May-0115.31 KBSupported for 6.xThis release is supported but is not currently the recommended release for 6.x.
5.x-1.22009-Mar-317.79 KBRecommended for 5.xThis is currently the recommended release for 5.x.


 
 

Drupal is a registered trademark of Dries Buytaert.