/user/me/edit is converted into /user/uid/edit

> The downside is, that /user/me/edit will get redirected to /user/uid/edit.

Note that this is the original behavior of the pre-6 module too. And for me, it was a feature, not a bug. As is, if a not-so-tech-saffy user ('user a') wants to send a link to their own page to someone else ('user b'), they may copy/paste the /user/me link. This will only work for the user a, user b will get a different page. IMHO, the url in the address bar of the browser should be without the dynamic 'me' alias.

I originally modelled the behavior of the module after flickr.com, which also redirects flickr/photos/me to flickr/photos/aldo (provided that I am logged in with a cookie).

The patch fails against the Dec.25 dev. Any chance of you re-posting it for the updated version?

I have views on user profile that rely on the uid arg, so I would really prefer /user/1/edit rather than /user/me/edit

Thanks,
Andrey.

After applying the patch manually, I get this error:

warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'me_user_edit_access' was given in /home/portal/includes/menu.inc on line 452.

Any ideas?

Thanks,
A.

mr.andrey,

probably you've missed some line. Sometimes such messages appear also after some code changes when cache is not cleared. In any case, it works for me fine, and I am attaching my patch for Dec. 25 6.x-1.x-dev version.

---

ahoeben,

I disagree to consider this behavior as a feature. If you decide to use me instead of uid (what is more or less "cosmetic" if we are concerned just about how it looks in users browser...), it shall be consistent (I generally prefer URLs which look more logical / structured instead of just some IDs / numbers...). If you prefer uid, why to use me at all? ;-)

It is simply not logical to have me everywhere but for /user/uid/edit, as generally you don't share this address (or?).

On the other hand, it is (for me at least) extremely convenient to have a possibility to use a "general" link (as /user/me/edit) in some instructions for users or so (I am sure much more users are able to simply click on such general link to get straight to their settings - or some other content - as they are able to understand what uid is and how exactly to compose URL with it...). This functionality (ability to use "general" URLs which include uid in node content, where me is dinamically converted to uid for logged in users and to some other preset URL for anonymous users or users who don't have rights to access this content - for example to instructions about how to register etc.) shall be even in core by my opinion.

As I agree there are situations where user shall be aware of his uid also in case me is generally used (if the site owner/admin decide to use me module), I suggest to:

• introduce an option (settable for each user, if enabled by admin option) to choose weather to use /user/me or /user/uid (so anyone can use uid generally, but if he/she clicks to some link which includes me this is dinamically replaced by a relevant uid)
• put a link somewhere in user settings (if enabled by admin option) indicating uid also in case me is selected, with corresponding explanation about how to use it to share some personal content

So, if a web site has contents which users shall share among them (a need for personal uids to be shared), site admin can enable one or another option (or both). If not, there is no need to confuse users with more options as needed, and both options can be disabled for users.

It would have made sense to make it 6.x-2.0, since it is a total rewrite.

Thank you, cdale.

Everything seems to work fine for me (also the patched version).