You can include a captcha field in a pdb_record form by explicitly naming all the fields you want shown in that form, using the “fields” attribute:
[pdb_record fields="first_name,last_name,email,captcha" ]
Thank you for your prompt response, that does indeed work.
However, I was hoping since I was using groups for each of these pages, that if I assigned the CAPTCHA field the same group as the others on this page, that would work the same.
CAPTCHA is included in the “contract” group and my include looks like this:
[pdb_record template=”final” groups=”contract” action=”application-received” submit_button=”Submit Application”]
I apologize that I didn’t include that in my initial posting.
I was hoping that I wouldn’t have to list all of the fields in my “contract” group for this to work – but I will if that is the way to do it.
Incidentally, I also tried doing:
[pdb_record template=”final” groups=”contract” fields=”captcha” action=”application-received” submit_button=”Submit Application”]
And, not surprisingly, just the CAPTCHA showed up without the contract group.
Also, when I included the CAPTCHA in the group on the initial pdb-signup page, that worked fine. On that page I have:
[pdb_signup groups=”main,personal” action=”application-page-2″ submit_button=”Next”]
When I assigned the CAPTCHA field to the “personal” group, it showed up correctly on the page.
The CAPTCHA was designed to be included in the signup form, so making it show up on the “record” form requires the fields to be explicitly listed (which overrides default field behavior)…at least for now. It’s a good idea to allow simply naming the group to override the defaults, so I’m adding this to the new features list.
Ok. I figured it was a design issue. I will name the fields explicitly on that page.
I appreciate your help and the great plugin.
Thanks!
