When the owner invites a user, the owner must set a username for that user

[Christopher Adams]

Each private profile will have a button that lets the Owner invite that People to the site.

At this point the owner must choose a username for the user. When the owner pushes Invite, a text field labeled "Username:" will appear. The owner must enter a unique username in that field before he or she can publish the profile.

Essential:

The form must constrain the allowed username:

* Only alphanumeric characters [A-Z] [a-z] [0-9].
* Usernames cannot be more than 25 characters. (Up for debate. Twitter is 15.).

Extra:

If the username is not unique or the right format, the owner should see a meaningful error and be able to choose a new name.

If the user navigates away from the page before choosing a username, then nothing should happen. The invitation should not go through. (Please test this!)

Ideally we ewant:

1) Owner imports user
    e.g.: Jon Phillips, http://twitter.com/rejon

2) Owner invites user to the site
    There will be some kind of invite button on the profile page

3) Owner is asked to choose username for the user
    e.g.: rejon

4) PPL checks the username is valid

5) PPL sends an email to the user with an invite code

6) Person now has a permalink
    e.g.: [root]/people/rejon

Is (6) possible or do we have to accept [root]/people/((userid))/((username))

?

[Brad Phillips (brad-bradphillips)]

Bassel, are there aiki functions that can be called to place limits on an edit form text entry? I know of methods like ":unique" that can be used in the "Databases & Forms" Section to ensure no 2 entries are alike or ":md5", but I haven't seen any examples of text limits based on length or type.

If nothing like this exists in aiki, what is best method to solve? Javascript pre-submit checking?

[Christopher Adams (christopheradams)]

Ideally we want:

1) Owner imports user
    e.g.: Jon Phillips, http://twitter.com/rejon

2) Owner makes user public
    Pushes the [lock] icon

3) Owner is asked to choose username for the user
    e.g.: rejon

4) PPL checks the username is valid

5) Person now has a permalink derived from username
    e.g.: [root]/people/rejon

[Christopher Adams (christopheradams)]

Let's modify this bug to achieve the following:

Change step 2)

2) Owner invites user to the site
    There will be some kind of invite button on the profile page

add step 4 a)

4 a) PPL sends an email to the user with an invite code

Is 5 still possible or can we only get:

[root]/people/((userid))/((username))

?

[Christopher Adams (christopheradams)]

Changing bug description and pushing back to 0.3

[Christopher Adams (christopheradams)]

I'm thinking now that we want to just let the Person choose his or her username. Otherwise it's too much work for the owners who have hundreds of contacts to invite.