Check box & Radio button data in New User Notification

[man-O-media]

I have configured the Administrative: New User Notification email function to send new registrations to the membership manager.

I have a couple of check boxes in my registration form and while I know that seeing a "1" as the data means true, I really question if the "membership" manager or who ever may be helping will get it.

I presume I can't call any php code so is there some way to get check boxes, radio buttons and the like to echo as true/false, yes/no, etc.?

And directly related to that, is there some way to gain access to the true/false MailChimp data?
The result of the Double Opt-In Checkbox is stored at MailChimp but it would be nice for the membership folks to know whether a particular user has said yes or no to receiving email.


Thanks, DP

[Jason Caldwell]

I have configured the Administrative: New User Notification email function to send new registrations to the membership manager.

I have a couple of check boxes in my registration form and while I know that seeing a "1" as the data means true, I really question if the "membership" manager or who ever may be helping will get it.

I presume I can't call any php code so is there some way to get check boxes, radio buttons and the like to echo as true/false, yes/no, etc.?

Sorry, not exactly. What you could do though, is change your Custom Registration Field configuration, so that instead of using checkboxes, you could use a Select ( drop-down ). This allows you to supply the exact values that you want returned, by configuring a list of options that will be available in the drop-down. For instance, true or false. See: s2Member -> General Options -> Custom Registration Fields.

And directly related to that, is there some way to gain access to the true/false MailChimp data?
The result of the Double Opt-In Checkbox is stored at MailChimp but it would be nice for the membership folks to know whether a particular user has said yes or no to receiving email.

Not yet, but this IS something we're working on.
Stick with MailChimp for now, we'll be adding this feature soon.

[man-O-media]

Sorry, not exactly. What you could do though, is change your Custom Registration Field configuration, so that instead of using checkboxes, you could use a Select ( drop-down ). This allows you to supply the exact values that you want returned, by configuring a list of options that will be available in the drop-down. For instance, true or false. See: s2Member -> General Options -> Custom Registration Fields.

Hmmm, I guess so...
Drop downs are not quite as user friendly but yea, that could work.

A question though... I know if you rename a custom field, any data associated with the old field name is lost.
If I change the field type I presume that will be the case as well?

As far as MailChimp goes, I'm happy enough with the situation so yea, I will be here to see any improvements.


DP

[Jason Caldwell]

If I change the field type I presume that will be the case as well?

As long as you don't change the Unique ID of that field, and you only change the type, no data will be lost. However, in your Dashboard, the new drop down may default to the first value when you edit a User, so that is something that you may have to work around. In other words, if the drop down is configured with values other than 1 or 0, the drop down menu will not match the existing value of a current User, and would default to the first value that is available in the drop down. So just to be aware of this. If you edit a User manually, or they edit their profile, the data may *appear* to be lost, although it's not, at least, not internally. Sorry, that's the best I can do right now.

[man-O-media]

Yea, OK... Thats not so bad.
There are not that many users at this point so manually cleaning up the data will not be so bad. And would certainly be easier to do having not lost the old data.


Thanks, DP

[Cristián Lávaque]

If you have s2Member Pro, exporting the users before changing the custom fields may be a good idea, you can then re-import them with the new field. Should be simpler than editing each one manually in their profiles.