The user had three custom post types (cpt1, cpt2, cpt3) and a custom field group called "cf" assigned to each of them. They wanted to use the same form for all custom post types to submit data from the frontend. However, Toolset only allows a separate form for each custom post type.
Solution:
-Create separate forms for each custom post type (cpt1, cpt2, cpt3).
- Go to Toolset > Content Templates and create a new Content Template, without assigning it to any post type (e.g., name it "conditional-logic").
- In the Content Template, use Conditional Blocks and Forms Blocks to create the desired conditions for each custom post type. For example:
[wpv-conditional if="( '[wpv-post-type]' eq 'cpt1' )"]
[shortcode for the form for cpt1]
[/wpv-conditional]
[wpv-conditional if="( '[wpv-post-type]' eq 'cpt2' )"]
[shortcode for the form for cpt2]
[/wpv-conditional]
[wpv-conditional if="( '[wpv-post-type]' eq 'cpt3
[/wpv-conditional]
Problem:
I had received a warning email from Google saying that the API was unrestricted and the key was potentially open to abuse. So, the sensible thing to do seemed to be to restrict it to the website URL. However, this seems to be causing the problem.
