'Domain User' same url for multiple users after change in username...rare possiblility

So the bug here is that the subdomain value needs to change when the username changes.

We would need to account for that in hook_user($op = 'update').

http://api.drupal.org/api/function/hook_user

There has to be something fixed at the code level.

Either that or you disable the ability to change usernames.

Not a problem. Note #1 is really a reminder to me (or anyone else who wants to try this fix).

No. That is the correct behavior.

Think of it this way, if you have multiple domains set up and then allow user-based domains, your administrative domains are more valuable and should be protected.

Look at the problem:

- You create a domain for 'guru.example.com' using 'create domain record'
- This is obviously a domain that is central to your site, and should be available to all users.
- If a user tries to register the username 'guru', then Domain User would try to create a record for 'guru.example.com' -- which already exists as a privileged domain record.

In this case, we have two options:

1. Register the user's domain as 'guru2.example.com' -- which is a bad solution for two reasons:
-- It is not the behavior that the user expects.
-- It requires us to do extra calculation when creating user domains.

2. Ban usernames that match 'privileged' domains.

The issue is not with the usernames -- Drupal already prevents two users from sharing a single username. The issue is that we don't update the Domain User record in the event that a user changes their username.

Patch that addresses the core issue.

Apply from the root 'domain' directory.

http://drupal.org/patch/apply

In this case, copy the patch file into the domain module directory on your server.

Then (using the command line) navigate to that directory.

Then type:

patch -p0 < domain_username.patch

And hit [enter] or [return].

I cannot answer that. You would need to ask your host.

Otherwise, FTP the files to your local machine, and edit the file by hand. Then re-upload the changes.

In this case, it is only adding a few lines to the end of domain_user_user() in domain_user.module.

Typically, we do all patch testing on test servers. So it would be best not to apply the patch to your live site.

Committed to HEAD and to 5-dev.