2

So what I'd like is:

If URI would look like {username}, load _thisTemplate.

Couldn't find the way without solid point like author ID.

Dominik Krulak
  • 1,562
  • 14
  • 27
  • Had the same issue, had to work around like: /people/phil-collins/832 ... – tom Jun 01 '15 at 12:53
  • One of the options, yes. I doubt, that it is possible yet. The craft needs to know, what user is the click link to and without assigning an user's ID, I think it's impossible. – Dominik Krulak Jun 01 '15 at 15:31

1 Answers1

10

I would not particularly advise creating a uri pattern that was just 'www.site.com/username' because usernames can essentially be anything which might cause routing conflicts (i.e. if the username is 'index' for example). You could however use something like 'www.site.com/members/username' or 'www.site.com/u/username'.

One way to do this would be to add a route using a 'subpattern'. For more info check out the routing docs on accessing subpatterns in your templates.

Here is the example given in the docs, which provides the variables 'year' and 'month' to the template that correspond to the matched uri segments (i.e. `news/2015/02'):

'news/(?P<year>\d{4})/(?P<month>\d{2})' => 'news/_archive',

You could essentially do the same thing but with a 'username' variable.

'u/(?P<username>[^\/]+)' => '_thisTemplate',

You can then use the 'username' variable in your template to retrieve the corresponding user.

{% set user = craft.users.username(username).first() %}
{% if user %}
    {{ user.firstName }}
    ...
{% else %}
    {% redirect 404 %}
{% endif %}
Douglas McDonald
  • 13,457
  • 24
  • 57
  • 1
    Note that by {% set user %} you're overwriting Craft's global user variable (i.e. the currently logged in user). Not a problem in most cases, but probably worth mentioning. – Mats Mikkel Rummelhoff Jun 01 '15 at 18:06
  • 2
    @mmikkel Good point. Although, 'currentUser' would still refer correctly to the currently logged in user, which I believe is the recommended usage anyway. – Douglas McDonald Jun 01 '15 at 18:14
  • To match everything but a slash for a URL pattern use this regular expression: (?P<username>[^\/]+) – carlcs Jun 01 '15 at 20:30
  • Thanks for the addition @carlcs. You also made me realize that I had an error in my expression, which was still expecting 4 digits. Corrected. – Douglas McDonald Jun 01 '15 at 21:37
  • For the given example above, How would you construct the link? <a href="{{ url('u/' ~ entry.author.username) }}">{{ entry.author.username }}</a> is what I have, but with 404 redirection. But anyway, some time ago I posted the question, if there would be possible to add a prefix to variable, like popular '#username'. In this case we wouldn't have to worry about any conflicts. Thanks to @Douglas McDonald, @mmikkel and @carlcs on participating this answer. – Dominik Krulak Jun 02 '15 at 08:08
  • 1
    Yes. The link you posted in your comment looks correct. As for the extra character, the pound sign "#", as you probably know, is reserved for anchor tag links — so I would suggest using something else at a minimum, perhaps dash "-" or underscore "_". Although the best in my opinion is still a subpath such as "/u/username". – Douglas McDonald Jun 02 '15 at 16:38
  • Yes, a subpath is very good insurance. And I think, I leave it like that. Also I've voted to reopen the question as it builds to this comment conversation. – Dominik Krulak Jun 02 '15 at 20:19