Developer forum

Forum » Feature requests » Some thoughts about users

Some thoughts about users

Dmitrij Jazel
Reply

First one would be:

Allow possibility to use AccessUser First Name and AccessUser Last Name, instead of current AccessUser Name? Allow it in the settings user settings maybe, so one could switch between one or another at any time.

 

Another one would be:

Allow possibility to user email as username.

In simmilar way, in user settings, just add a checkbox that could say, use AccessUserEmail email as AccessUserUserName :-)

 

Cheers,

Dmitrij

 

 


Replies

 
Asger Munkholm Højfeldt
Reply

Hi - Please use custom fields to achieve the feature of a separate first and last name.

//Asger

 
Dmitrij Jazel
Reply

Hi Asger,

Thanks for advice, but if we compare not just a user field, but The name of the user - this field actually has some more importance in CMS both in front-end and in back-end. By this I can give a very simple example:

When CMS admin is logging in into the Admin panel, and than goes to User management, and than he seas - the Name of the user with his email. He does not see any custom field, instead of the actual name.

I can bring some more examples, of why it would be so much more convenient to have actually 2 fields.

Like why does Checkout has a AccessUserSurname is available - that actually is a last name. Do I have to extra load my templates, and user more time and energy on managing "already complicated enough and slow enough behind the scenes javascript" in order to have some functionality that is used in ~95% of nearly all the cases, with normal user related templates, and user management of some sort.

It's good if it is my projects that I set-up right from the start. But what if I take over somes, that's something to think about. That is why it is in Feature request. :-)

//Dmitrij

 
Imar Spaanjaars Dynamicweb Employee
Imar Spaanjaars
Reply

+1 Having first name and last name fields out of the box makes a lot of sense!

Imar

 
Remi Muller
Reply

"+1 Having first name and last name fields out of the box makes a lot of sense!"

Indeed!

Do not forget about fields: "Title", "Middle name", "House number", "House number suffix".

These fields should also be mirrored to the order object for user and address fields.

DW it is also important for the backend that these fields are placed on logical positions in the UI.
- UI for editing a user

- UI for viewing/editing an order. (it is ugly when we have this in custom fields at the bottom)

 

 
Anders Ebdrup
Reply

And a +1 from me :-)

 
Asger Munkholm Højfeldt
Reply

Hi guys - ok I see where you are heading. 

New format would be like:

  • Name
  • Title
  • First Name
  • Middel Name
  • Last Name
  • Email
  • Address
  • Address 2
  • House Number
  • Zip
  • City
  • State/Region
  • Country

Would that work for you?

 
Remi Muller
Reply
  • Name
  • Title
  • First Name
  • Middel Name
  • Last Name
  • Gender
  • Email
  • Address
  • Address 2
  • House Number
  • House Number suffix
  • Zip
  • City
  • State/Region
  • Country

This would work even better ;)

 

We are also seeing some backoffices where housenumber like '1a' is split over housenumber(1) and a suffix(a) field.

Gender field(male/female) is also convenient.

 

Do not forget to add these new fields to the Global:Extranet template tags.

 

 
Dmitrij Jazel
Reply

Hello everyone,

Regarding fields, I think Middle, Last name and Gender is a good thing to include. It would be really great if those fields would be automatically mirrored in Extranet User management module and Checkout information step.

 

Regarding House number suffix:

Isn't having a dedicated field for a "suffix" and and separate house number, is a bit too much? You should be able to use custom fields for this. There are many different variations and ways how users are stored in many different countries arround the world. You cannot have 1 perfect solution to solve all that.

Keep in mind a validation, and other places in CMS Core where you have to assure that all that information is concurrent and treated in the way it should be. I would rather have more better/powerfull Razor possibilities in DW and better CMS overal rather than having House suffix field included.

Maybe user backend is a bit "ugly" as Remi said it out in the top.

Maybe having a possibility to organise (sort / build) the user detail overview (in the backend) would be a great solution. So that you could create a custom field, move it wherever you like it (between whatever row you like) not just keep it in the buttom box, but have an subtle index aside the field that could incicate that this is a custom field.

 

Having a possibility to mirror custom field in Extranet User management and Checkout Information step just by using system name would be cool. Rather than looping through the list of all custom fields first, than copying value with JS etc...

 

 
Nuno Aguiar
Reply

Hi,

 

A (custom) field we use a lot is Company/Private user. We need this field (radio) to latter change profile layouts and use custom development due to EU business laws regarding VAT's and/or prices.

 

If by default we also had this field, would be great.

 

Nuno

 
Remi Muller
Reply

Is this planned for 8.5 or 8.6?

 
Asger Munkholm Højfeldt
Reply

Will be released in 8.5 - August 26th. 

//Asger

 
George Nelzo Pereira
Reply

Hi... About this...
It's possible to Add the House Number in Address structure?
Will be possible to edit and Add new address in the same structure.

 

George Nelzo

 
Dmitrij Jazel
Reply

Hello George, 

What do you mean by saying "Address structure?"

After the 8.5 release, House Number has it's own field in the User properties.

If you don't have it, than you probably using pre 8.5 application, maybe?

 

/Dmitrij