I like to have the user’s full name in their profile page-url rather than the username in case they don’t want their username associated with their full name. In my case they don’t get to set the username at the sign up point but might been asked for a username by the person signing them up.
So, how do i use the user’s full name as an identifier in the url of their profile page?
Like so: example.com/user/first-last
Is that even possible?
Although the craft.users tag let you find users who have firstName or lastName matching whatever, I wouldn't try to match just against that, as you could end up having users with the same sames.
I would include the id of the user in the URL, so you would have something like example.com/user/1-first-last
Then you can lookup the profile by doing this:
Graf the profile with something like this:
{#
- Use matches variable from dynamic route
- matches.number will give you the expected id if you only have
one number segment in your dynamic route
#}
{% set userId = matches.number %}
{# Find user #}
{% if userId is defined %}
{% set profile = craft.users.id(userId) | first %}
{{ profile.name }}<br/>
{{ profile.username }}<br/>
{{ profile.email }}<br/>
{{ profile.id }}<br/>
{% endif %}
Marcus, I think you can use anything as an url for a user's page. In your case, I'd make a dynamic route like:
user/*
and assign it a template, for instance:
user/_entry
Within that template, all you'd have to do is lookup the user by the match found in the url. The variable matches contains the first-last part (the * part of your route). With that, the user should be easy to find:
{% set names = matches[1] | split('-') %}
{% set user = craft.users.firstName(names[0]).lastName(names[1]).first() %}
{% if user %}
// Do with it what you want
{% endif %}
You'd have to be careful, however, that no two identical first- and last name combinations exists. The advantage of using the username is that it's always unique.
