How to update w/o new entry?

This might do the trick for you:

add_filter('gform_update_post_entries', 'fu_gform_update_post_entries', 10, 2);

function fu_gform_update_post_entries($status, $form)
{
  return false;
}

I’ll be trying this out later this week. If I find out anything different, I let you know.

Much appreciated, jr00ck. Didn’t completely work for me in that a new entry was created when I updated the post. Strangely enough, though, the post captured some of the updated fields on the two post types I tried, but not others. Your suggestion might be headed in the right direction. Please let me know how you fare when you try it out, and if you manage to get this working. Thanks again.

https://themergency.com/stop-gravity-forms-from-creating-form-entries/

/**
 * Turn off all entries on all forms
 *
 * To only target a specific form or forms, add the form id to the action:
 * add_action( 'gform_post_submission_2', 'custom_remove_entries', 10, 2 ); // Targets form 2
 * add_action( 'gform_post_submission_5', 'custom_remove_entries', 10, 2 ); // Now you are targeting 2 and 5
 */
add_action( 'gform_post_submission', 'custom_remove_entries', 10, 2 );
function custom_remove_entries( $entry, $form )
{
	if (! class_exists('RGFormsModel') ) return;

	global $wpdb;

	$lead_id                = $entry['id'];
	$lead_table             = RGFormsModel::get_lead_table_name();
	$lead_notes_table       = RGFormsModel::get_lead_notes_table_name();
	$lead_detail_table      = RGFormsModel::get_lead_details_table_name();
	$lead_detail_long_table = RGFormsModel::get_lead_details_long_table_name();

	// Delete from detail long
	$sql = $wpdb->prepare( "DELETE FROM $lead_detail_long_table
								WHERE lead_detail_id IN(
								SELECT id FROM $lead_detail_table WHERE lead_id=%d
								)", $lead_id );
	$wpdb->query( $sql );

	// Delete from lead details
	$sql = $wpdb->prepare( "DELETE FROM $lead_detail_table WHERE lead_id=%d", $lead_id );
	$wpdb->query( $sql );

	// Delete from lead notes
	$sql = $wpdb->prepare( "DELETE FROM $lead_notes_table WHERE lead_id=%d", $lead_id );
	$wpdb->query( $sql );

	// Delete from lead
	$sql = $wpdb->prepare( "DELETE FROM $lead_table WHERE id=%d", $lead_id );
	$wpdb->query( $sql );
}

I added this to the bitbucket readme. Thanks!

This actually deletes the new entry after it is created, but it works. If you find a better way, let me know.

I actually am using the method jcow posted on an older website and it does work. But yeah, it’s kind of weird to delete the entry right after it was created rather than prevent it from being created. Not sure if it has to be that way since Gravity Forms might require having an entry in order to pass that info to a custom post type afterwards. Don’t know.

Anyway, I don’t think I’ll be posting anything more because what I need for this week is actually to edit an existing entry as I’m not using CPTs. As of Gravity Forms 1.8, you can query, edit, delete entries directly with their API and so it’s starting to eliminate the need for CPTs in certain instances. Good luck.

That said, any chance this plugin could auto-fill and edit existing entries instead of CPTs? That’s what I’ll be creating this week, would be nice if a plugin was out there that could do it. I haven’t found anything.

Sorry. Outside of the scope of this plugin. A whole different world there. Good luck!

Thanks, jcow. The code works exactly as intended and I’ll be using it to keep the entries down. But like jr00ck, I think what I need is to edit existing entries. My problem is that the update makes it into the database and shows up in a new entry but somehow doesn’t actually make it to the post. So the post continues to display the original entry data. I’ll keep an eye out here in case there’s another solution. Thanks for the awesome plugin.

Let me put the question this way… When I view the post in the admin, the custom fields contain the original entries no matter how many updates I’ve submitted (with and without the turn-off-entries snippet above). Yet this plugin properly loads the latest entry on the frontend when called to update the post. It appears, at least in my case, that the entry is being updated but not the custom fields in the post. Is there a way to force the post to update its custom fields when a new entry for that post is created? Thanks again.

I am not able to replicate this currently. What fields exist in the form? They are custom field fields?

When I update a post, it updates the actual post.

The form contains a standard title field (the post title) and any number of custom fields, eg, height, weight, hair color, mood. The custom fields can be single line, paragraph, dropdown, checkbox, etc. When I update a post, only the standard title field gets updated, but none of the custom fields. It’s not a public site, but I’m happy to share credentials if you want to take a look.

You can email me:
[email protected]

Problem solved! You were able to change the fields and show them changed on the admin side. The problem is with the front-end display software, not with this plugin. Great plugin, great support, much appreciated!

Hi Jcow

I have been reading this thread with interest. i too have the same issue:

My post contains custom fields and when I update in a Gform it creates another post instead of updating the post I was editing

is there a solution for this ?

thanks alot

joe

This is my template shortcode for your plugin that loads the current post into the form with its custom fields – to be edited (but when I submit it creates a new post)

echo do_shortcode(‘[gravityforms title=”false” description=”false” id=”1″ update field_values=”c_fname=’.$fname.’&c_lname=’.$sname.’&c_premises=’.$premises.’&c_street=’.$street.’&c_town=’.$town.’&c_county=’.$county.’&c_pcode=’.$pcode.’&c_phone=’.$phone.’&c_email=’.$email.’&b_model=’.$model.’&b_serial=’.$serial.’&b_idate=’.$idate.’&w_length=’.$length.'”]’);