I created a Test Form on your site called Test Post Form and configured it to create a post utilizing both a content template on the Post Title as well as incorporating a Custom Field. Everything worked as expected. You can recreate what i've done by previewing the Test Post Form I created and then submitting your own test and seeing the Post that it creates afterwards.
Here is the Test Form I submitted:
Here is the Entry that was created:
Here is the Post that was created:
You'll see in the post that the Post Title used our Content Template to include the value of our custom field that is on the form, which I submitted a value of "CustomFieldValue". You'll also see that Custom Field listed in the Custom Field UI in that screenshot using the Name of "customfieldname" and a value of "CustomFieldValue" exactly as it is configured to do.
So custom fields are being created properly by Gravity Forms, with or without the content template.
I was able to recreate the issue you reported with the Testimonial form. Because it is being created using the 3rd party Gravity Forms Custom Post Type Add-On the issue is most likely related to the use of that Add-On, because that is the difference between your form and the test form I created that is working fine.
I know a lot of users use that plugin and I haven't seen anyone else report this issue, so i'm not sure if it's a bug with the version of the Custom Post Type Add-On you are using or some sort of conflict. But it's specific to using that Add-On. You are going to need to get in touch with the developer of the Gravity Forms Custom Post Type Add-On.
Get in touch with him and explain that custom fields aren't being saved when you implement a content template on the Post Title field. It's probably a bug related to how he's creating the custom post type information.
Posted 7 years ago on Wednesday July 13, 2011 | Permalink