Disabling those older fields sounds fine to me. Will you also disable the newer profile fields by default?

I presume that you can make any of these profile fields required at registration, right? Also, will the user be able to delete the predefined profile fields or just disable them (I'm in favor of not allowing them to be deleted).

Pony99CA wrote:Disabling those older fields sounds fine to me. Will you also disable the newer profile fields by default?

I presume that you can make any of these profile fields required at registration, right? Also, will the user be able to delete the predefined profile fields or just disable them (I'm in favor of not allowing them to be deleted).

Steve

+1 for not allowing to delete built-in profile fields - sth similar to the group management.

Pony99CA wrote:Disabling those older fields sounds fine to me. Will you also disable the newer profile fields by default?

I don't see a reason, to disable stuff that is going to be used. So no, they will be active by default

Pony99CA wrote:I presume that you can make any of these profile fields required at registration, right?
Also, will the user be able to delete the predefined profile fields or just disable them (I'm in favor of not allowing them to be deleted).

Like with current profile fields the admin has the option to require them anywhere, hide them, disable them and delete them.
We will also not stop anyone from deleting them. Why would we want to prevent it? If an admin decides he does not need these fields, he can delete them to make the db a little smaller and cleaner.

If an admin decided he accidently deleted one of them, we can add a module to the SupportToolKit to readd profile fields easily.

Pony99CA wrote:I presume that you can make any of these profile fields required at registration, right?
Also, will the user be able to delete the predefined profile fields or just disable them (I'm in favor of not allowing them to be deleted).

Like with current profile fields the admin has the option to require them anywhere, hide them, disable them and delete them.
We will also not stop anyone from deleting them. Why would we want to prevent it? If an admin decides he does not need these fields, he can delete them to make the db a little smaller and cleaner.

I agree, if an admin does not want certain profile fields, they should have the option to delete them.