Closed (fixed)
Project:
Hosting
Version:
5.x-0.1-beta1
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
17 Nov 2008 at 07:59 UTC
Updated:
16 Dec 2008 at 02:41 UTC
An extra field on users which associates them with clients in an autocomplete field, ie: so each user has one client, and each client has one or more users. There needs to be an admin permission to be able to change it
| Comment | File | Size | Author |
|---|---|---|---|
| hosting.nov_.17.xiong_.patch | 4.61 KB | xiong |
Comments
Comment #1
adrian commentedThis has some issues.
Firstly, there should be a user for every client, and a client for every user.
When a new client is created, a new user account should be created and a welcome mail sent to the user.
However, when importing hundreds of sites / clients, the welcome mails will time out the process(this also needs to happen in the update_N function.)
So we need a mail queue of some form.
Also, the update function is in the wrong format (doesn't return an array or use update_sql)
I'm thinking this patch is only going in after the 0.1 release.
Comment #2
adrian commentedTill after 0.1
Comment #3
anarcat commentedcleanup title.
we need this. :)
Comment #4
anarcat commentedI should also add here that the relation between clients and users should be "qualified" There are different "types" of "users" that have access to the the "client". On the top of my head I can already think of those:
* tech
* billing
* owner
Those can be all the same person, but it's important to have different types of contact for the site so that we contact the right person for various issues (billing is very different from tech issues: the first will receive the bills, the second one maintenance announcements and the like).
I also think that users can have access to multiple clients too. So the relation is actually many to many, and typed. Note that this is also related to http://drupal.org/node/336068: that issue is an excellent example of use for the tech contact. The mail should be sent to the tech contact.
Comment #5
adrian commentedThe basic implimentation of this has been committed, including node_access, so nodes that you do not have a business seeing are hidden.
Comment #6
anarcat commentedThis is a hosting issue.