This is not hard, there are several ways to do this. One approach is to put the email in a private group: this is a group that has “public” unchecked. Fields in the group won’t be shown by [pdb_single] shortcodes.
To make the field show up in the signup form, you need to use the “fields” attribute of the signup shortcode to make it show:
[pdb_signup fields=”first_name,last_name,email”]
To make it show up in the record edit forms, you can use the groups attribute to tell it which groups to show:
[pdb_record groups=”main,address,personal”]
Ok, that seems easy enough, thank you! Will I have to list every field with the signup shortcode? Or just the “private” one?
When you use the “fields” attribute, you have to list all of the fields you want shown.
I tried using the [signup] shortcode with “fields” attribute and it still did not display the email field even though it was listed. In this instance “email” was in a group that was NOT public.
I also tried using [pdb_single groups=”main”] while the email address was in a different group, but it still displayed both groups, including the email field. In this instance “email” was in a PUBLIC group.
This works, I guess make sure the syntax is correct, no spaces around the =
When using “groups” in the signup form, the groups must be public, the fields must be in the named group, and only fields with “signup” checked will show up.
When using the “fields” attribute, it will show all the named fields without regard to the group settings or the “signup” checkbox.
Ok, so I ended up just using “fields=” on the view page and that did the trick. Didn’t use “groups=” anywhere.
Thanks, as always, for your assistance! I wish all plug-in authors were this responsive