Dave from Gravity Wiz

I’m not able to recreate this issue. Can one of your provide the following:

1. An export of your form.
2. The ID of the field in question.

This integrates with Gravity Forms so all the hooks that are available through Gravity forms are available here as well.

1. gform_after_submission would do the trick.

2. gform_disable_post_creation is probably your best bet if you might need to cancel post creation based on a remote query.

You can use the “gfcpt_post_type_args” filter to modify the post types that are available in the Post Types drop down.

add_filter( 'gfcpt_post_type_args', 'my_gf_post_type_args' );
function my_gf_post_type_args( $args ) {
    $args['public'] = false;
    return $args;
}

Typically issues with custom fields are related to Gravity Forms and not the GF CPT plugin specifically. If you disable the plugin and create a regular post, do the custom fields get mapped there?

Sounds like this is more about modifying the form object before GF CPT has processed the post to account for your custom inputs. Glad you were able to find a solution.

Thanks for reporting this. It has been fixed in v3.1.2 which will be available soon.

Hi guys, what versions of Gravity Forms and this plugin are you running?

Hi balbuf,

What version of this plugin are you using? This issue was fixed in v3.1

I’ll implement your other suggestion in the next version. ??

The $field object also has a formId property. You can check for a specific form and field like so:

https://pastie.org/private/g9mztt7nhlxvr3cgoo2sza

The GF support team will get you squared away. ??

Hi Jon,

Gravity Forms handles saving the post meta even for the custom post types. This plugin just handles changing the post type. With that said, if you deactivate this plugin, are the hidden post meta values populated as expected? The post would be created as a “post” and not your custom post type so you’d need to look there.

Hm, I have had any luck recreating this issue. A few questions for anyone able to recreate:

1. What type of GF field are you using?
2. What version of GF are you using?
3. Does it only occur with hierarchical taxonomies or all taxonomies?

Here’s an alternate version that allows you to specify a different default value per field ID:

https://pastie.org/private/eqs3xt1vugtjbo4ozkpug

Hi antonCPT, I can confirm that this issue does exist and that I’m able to recreate it. I don’t have plans to fix this currently but I will leave this ticket open for any other developers who want to look into this.

Hi Maelga, I see what you mean. This is just how the plugin works. The choices are dynamically populated every time the form is loaded. Any changes you make to the choices will be overwritten with the newly populated choices. We don’t have plans to add support for this currently.