Because of the way the node title is constructed for clients, it's perfectly possible and easy for users to create two clients with the same apparent name even if they are unique (unicity is currently based on email for clients).

This is particularly confusing when creating a site for a client or when selecting a client in any form: you get only one client back from the autocomplete, but it can be the wrong one. In that case we end up in a weird SNAFU: we choose a client we were presented, but we can't actually create a site with it because we don't have the perms. Really weird.

I think we should completely refactor the fields in the Client, but maybe that's not necessary to fix this issue, so I'll file that as a separate request (#962330: refactor and clarify the fields in the client content type).

Comments

anarcat’s picture

Status: Active » Patch (to be ported)

This should now be fixed in head, it should be merged with the rest of #962330.

anarcat’s picture

Status: Patch (to be ported) » Fixed

this was merged in stable.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

  • Commit 2364193 on 6.x-2.x, 7.x-3.x, dev-ssl-ip-allocation-refactor, dev-sni, dev-helmo-3.x by anarcat:
    #962338 - make sure the client name is unique
    

  • Commit 2364193 on 6.x-2.x, 7.x-3.x, dev-ssl-ip-allocation-refactor, dev-sni, dev-helmo-3.x by anarcat:
    #962338 - make sure the client name is unique