Boolean Custom Field default value

Hello,

I had created myself a user custom filed by using your settings, and wasn't able to reproduce and see your issue.
Can you provide a step by step in order to allow us to reproduce the context, don't forget to detailed everything and precise where you see a default Boolean set by default to "no"

Awaiting news from you
Regards

Hi,

It's actually not a problem of the fact that the custom field is a boolean custom field. you would have the same issue with any kind of custom user field with a default value.
That's because you create the user from the backend and on the backend form to create the user, these custom user fields don't show up so their default value cannot be initialized.
However, if you test again by creating a user from the HikaShop registration form on the frontend, you shouldn't have the problem as you will see the custom fields on the registration form.
I suppose that it is why Philippe didn't had the problem since he must have tried to reproduce by creating a user from the frontend, since that's what 99% of the merchants care about.
Now we could potentially add the capability to set the default value when creating the user from the backend but that's not something that easy to add.

Hi,

You mean even when you register through the HikaShop registration form ? (I'm not talking about joomla's since the fields don't appear on Joomla's registration form either)

Hi,

And are you sure that you turned on the "frontend" display setting of your custom user fields so that they can display on the frontend ? Otherwise, they will be ignored like when you create a user from the frontend.

Hello,

Nicolas wrote :

And are you sure that you turned on the "frontend" display setting of your custom user fields so that they can display on the frontend ?

And regarding your screenshot, the field "invite to review" IS displayed in the front-end, we can see the green checkmark on the column just after the ordering column.

So the field is displayed in the front-end because it is configured as well.
But your screenshot is showing the edition of the profile ; not the registration. Which mean that we can't deduce anything from that except that when you edit a profile, it load the current saved data.

For that part, Nicolas already gave you the answer :

That's because you create the user from the backend and on the backend form to create the user, these custom user fields don't show up so their default value cannot be initialized.

For the registration, since we do not have any details about the issue (nor the kind of registration you're using ; because it might be something which is not the HikaShop registration form, so something which might not handle the HikaShop fields).

Afterwards, regarding the newsletter ; I'm afraid that is not related to HikaShop stuff but to your newsletter component.
Please understand that we do only provide support for our components.

Regards,

Hi,

We're not able to reproduce the problem on our end.
I wanted to look at the issue on your website, however, I don't see the custom field on your checkout registration form:
monosnap.com/file/AoHevxBBQGGzQTMph1RLDd8HMEScbJ
And when I try to access the registration form page, I see the registration form page of Joomla, not HikaShop's, as you didn't activate the Redirect Joomla registration to HikaShop plugin via the Joomla plugins manager:
monosnap.com/file/8OxRfcNmH8YkGM9B9OgT0pI5G6015N

Note that the default value of a custom field is the default value used to initialize the custom field when it is displayed in a form.
If you create the element through another mean than a form where the custom field is displayed, then the default value won't be set.
That goes for users but also for any other custom field.
For example, if you have a custom order field with a default value but you click on the "new" button of the orders listing in the backend, the default value won't be set as the custom field won't display through that process. It would however if you configure the custom field to display through the checkout (which is usually the case for custom order fields).
So if you create the user through the Joomla user manager in the backend, through the joomla user registration form of the frontend, or even if you created the user account through the HikaShop registration form BEFORE you configured the custom field or its default value, then you won't see the default value when you edit the user profile.

Hi,

I checked your settings.
All your custom user fields have the "frontend" setting turned off.
So the custom user fields are not displayed on the HikaShop registration forms on the frontend and thus their value is not initialized, as if you were registering through the Joomla registration form.
You need to activate the custom fields and if you don't want to display them to the user, you can use custom CSS to hide them.
Alternatively, do no use a "boolean" type but a radio type. Then, when you add the yes / no values to the custom field values list, make sure that you leave the "value" input empty for the default value you want. That way, even if the custom field is not displayed on the form, the default value will correspond to the field not being used and it will display properly on your user details page in the backend.