Blesta Addons Posted April 29, 2018 Report Posted April 29, 2018 might we can say in a future release a new fields in contacts for age(birthday) and gender ? some companies need this two data for some interne stats, and i really see this a nice new fields to add, it mandatory of course, but we can force client to fill them . activa and Michael 1 1 Quote
Michael Posted April 30, 2018 Report Posted April 30, 2018 +5 I had a custom date of birth but nice to get it as default. activa 1 Quote
Paul Posted April 30, 2018 Report Posted April 30, 2018 You can create custom client fields, but it looks like they only apply to the primary contact (client contact) and not other contacts. Is this a request to make custom client fields work for other contacts also, or specifically to add these as standard fields? Quote
activa Posted April 30, 2018 Report Posted April 30, 2018 +1 for gender . Is a great criteria select stats for iur services. In custom fields the dropdown value select are not translated as the main field and this make our frontend not fully multi languages. I prefer to see them in the standard field and defaut to optional . Quote
Blesta Addons Posted May 1, 2018 Author Report Posted May 1, 2018 17 hours ago, Paul said: You can create custom client fields, but it looks like they only apply to the primary contact (client contact) and not other contacts. Is this a request to make custom client fields work for other contacts also, or specifically to add these as standard fields? Personally i prefer to be in the core, and can be for the primary contact or additional contacts, this will make blesta support COPPA laws, for gender field is needed for some industry law firms or any other service provider for social issues. 11 hours ago, activa said: In custom fields the dropdown value select are not translated as the main field and this make our frontend not fully multi languages. this issue i have already talked about it here Michael 1 Quote
Jonathan Posted May 1, 2018 Report Posted May 1, 2018 If such fields were added to core as opposed to using custom fields it should also be possible to disable them completely as not everyone will want to use these fields or even allow customers to fill them in. Beav, BeZazz and Michael 3 Quote
Michael Posted May 1, 2018 Report Posted May 1, 2018 4 hours ago, Jonathan said: If such fields were added to core as opposed to using custom fields it should also be possible to disable them completely as not everyone will want to use these fields or even allow customers to fill them in. Quite like the current system, first name etc. Quote
Paul Posted May 1, 2018 Report Posted May 1, 2018 4 hours ago, Jonathan said: If such fields were added to core as opposed to using custom fields it should also be possible to disable them completely as not everyone will want to use these fields or even allow customers to fill them in. That's the thing.. which makes this 2 feature requests. New fields + ability to hide/disable fields. Right now you can set which are required fields, though First, Last, Email is always required, we'd have to add another option for whether to show the field at all. I think it'd be a good feature, people sure ask enough about removing fields, but it's two feature requests. Quote
Paul Posted May 1, 2018 Report Posted May 1, 2018 Also, separately, I don't know if we really want to get into the gender debate. ?? Quote
Jonathan Posted May 1, 2018 Report Posted May 1, 2018 3 minutes ago, Paul said: Also, separately, I don't know if we really want to get into the gender debate. ?? That's pretty much my point for having the ability to completely disable it. As soon as it's there people can/will get offended. If it's not there, everyone is equal. Quote
Paul Posted May 1, 2018 Report Posted May 1, 2018 2 minutes ago, Jonathan said: That's pretty much my point for having the ability to completely disable it. As soon as it's there people can/will get offended. If it's not there, everyone is equal. Maybe it can just be a write-in, I dunno.. but I agree, both DOB and gender fields disabled out of the box. Blesta Addons 1 Quote
Blesta Addons Posted May 2, 2018 Author Report Posted May 2, 2018 hoep i can see them soon, as i have project client that require them both and i don't want to work with custom fields then revert to core one Quote
activa Posted May 8, 2018 Report Posted May 8, 2018 Adding them and make them disabled is better than they not exist at all. My custom case require gender field more than adress2 field . Quote
Paul Posted May 8, 2018 Report Posted May 8, 2018 14 hours ago, activa said: Adding them and make them disabled is better than they not exist at all. My custom case require gender field more than adress2 field . Why doesn't a custom client field work for you? For language, you can add your own language definitions to the custom language file and use a definition here for the name instead. Quote
Blesta Addons Posted May 8, 2018 Author Report Posted May 8, 2018 17 minutes ago, Paul said: Why doesn't a custom client field work for you? For language, you can add your own language definitions to the custom language file and use a definition here for the name instead. from my case i use, but the only issue i have that the select value is not in traslate mode like the field value . in your case, Please Select will not be translated when the client change language, instead of gender we can put it in language file and make it translatable . PauloV 1 Quote
Paul Posted May 9, 2018 Report Posted May 9, 2018 23 hours ago, Blesta Addons said: from my case i use, but the only issue i have that the select value is not in traslate mode like the field value . in your case, Please Select will not be translated when the client change language, instead of gender we can put it in language file and make it translatable . Maybe the fields, like "Option Name" here should be able to be language definitions. If the fields could be translated, do you still think we should add Birthday and Gender? This would allow any fields to be added, and fully translatable. I think this is better than adding the fields into the core. Someone else will ask for SSN, hair color, or whether the person owns a dog, and custom client fields were intended to allow people to add anything they want. Beav and Jonathan 2 Quote
Blesta Addons Posted May 10, 2018 Author Report Posted May 10, 2018 13 hours ago, Paul said: Maybe the fields, like "Option Name" here should be able to be language definitions. If the fields could be translated, do you still think we should add Birthday and Gender? This would allow any fields to be added, and fully translatable. I think this is better than adding the fields into the core. Someone else will ask for SSN, hair color, or whether the person owns a dog, and custom client fields were intended to allow people to add anything they want. For me translated field value also good option, but not sure some fields are universal use like gender ect ... others option that will be rock the custom fields are ; - Option to set Order (1, 2 , ect ...) - Option to set class or attributes (class, id, data-xxx, ect ... ) what is really good option to add is the user avatar Quote
activa Posted May 14, 2018 Report Posted May 14, 2018 And what about client group. We should add the custom field for every group !!! Quote
Blesta Addons Posted May 21, 2018 Author Report Posted May 21, 2018 why the read only field are applied to signup also? is should only for edit profile Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.