wp_create_user & username_exists

[Rich Pedley]

This may be a silly question, and I may end up not even using it, but...

I have a scenario (shopping cart) where I want to automate the user creation as much as possible. Now I know how to do this using a simple wp_create_user. But this calls username_exists to check to see if that name already exists, and rightly so. Now I realise that I may get the occasional error with a duplicate email address, that I can cope with. But what I'd like is for a way of changing the username if it already exists automagically behind the scenes, with no further user intervention.

eg. username Rich exists, so use Rich47 sort of thing.

What is the easiest way of doing this with minimal db calls?

Or should I forget it and add a field for them to fill in and keep amending until they find a free name? (which is what I'm trying to avoid).

Currently I'm thinking of creating an array of possible names, and then trying to construct a single query that checks for all of them and returns which one(s) are available for use. This check would be run prior to wp_create_user or via the pre_user_login filter.

[chipbennett]

This may be a silly question, and I may end up not even using it, but...

I have a scenario (shopping cart) where I want to automate the user creation as much as possible. Now I know how to do this using a simple wp_create_user. But this calls username_exists to check to see if that name already exists, and rightly so. Now I realise that I may get the occasional error with a duplicate email address, that I can cope with. But what I'd like is for a way of changing the username if it already exists automagically behind the scenes, with no further user intervention.

eg. username Rich exists, so use Rich47 sort of thing.

What is the easiest way of doing this with minimal db calls?

Or should I forget it and add a field for them to fill in and keep amending until they find a free name? (which is what I'm trying to avoid).

Currently I'm thinking of creating an array of possible names, and then trying to construct a single query that checks for all of them and returns which one(s) are available for use. This check would be run prior to wp_create_user or via the pre_user_login filter.

Why not do it via javascript, and query the database when the appropriate form field (e.g. "Username") loses focus? Then, display feedback next to the form field, based on the query response (e.g. "Username Avaliable" or "Username Not Avaliable. Please try another.").

[Rich Pedley]

Because I hate javascript?

Actually having posted I asked my significant other and she simply said why not just get the next user id and append that... That should ensure they are all unique.

moral: ask the wife before posting.

[chipbennett]

Because I hate javascript?

Actually, in-line form data-entry validation is good for user experience - but, personal preference/to each his own, and all that.

Actually having posted I asked my significant other and she simply said why not just get the next user id and append that... That should ensure they are all unique.

moral: ask the wife before posting.

Always a wise moral!

[Rich Pedley]

Actually, in-line form data-entry validation is good for user experience - but, personal preference/to each his own, and all that.

I haven't done testing to see how accessible it is though. If implemented correctly I'm sure it can be though.