Issues with user registration from administrative console

[Alexander Obuhovich]

There are 2 configuration options:

1. automatically generate password for new users
2. use email as login

First option doesn't work in administrative console at all and I still see password fields and I can use them. Of course none email is sent to user, with it's auto-generated password.

Second option will work as expected, but it will always overwrite Login field contents with Email field value. In administrative console I have both fields editable, but I think that Login field should not be available for editing or totally hidden in this case.

In conclusion I think that user registration form in administrative console should work same way as on front-end.



--
Best Regards,

http://www.in-portal.com
http://www.alex-time.com

[Phil -- wbtc.fr --]

I agree, but login field should be greyed, and not hidden (could be confusing for average admin ^^)

2010/6/8 Alexander Obuhovich <aik....@gmail.com>

--
You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
To post to this group, send email to in-port...@googlegroups.com.
To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/in-portal-bugs?hl=en.

[Alexander Obuhovich]

I'm ok with login field disabled, that's why I'm asking, since I'm not pretty sure about it too.

[Alexander Obuhovich]

Dmitry, what's you thoughts on this?

[Dmitry Andrejev]

Hi guys,

I think we should:

1. Still allow to enter the Password in Admin even if in Admin it's auto-generated, but I would add a JS button Generate password next to the password field (and i will auto populate in repeat password if used)

2. I would disable Login field, but would show changes in there as Admin types the email so there is NO confusion why it's this way and Admin sees that Login basically will be the same as Email, but can't change it.

DA.

[Alexander Obuhovich]

What about emails, that are sent to user being created while auto-generate password option is in use?

[Dmitry V. Andrejev]

What if we have a checkbox (available only when that option is selected) which is checked by default and we'll be sending passwords to the user?


DA.

-- 
With best regards,

Dmitry V. Andrejev

[Alexander Obuhovich]

Why we need to complicate things in administrative console? No options, just work as simple as on front-end. I will generate password before page is displayed, since I can't place anything in password fields later.

[Dmitry Andrejev]

1. I can't agree here. It's a bit confusing if I click Add User and see some password there especially if I am not a ROOT who setup the system to auto-generate the passwords.

I think we should have that "Generate" button in JS which will do both - generate the pass and put it in both Password and Repeat password. I say we show it always - see attached screen.

2. Have a check-box which would email user a password and it can be always there too, but will be pre-checked if current setting indicates that password is generated and email automatically.

The way I see it - the problem with doing in Admin exactly as we do in Front won't do any good from the Interface point - only additional complexity.

DA.

[Phil -- wbtc.fr --]

I don't see the point being an administrator and having an auto-password-generation system. The custom can do it by himself following "lost password" process, and an administrator would enter directly a new password prompted by user, don't you think so?

2010/6/11 Dmitry Andrejev <dand...@gmail.com>

[Dmitry Andrejev]

Point is simple:

Task: Phil, please create a new User for a new System Admin or Regular user and email him the details.

How many steps you'll need to do? At least 3 (plus all in separate places)

1. Think of the password and put it in

2. Create a User

3. Email the User his details.

If we do what I suggest we can do this in 1 simple step from the same Add User step and user will get his Username/Password sent by In-Portal.

Again, the functionality will be useful NOT only when we have auto-generate password enabled for the Front, but in all cases.

I hope it explains things a bit better.

DA.

[Phil -- wbtc.fr --]

Hi Dmitry,

I clearly understand your point and I agree, if the button create a temporary password AND e-mail user the password AND confirm the sending AND close the user's file. Avoiding any supplementary clicks is a very good idea, and I agree in this way :)

Phil.

2010/6/12 Dmitry Andrejev <dand...@gmail.com>

[Alexander Obuhovich]

I see your point now, and I agree too.

[Dmitry Andrejev]

Great!

I guess we are ready for a task here?

DA.

[Alexander Obuhovich]

Yes.

[Dmitry Andrejev]

New task has been filed:

778: Improvements to Create User & Admin form in Admin

http://tracker.in-portal.org/view.php?id=778

I have improved specs a bit so it's more consistent with current system.

DA.