I contacted ACF about this and they replied like this:
I’m afraid you need to ask Formidable Forms support if there’s any way you can set the receiver email address by using a hook. In that hook, you can get the email address by using this code:
$email = get_field(‘char_email’, $post_id);
Where $post_id is the post ID of the current custom post (charity).
I think you can also set the form field visibility, but I’m not sure about the security, though. I’ve attached a screenshot for your reference.
I don’t know if that helps anybody understand what I want / need to do?
In simple terms, if anybody reads this, I’m trying to do this:
I have several custom post types, each one of which is submitted front-end by formidable pro, with the data being stored in custom fields using ACF pro. Each post is used to create a sort of profile page for a business.
On each single post page there is all the relevant data, plus an embedded contact form. The contact form uses formidable forms. However, the contact form doesn’t see the email address I need it to be sent to.
ACF (who obviously have no connection with the forms) advised me thus :
I’m afraid you need to ask Formidable Forms support if there’s any way you can set the receiver email address by using a hook. In that hook, you can get the email address by using this code:
$email = get_field(‘char_email’, $post_id);
Where $post_id is the post ID of the current custom post (charity).
Can anybody tell me how to do this?
Thanks
Hi Dawn,
Can you please log in with a paid account and post in our help desk if you’d like help from our team on this? Thanks!
https://formidablepro.com/new-topic/
I already tried that. I paid $39 or something like that, but apparently I have to pay $80 if I want to be able to post a support ticket, which is why I posted here. There’s nothing relating to this as far as I can see in your kb.
Never mind. I found the solution myself. Given that it only required you to say ‘add an email field to the contact form, choose author email address as the default value and then save’, I somewhat amazed that you require someone to pay for paid help (having already paid for the plugin) in order to explain how to do something that you seem to have neglected to mention in your documentation. Seems exceptionally mercenary.
