I could really do with the mailing list having separate boxes for first and last name ... I can't see any way of doing that myself?
What are the chances of a quick update??
Alternatively, I assume I could use Umbraco Member records instead? Only problem with that, is I can't then use the custom field feature! (Sorry thinking and typing at the same time!!).
At the moment the "name" is just a singel text-field where you could put either just the first name or the whole name. I haven't seen any other request about this but why do you need them to be seperat? Using a custom provider won't help you becuse it uses the "MemberObject.Text"property which contains the whole name. But with the new upcomming version you could use member section and create your own "RenderTask" that talks to the member-api and gets first/last name.
If this is something other parts of the community would like to see it could be included in up comming updates.
Could you explain why this is important to you so that I can have that in mind when planning the work.
It's mainly in case of newsletter personalisation - if there is only one box people may put "Gordon" or "Gordon Saxby". When you then put the "name" into a newsletter you can't be sure that you are addressing them by their first name only.
If it was possible to put your own macros in, then I could write some code to check / chop up the name.
It's not a killer problem, just that it would be nice to have the option.:-)
I see. It's a good point, at the moment you could call the textbox label "First name" and pray that the users only adds there first name. But I'll keep this in mind and I'll put it in the backlog.
And yes in the future you could add your own merge field. Ie [firstname] and then run som code against the name-variable to check if it's likely to be a valid first name, its called Render Tasks and will be included in the next major release.
Hello,
i vote for separate first and last name. Because in czech we have to generate salutation for example: Michal needs to be transformed to Michale. So we have to know what is first and last name.
I also suggest to add some custom data field to person. Because of some CRM stuff like interest etc. I can use it for storing first and last name also. :-)
First and Last name
I could really do with the mailing list having separate boxes for first and last name ... I can't see any way of doing that myself?
What are the chances of a quick update??
Alternatively, I assume I could use Umbraco Member records instead? Only problem with that, is I can't then use the custom field feature! (Sorry thinking and typing at the same time!!).
Oh well, some more ideas for the future ;-)
Hi Gordon!
At the moment the "name" is just a singel text-field where you could put either just the first name or the whole name. I haven't seen any other request about this but why do you need them to be seperat? Using a custom provider won't help you becuse it uses the "MemberObject.Text"property which contains the whole name. But with the new upcomming version you could use member section and create your own "RenderTask" that talks to the member-api and gets first/last name.
If this is something other parts of the community would like to see it could be included in up comming updates.
Could you explain why this is important to you so that I can have that in mind when planning the work.
It's mainly in case of newsletter personalisation - if there is only one box people may put "Gordon" or "Gordon Saxby". When you then put the "name" into a newsletter you can't be sure that you are addressing them by their first name only.
If it was possible to put your own macros in, then I could write some code to check / chop up the name.
It's not a killer problem, just that it would be nice to have the option.:-)
I see. It's a good point, at the moment you could call the textbox label "First name" and pray that the users only adds there first name. But I'll keep this in mind and I'll put it in the backlog.
And yes in the future you could add your own merge field. Ie [firstname] and then run som code against the name-variable to check if it's likely to be a valid first name, its called Render Tasks and will be included in the next major release.
Hello, i vote for separate first and last name. Because in czech we have to generate salutation for example: Michal needs to be transformed to Michale. So we have to know what is first and last name.
I also suggest to add some custom data field to person. Because of some CRM stuff like interest etc. I can use it for storing first and last name also. :-)
M.
is working on a reply...