Post My CF7 Form


This plugin enables the mapping of each form field to a post field. Each forms submitted from your website will then be saved as a new post which you can manage in your dashboard and display on the front end.

You can submit and map to a post all of the following fields,

  • Default post field, title, author, content, excerpt
  • featured image, you can submit a file and save it as a post attachment
  • meta fields, unlimited number of meta-fields can be created
  • taxonomies, you can map select/checkbox/radio input fields to taxonomies and the plugin will auto-populate your field items.
  • map your submitted forms to existing post types using the new UI
  • addition of form key to identify cf7 forms instead of the form id to make development more portable
  • this plugin allows your users to manage multiple draft submissions from a single page.
  • for large forms with multiple fields, an auto-create functionality has been added for meta-field mapping. See the installation instruction for details.
  • add links to newly saved posts into your confirmation mail.

v3.0 of this plugin introduces many changes to enable other plugin developers to leverage the functionality available in this plugin. If you are a developer, please look at the code where ample comments are provided.

Make your CF7 Form more portable

this plugin introduces form keys (which you can modify in the CF7 admin table). Keys are unique for each form, allowing you identify a form my its key rather than an ID. Why is this priceless? IDs changes from one server to the next because they are the custom post ID attributed by the WordPress installation, and therefore you develop your form in a local machine only to find out that the IDs are different when you move your form to your production server. To overcome this problem, we suggest you use a form key along with this plugin’s contact form shortcode, [cf7form key="contact-us"]. Don’t worry your old contact form 7 shortcodes will still work too, behind the scenes we simply map the key to the ID and call the regular contact form 7 shortcode.

Powerful form designs

This plugin is now fully compatible with Smart Grid-Layout Designs for Contact Form 7. The Smart Grid for CF7 allows responsive grid-layout designed forms, as well as powerful features such as repetitive field inputs (using table structures with multiple row inputs), repetitive form sections using multiple tabbed inputs, as well as optional input sections using toggled collapsible sections. Furthermore the plugin offers a modular approach to form design, where existing forms can be inserted as sub-sections.

Post my CF7 Form now saves these complex forms designs seamlessly into your dashboard posts.

Other compatible plugins

  • Contact Form 7 Conditional Fields By Jules Colle.
  • Contact Form 7 Multi-Step Addon By ThemeREX.
  • Contact Form Submissions by Jason Green.
  • Live Preview for Contact Form 7 by Addons for Contact Form 7.
  • Void Contact Form 7 widget for elementor page builder by voidCoders.
  • Country & Phone Field Contact Form 7 by Narinder Singh Bisht.
  • Date Time Picker Field by Carlos Moreira.

Filters for fields

In addition to mapping your form fields to post fields you are also given a custom filter for that specific form field. The filter option allows you to custom fill the post created for the submitted form, for example if a form requests the date of birth, you may want to create an additional post field for the age, so you can filter the date field in your functions.php file and calculate the age and save it to a custom post meta field. The custom filters are created using the following nomenclature, cf7_2_post_filter-<post_type>-<post-field>. For example if you have created a custom post type quick-contact, which as a meta field age, you could filter it with,

function filter_date_to_age($value, $post_id, $form_data){
  //$value is the post field value to return, by default it is empty
  //$post_id is the ID of the post to which the form values are being mapped to
  // $form_data is the submitted form data as an array of field-name=>value pairs
    //calculate the age
    $value = ....
  return $value;

Special Fields

Author – unless the user sets the field, the default set in this order: current logged in user else, the recipient of the CF7 form email if such a user exists in the database, else it reverts to the user_id=1 which is the administrator. A filter is also available to set the author.

Featured image/Thumbnail – these will only accept form fields of type file. However, non image files uploaded will not show up as thumbnails in the post edit page.

Title/Content/Excerpt – there are enabled by default, and can be used to map any form fields to them. However, if you wish disable these fields (using the post registration supports array of values), then please use the filter that allows these to be set for your custom post type. (see the filters section for more info)

Pre-fill form fields

Contact Form 7 does not allow you to pre-fill fields before your form is displayed. With this plugin you can do this, you will need to map your form first, and use the filter ‘cf7_2_post_filter_cf7_field_value’ to pre-fill your fields, see the Filter & Actions section for more details.

Contact Form 7 list table

This plugin re-organises the CF7 dashboard list table, using the cf7 custom post list table to permit other developers to easily add custom columns to the list table. You can therefore use WP functionality to customise your table. For example you could view how many submits a form has received.

Other hooks

The plugin has been coded with additional actions and filters to allow you to hook your functionality such as when a form to post mapping is completed. For a list of such hooks, please refer to the Filter & Actions section.

Checkout our other CF7 plugin extensions

  • CF7 Polylang Module – this plugin allows you to create forms in different languages for a multi-language website. The plugin requires the Polylang plugin to be installed in order to manage translations.

  • CF7 Multi-slide Module – this plugin allows you to build a multi-step form using a slider. Each slide has cf7 form which are linked together and submitted as a single form.

  • Post My CF7 Form – this plugin allows you to save you cf7 form to a custom post, map your fields to meta fields or taxonomy. It also allows you to pre-fill fields before your form is displayed.

  • CF7 Google Map – allows google maps to be inserted into a Contact Form 7. Unlike other plugins, this one allows map settings to be done at the form level, enabling diverse maps to be configured for each forms.

*Smart Grid Layout Design for CF7 – allows responsive grid layout Contact Form 7 form designs, enabling modular designs of complex forms, and rich inter-linking of your CMS data with taxonomy/posts populated dynamic dropdown fields.

Privacy Notices

This plugin, in itself, does not:

  • track users by stealth;
  • write any user personal data to the database;
  • send any data to external servers;
  • use cookies.

However, be aware that this plugin allows you to map your forms so as to save the data of any submissions made through these forms to the WordPress database. Should any of these mapped forms collect data considered to be private to the user, it will be saved to the database so you should take due diligence to inform your form user and comply with Privacy Data laws.

Filters & Actions for Developers

The following are hooks primarily aimed at developers. More general hooks and filters are now documented inline in a helper metabox in the mapping edit page.


This filter allows you to customise taxonomies arguments before they are registered.

function modify_my_categories($taxonomy_arg){
  //$taxonomy_arg is an array containing arguments used to register the custom taxonomy
  //modify the values in the array and pass it back
  //for example, by default all taxonomies are registered as hierarchical, use this filter to change this.
  $taxonomy_arg['hierarchical'] = false;
  return $taxonomy_arg;

It is possible to pass optional arguments for Metabox callback functions, taxonomy count update, and the taxonomy capabilities. See the WordPress register_taxonomy documentation for more information.

function modify_my_categories($taxonomy_arg){
  $args = array(
          'meta_box_cb' => 'my_custom_taxonomy_metabox',
          'update_count_callback' => 'my_taxonomy_selected',
          'capabilities' => array(
                              'manage_terms' => 'manage_categories'
                              'edit_terms' => 'manage_categories'
                              'delete_terms' => 'manage_categories'
                              'assign_terms' => 'edit_posts'
  return args;


This filter allows you to modify the taxonomy terms query arguments for a form’s dropdown/checkbox/radio list.

function custom_dropdown_order($args, $cf7_post_id, $taxonomy){
  if(20 == $cf7_post_id && 'location_categories' == $taxonomy){
    //modify the order in which the terms are listed,
    $args['order_by'] = 'count';
  return $args;

This function changes the list order, putting the most commonly used terms at the top of the list.
For more information on taxonomy query arguments, please refer to the WP codex documentation.


This filter expects a boolean, by default it is true and enables jQuery select2 plugin on select dropdown fields.
To disable it, do the following

function disable_select2_plugin($enable, $cf7_post_id, $form_field){
  if(20 == $cf7_post_id && 'your-option' == $form_field){
    //we assume here that cf7 form 20 has a dropdown field called 'your-option' which was mapped to a taxonomy
  //you could just return false if you want to disable for all dropdown
  return $enable;


This allows you manually launch the select2 jQuery dropdown fields. This is required if you need to customise the select dropdown on windows load event with your own jQuery scripts before the select2 transformation is applied. Please read the FAQ on custom scripts to make sure you trigger your script after the form is mapped.

add_filter( 'cf7_2_post_filter_cf7_delay_select2_launch', '__return_true');


This filter expects a boolean, by default it is false and disables optgroup on select dropdown options.
To enable grouped options for hierarchical taxonomy top level term, you can use this filter. Note however, that child term options will be grouped by their top-level parent only as nested optgroup are not allowed. Furthermore the parent term will not be selectable. Therefore this option only makes sense if you have a hierarchical taxonomy with only single level child terms which can be selected. To enable grouped options,

function enable_grouped_options($enable, $cf7_post_id, $form_field, $parent_term){
  if(20 == $cf7_post_id && 'your-option' == $form_field){
    //we assume here that cf7 form 20 has a dropdown field called 'your-option' which was mapped to a hierarchical taxonomy
    //you can even filter it based on the parent term, so as to group some and not others.
    //the attribute $parent_term is a WP_Term object
      case 'Others':
  return $enable;


This filter is useful to change the behaviour in which previously submitted values can be edited by a user. By default the plugin loads forms values that have been saved using the ‘save’ button. However, you can modify this by changing the default post query such as the example below,

function load_published_submissions($query_args, $post_type){
  if('submitted-reports' == post_type){
    //we assume a cf7 form allowing users to submit online reports has been mapped to a post_type submitted-reports'
      $user = wp_get_current_user();
      //load this user's previously submitted values
      $query_args = array(
        'posts_per_page'   => 1,
        'post_type'        => post_type,
        'author'       => $user->ID,
        'post_status'      => 'published'
  return $query_args;


this filter is fired when the cf7 shortcode output is printed, it allows you to add a custom script at the end of your form should you need it,

add_filter('cf7_2_post_form_append_output', 'append_my_script', 10, 4);
function append_my_script($output, $attr, $nonce, $cf7form_key){
    return $output;
  $cf7_id = $attr['id'];
  if(19 == $cf7_id){ //check this is your form
    $output .= '<script type="text/javascript">';
    $output .= '(function( $ ) {';
    $output .= '  //fire your script once the form nonce event is triggered';
    $output .= '  $(document).on("'.$nonce.'", $("div#'.$nonce.' form.wpcf7-form"), function() {';
    $output .= '  var cf7Form = $("div#'.$nonce.' form.wpcf7-form");';
    $output .= '  ... //your custom scripting';
    $output .= '});';
    $output .= '})( jQuery );';
    $output .= '</script>';
  return $output;


This filter allows you to load default values into your mapped forms. If the current user has a saved form, this filter will override any values you set.

add_filter('cf7_2_post_form_values', 'set_default_location', 10, 3);
function set_default_location($values, $$cf7_id, $mapped_post_type, $cf7_key){
  if('travel_post' != mapped_post_type){
    return values;
  if('contact-us' == cf7_key){ //check this is your form
    $field_name = 'location-rental';
    $values[$field_name] .= 'Paris';
  return $values;


this filter allows you to tweak the arguments used to register the custom_post type, for example, if you want to modify the rewrite front-end slug for the post type,

add_filter('cf7_2_post_register_post_my-custom-post', 'set_rewrite_slug');
function set_rewrite_slug($args){
  $args['rewrite'] = array(
    'slug' => 'posted-replies',
    'with_front' => true
  return $args;


action introduced for plugin developers specifically. Fired at the end of the submission mapping process, once a new post has been created for a new submission. The current mapping of the form fields is exposed, along with the data values submitted in the form and the files uploaded. For developers interested in using this hook, please lookup in the inline documentation in the code itself. The action is located in the includes/class-cf7-2-post-factory.php file.


This action is fired each time the a mapped post is registered with the WP framework. This is mainly added for plugin developers to extend this plugin and target custom post types that are created by this plugin.
add_action(‘cf72post_register_mapped_post’, ‘custom_mapped_post’);
function custom_mapped_post($post_type){
//$post_type the post type being registered in the backend.


The following have contributed to bug fixes, documentation, and/or translations for this plugin,



  • 1.You can map your form fields to post fields and meta-fields. You can save the mapping as a draft. You can also change the custom post attributes that will be used to create the post. The default ones are public, show_ui, show_in_menu, can_export, has_archive, exclude_from_search. For more information, please consult the custom post documentation.
  • 2.Once created, you have can only view the mapping. All the fields are disabled to maintain post integrity. You can however add new meta-fields. You will also see your new custom post in your dashboard menu is you have enabled post attributes show_ui & show_in_menu.
  • 3.The CF7 table list shows an extra column with the status of the form mapping.
  • 4.You can now map forms fields to custom taxonomies
  • 5.You can edit your custom taxonomy nomenclature and slug, do this before mapping it.
  • 6.If your form contains a file upload field, the featured-image option will appear on the mapping screen. Select your file field to map the uploaded image to the post thumbnail.
  • 7.making custom posts publicly queryable.
  • 8.Helper metabox on the mapping admin screen gives you direct access to actions and filters to customise the way your form submissions are mapped to a post. Easy click-to-copy functionality ready to paste into your functions.php file.
  • 9.Follow the screenshot instructions to map a field to a taxonomy.


  1. Install the Contact Form 7 plugin
  2. Install the Post My CF7 Form plugin
  3. Create a contact form. A new column appears in the contact table list which shows you which Post Type the form is mapped to
  4. Click on the link ‘Create New’ that appears on the column to start mapping your form to a custom post.
  5. Create the post and it will appear in your Dashboard. Currently you cannot undo a mapped form, you will have to create a new form and re-map it while deleting the old one to change the mapping. So be careful when you save finally create your form. In a later version of this plugin I will introduce functionality to un-publish a mapped form.
  6. As of v1.5 of this plugin a functionality has been introduced to quickly create meta-field mappings. This is useful when you have complex forms with multiple fields. Simply add a new meta-field and select a field to map (leave the meta field name to the default value), the meta-field name will automatically update itself to reflect the form field name with hyphens replaced by underscores. Subsequent additions of new meta-fields will further increase the magic by auto-selecting the next form field in the dropdown and filling in the meta-field name too. If you wish to switch-off this functionality, simply manually edit the meta-field name and it will switch-off the autofill.
  7. Each time a visitor submits the form on your website, a new post will be created.


1. How do I redirect to a page and access the saved post?

Place the following in your functions.php file,

add_filter('cf7_2_post_form_append_output', 'redirect_on_submit', 10, 3);
function redirect_on_submit($script, $attr, $nonce){
  //$attr cf7 shortcode attributes to check if this is the correct form.
  $url = site_url('/submitted'); //page slug to redirect to.
  $url = add_query_arg( array('cf72post' => $nonce,), $url);
  $url = esc_url($url);
  $script .= '<script>'.PHP_EOL;
  $script .= 'document.addEventListener( "wpcf7mailsent", function( event ) {'.PHP_EOL;
  $script .= '  var save = document.getElementsByClassName("cf7_2_post_draft");'.PHP_EOL;
  $script .= '  if(save.length == 0  || "false" === save[0].value){'.PHP_EOL;
  $script .= '    location = "'.$url.'";'.PHP_EOL;
  $script .= '  }'.PHP_EOL;
  $script .= '}, false );'.PHP_EOL;
  $script .= '</script>'.PHP_EOL;
  return $script;

where you need to change the slug of your page to which you want to redirect.

Now the submitted form is saved to a post and its ID is stored in a transient field by the plugin. You can access this transient field with the following code in your page template,

  $post_id = get_transient($_GET['cf72post']);
  echo 'form submission saved to post:'.$post_id;

If you wish to redirect to the newly saved post (assuming it is published, see FAQ #16),
$post_id = get_transient($_GET[‘cf72post’]);
//get the link to the new post,
$url = get_permalink($post_id);
if ( wp_redirect( $url, 200 ) ) {
echo ‘unable to redirect, maybe the post wasn’t published’;

2. map a form to a post?

In the Contact Form 7 table list you will notice a new column has been added which allows you to create a new custom post mapping. This will take you to a new screen where you will see your existing fields listed in select dropdowns. Map your form fields to either a default field (eg title, content, excerpt, or author), or create a custom (meta) field, or even create a new taxonomy for your post. Once you have mapped your form you can toggle its status from on to off. In the off position, the plugin will no longer capture form submissions and save them to the mapped post.

3. I made a mistake in my form mapping, how do I correct it once it is created?

You can simply modify the mapping at any given time, however if a mapping has been live and saving submissions to your post, then it is not recommended to make changes. Unless you have a fair understanding of WordPress posts and meta-fields structures and how these are saved in the database, I highly recommend that you delete any existing posts that may have been saved from form submissions that used the previous mappings. Failing to do this without a proper understanding of the changes you are making to an existing mapping with previously saved post submissions could lead to difficult errors to debug and fix once you start creating post submissions that have a different mapping. Consider yourself warned!

4. How do remove a mapping?

Simply toggle the status to off.

5. How do I map a field to a taxonomy ?

You create a new taxonomy and map your field to it. Note however that only select/checkbox/radio type of fields can be mapped to taxonomies. Once mapped and published you will see your taxonomy appear in your custom post menu. You can add terms to your taxonomy and these will be made pre-filled into your mapped field. Users can select a term and when the form is submitted, the post will be created with those terms assigned to it. (see screenshot 9 for more details.)

6. How do I create non-hierarchical taxonomies ?

You need to use a special filter for this, ‘cf7_2_post_filter_taxonomy_registration-{$taxonomy_slug}’, see the Filter & Actions section for more details.

7. Why filter the taxonomy mapping ?

You may have noticed that in addition to mapping a post field or taxonomy to one of your form fields, you can also use a filter to hook your own custom values. In the case of taxonomies, you can actually map a form submission to a specific set of terms depending on the submission of other fields.

8. How do I allow my form users to create a new term for a taxonomy?

This is a little more complex. You will need to create an input field in your form in which users can submit a new term. You will then need to hook the action cf7_2_post_form_mapped_to_{$post_type} which is fired right at the end of the saving process. The hook parses the newly created $post_ID as well as the submitted $cf7_form_data form data array. You can then check if your user has submitted a new value and include it in taxonomy and assign the new term to the post.

9. How can I pre-fill a form’s field values ?

There are are 2 filters provided to achieve this. In both cases, these filters are fired if the form is mapped to a post type only. The default behaviour is for the plugin to seek any draft saved form values for teh current user. A form is saved (draft) if the save button tag is used which allows a user to save a partially filled form and to submit it at a later stage. If a draft form is found for the current user, then the first filter will not be fired,

  1. the cf7_2_post_filter_cf7_field_value is fired for each field, and a helper code is available in the mapping edit admin page (see the Screenshot #8), filter #7.

  2. cf7_2_post_form_values is fired at the end of values pre-fill process, and allows all the values to be filtered, including those that may have been loaded if the current user as a draft form saved.

    add_filter(‘cf7_2_post_form_values’, ‘simple_cf7_form_values’ ,10,4);
    function simple_cf7_form_values($field_values, $cf7_id, $post_type, $ck7_key){
    if( ‘my-form’!=$ck7_key ) return $field_values; //check this is the correct form.
    $field_values[‘your-name’] = ‘prefilled name’;
    return $field_values;

If you have a WordPress page template that contains a CF7 form and want to change the field values from one page request to another, this can be done using the cf7_2_post_form_values filter (see Filter & Actions for more details). You will need to create an anonymous function on this filter and pass the CF7 id form your shortcode which you can automatically scan for form your page content. In the example below I assume that the page contains the default ‘Contact Me’ CF7 form which I want to pre-fill if a user is logged in,

$content = get_the_content();
//let's find our shortcode
preg_match_all( '/' . get_shortcode_regex() . '/s', $content, $matches );
$args = array();
if( isset( $matches[2] ) ){
  foreach( (array) $matches[2] as $key => $shortcode ){
    if( 'contact-form-7' === $shortcode )
      $args[] = shortcode_parse_atts( $matches[3][$key] );
//here I am assuming there is a single form on the page, if you have multiple, you will need to loop though each one
if(!empty($args) && isset($args[0]['id'])){
  $short_id = $args[0]['id'];
  $values = array();

    $user = wp_get_current_user();
    $values['your-name']= $user->display_name;
    $values['your-email'] = $user->user_email;
      $term = get_term_by('id', $subject, 'project-type');
      $values['your-message'] = 'Dear Hexagon,'.PHP_EOL.'I request you to create a new '.rtrim($term->name,'s') ;

    //now lets filter the values
    add_filter('cf7_2_post_form_values', function($field_values, $cf7_id) use ($short_id, $values){
      if($short_id == $cf7_id ){
        return $values;
    }, 10,2);

10. How to use custom JavaScript script on the form front-end ?

The plugin fires a number of jQuery scripts in order to map saved submissions back to draft forms. So if you have a form which your users can save before submitting and you need to customise some additional functionality on your form on $(document).ready(), then you need to make sure it fires after the plugin’s scripts have finished. In order to achieve this, the script fires a custom event on the form, cf7Mapped, which you can use to ensure you script fires in the right order, here is how you would enable this,

(function( $ ) {
    'use strict';
  $( function() { //the jQuery equivalent of document.ready()
    var cf7Form = $('div.cf7_2_post form.wpcf7-form'); //this ensures you target the mapped forms
    cf7Form.on('formMapped', function(){
      //fire your script
})( jQuery );

11. Is it possible to save my form to an existing post type?

yes, but you need to know how to use WordPress hooks in your functions.php file in order to get it to work. If you map your form, you now have a dropdown to select the type of post to which you want to save it to. When you select ‘Existing Post’ from the option, instructions will show up on screen to map your form.

12. I am saving my form to an existing post, can I pre-load taxonomy terms in my form?

Sure you can, again you need to use the hooks cf7_2_post_map_extra_taxonomy & cf7_2_post_pre_load-{$post_type} to get it to work, see the example in the section Filter & Actions.

13. Is there any advanced documentation for developers ?

sure, there is a section Filter & Actions which lists all the hooks (filters & actions) available for developers with examples of how to use them. These expose a lot of the default functionality for further fine-tuning. If you see a scope for improvement and/or come across a bug, please report it in the support forum.

14. Is it possible to have multiple forms submitted from a single page ?

yes, as of v1.4 of this plugin you can now have multiple saved/draft submissions on a single page. To get it to work you need to track which forms are mapped to which post yourself. Introduce a hidden variable in your form to store your mapped post ids. For example you have a custom post which maps/stores submitted faults reported by your users. On page load, you need to pass the mapped post id to this plugin via your cf7 shortcode by dynamically calling the shortcode using do_shortcode and the attribute cf7_2_post_id,

$args = array(
  'post_type'  => 'fault-post',
  'post_status'=> 'any',
  'author' => get_current_user_id()
$faults = get_posts($args);
foreach($faults as $post){
  $cf7_attr = ' cf7_2_post_id="'.$post->ID.'"';
  //display your form, you might want to add some more html to structure to display them as tabs or something else.
  echo do_shortcode('[cf7form key="user-fault" title="Faults" '.$cf7_attr.']');
//if you need to add an extra empty form, then ensure you pass the cf7_2_post_id attribute as -1
//$cf7_attr = ' cf7_2_post_id="-1"';
//echo do_shortcode('[cf7form key="user-fault" title="Faults" '.$cf7_attr.']');

15. I have enabled a save button on my form, but draft submissions are not being validated!

This is the default functionality for saving draft submissions. This is especially useful for a very large forms which users may take several visits to your site to complete. Email notifications of draft submissions are also disabled. If you wish to override this, you may do with the filters cf7_2_post_draft_skips_validation & cf7_2_post_draft_skips_mail examples of which are given in the documentation Filters & Actions below.

16. How do I publish posts automatically on form submission ?

The default behaviour is to save post to ‘draft’ status. If you wish to change this, you can use the filter ‘cf7_2_post_status_{$post_type}’ and return a valid post status. See the Filters & Hooks section of this documentation for more information.

17. How do I make custom posts publicly visible on the front-end ?

the default configuration of the plugin mapped custom posts are only visible in the dashboard. This a security feature. If you want your posts to be visible on the front-end, then you need to change the registration attributes. See this screenshot for the posts settings you need to enable or disable for making your posts public as well as query-able on the front-end.

If you have created a custom taxonomy for your post, you can include these into your main menu by enabling them in the Appearance->Menu screen options dropdown of your Dashboard.

18. I mapped some fields to post meta-fields, why can’t I see them in the dashboard?

When you map your form fields to the custom post meta fields, you need to to ensure that these meta-fields are displayed in the post edit page of your dashboard using meta-boxes. You can custom create these meta-boxes in your functions.php file or you can also use a plugin. However, without these metaboxes you won’t be able to see your field values when you edit your posts.

19. Why does my form page have no-cache metas ?

As of v3.0.0 the no-cache metas have been added by default to pages with embedded forms that are being mapped by this plugin. Note this does not affect pages with forms which are not mapped. This is done to ensure that forms with pre-loaded field values (saved draft forms or forms with pre-filled values) are not being cached by the browser and as a result load spurious values.

If your form is not being saved by users and not being pre-filled, then you may decide to disable the no-cache metas with the following filter,

add_filter('cf7_2_post_print_page_nocache_metas', '__return_false'));

It is not possible to target pages with specific forms.

20. How can I reload forms already submitted?

Once a form is submitted the _cf7_2_post_form_submitted meta-field is updated (from ‘no’ to ‘yes’) in the post to which the form was saved. As of v3.3.0 a metabox is introduced in the post admin page which allows an administrator to toggle the status back to ‘no’ and therefore allow your user to re-load the form with the submitted values (same functionality as a saved draft form).

21. How can I filter the terms of a mapped taxonomy field ?

Use the filer provided in the filter & actions helper metabox of the mapping page in the dashboard (see screenshot 8). Use the filter terms list (#4 in the section Form Loading Hooks),

22. Can I map deeper levels of my hierarchical taxonomy to a select2 field?

As of v3.8, 2 new hooks have been introduced to allow you to custom map your taxonomy terms to form fields that use a JavaScript plugin to allow users to select terms which are nested deeper than the default parent-child setup provide by this plugin. An example of such a js plugin is the Select2 extension, Select2-to-tree. This plugin requires the select options to have specific classes and attributes to be set (see the documentation). To achieve this, here is an example of code you can place in your functions.php,

/add_filter('cf7_2_post_filter_cf7_taxonomy_select_optgroup', 'turn_off_grouping', 10, 5);
function turn_off_grouping($isGrouped, $cf7_post_id, $field, $term, $cf7_key){
  if('my-contact-from' == $cf7_key && 'your-country' == $field){
    $isGrouped = false;
  return $isGrouped;
//switch off select2 that is loaded & initialised by this plugin.
add_filter('cf7_2_post_filter_cf7_taxonomy_select2', 'turn_off_select2', 10, 4);
function turn_off_select2($useSelect2, $cf7_post_id, $field, $cf7_key){
  if('my-contact-from' == $cf7_key && 'your-country' == $field){
    $useSelect2 = false;
  return $useSelect2;
//enqueue your own select2/select2-to-tree libraries.
add_action('cf72post_form_printed_to_screen', 'enqueue_libraries');
function enqueue_libraries($cf7_key){
//add extra classes.
add_filter('cf72post_filter_taxonomy_term_class', 'add_custom_classes_to_options', 10, 5);
function add_custom_classes_to_options($classes, $term, $level, $field, $cf7_key){
  if('my-contact-from' == $cf7_key && 'your-country' == $field){
    $classes[] = 'l'.(level+1);
  return $classes;
//add extra attributes.
add_filter('cf72post_filter_taxonomy_term_attributes', 'add_custom_attributes_to_options', 10, 5);
function add_custom_attributes_to_options($attributes, $term, $level, $field, $cf7_key){
  if('my-contact-from' == $cf7_key && 'your-country' == $field){
      $attributes['data-pup'] = $term->parent;
  return $attributes;

You will also need to initialise your select2 field,

var $mappedForm = $('div.cf7_2_post form.wpcf7-form');
var eventID = $mappedForm.closest('div.cf7_2_post').attr('id');
//initialise once the form has been loaded by the plugin.
$mappedForm.on(eventID, function(){
  $('.your-country select').select2ToTree();

23.Can a previously submitted post be reloaded into a form programmatically?

yes, this is possible. You have to know a few things first,

  • A mapped post that has been saved as a draft is reloaded automatically for the same author/logged in user.
  • A submitted post, as opposed to a saved/draft one, has a its meta-field _cf7_2_post_form_submitted set to ‘yes’, and this controls whether or not an author’s post is to be reloaded when the form is being displayed for the current user.

However, you can override all this by actually hooking into the post loading process prior to displaying the form. The process used get_posts to retrieve a post, and takes the first post it finds.

add_filter('cf7_2_post_filter_user_draft_form_query', 'custom_post_query',10,3);
function custom_post_query($query_args, $post_type, $cf7key){
  if('my-form' === $cf7key){ //check for your mapped form unique key.
    //set up your custom $query_args
  return $query_args;

24. How do I add a link to newly saved post in the confirmation mail?

Use the mail tag [cf7_2_post-edit] and [cf7_2_post-permalink] to add a link to the editable post in the admin dashboard and the post permalink in the front-end respectively.

25. When deleting a mapping, how do I delete all submitted posts data ?

Hook the following filter in your functions.php file prior to deleting the mapping for that post_type.

add-filter('cf7_2_post_delete_submitted_posts', 'delete_posted_data',10,3);
function delete_posted_data($delete_data, $post_type,$form_key){
  //you may filter by form_key and/or post_type....
  $delete_data = true;
  return $delete_data;

26. Save draft button is auto-styled, how to custom style it?

The save button is automatically styled (with inline style script) to be the inverse colours of the submit button as well as having a 1px wide border. The border line style is set using rules included in the CSS stylesheet and can be overridden with custom CSS.
The auto-styling of the colour and background colour can also be overridden or altogether switched off with the following filter in your functions.php file,

add_filter('c2p_autostyle_save_button', '__return_false');

the filter also passes the form key, should you want to distinguish between forms.


August 24, 2021
5.0.0 is truly a before & after version. You can now make changes in the field mapping without drafting the form again and again (the most veterans here know what I mean). Mapping process now goes on-the-fly, and the transition from the old version to 5.0.0 has been miracolously flawless, with no errors. The plugin allows to map custom post types, custom fields and even custom taxonomies and it follows the WordPress post creation standards. For anyone who's not familiar with it, this is a good (and very respectful) practice, because if you happen to deactivate the plugin, your created posts will still be there. Practices like this truly help the WordPress community to grow bigger. Thank you Aurovrata for your support and for this amazing plugin. CF7 (and us, too) owes you a lot, because you've taken CF7 to a higher level.
March 10, 2021
This plugin works perfectly. There was an issue with the messages (not displaying) when visitors submitted their forms. The plugin maker was able to help me out quickly with an update. What now works for me: - Create a form - Map form fields onto custom fields - Submitted forms displayed in custom fields as custom draft posts - I only have to review and publish to make the posts appear on the website Thanks!
February 27, 2021
This Plugin is awsome. Let your users generate content, and you can do with the stuff everything you want, with of the included filters. And if an update comes up with any problem -> support forum -> solution is on the way.
Read all 35 reviews

Contributors & Developers

“Post My CF7 Form” is open source software. The following people have contributed to this plugin.


Translate “Post My CF7 Form” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.



  • fix compatibility of mappings handled with filter.


  • imrpove admin js field tag scanner.


  • fix post udpate process on existing submitted posts.


  • fix auto mapping of meta fields.
  • added hooks shortcut for taxonomy mappings.


  • update hybrid library.


  • enable inverse auto-style of draft submit.
  • added ‘c2p_autostyle_save_button’ filter to switch off autostyling.
  • hide save tag in admin from non-mapped forms.
  • fix files empty loop.
  • added ‘c2p_delete_all_submitted_posts’ boolean filter when deleting mapping.
  • added ‘c2p_delete_all_submitted_posts_query’ filter post query.
  • enable mapping delete.
  • added mapping delete in form table quick-edit
  • fix filter taxonomy mapping.
  • fix update of cpt attributes bug.
  • fix post type creation bug on new and unmapped posts


  • fix admin source change mapping bug.


  • fix add custom meta field issue.
  • fix file field handling when no file uploaded.


  • enable front-end form display for ‘draft’ forms.
  • added helper for ‘cf7_2_post_delete_submitted_posts’ hook.
  • update hybrid dropdown library.


  • improve hook helper code.
  • pass branch array to cf7_2_post_filter_taxonomy_query hook.


  • update hybrid dropdown library in admin.
  • fix admin styling issues.
  • fix taxonomy mapper.
  • enable mapping of taxonomy to multiple form fields.


  • complete rewrite of admin mapping editor.
  • partial rewrite of post factory.
  • creation of mapper classes to handle form mapping to/loading from the DB.
  • added ‘cf7_2_post_delete_submitted_posts’ filter.
  • fix save draft form for file fields.
  • include Hybrid Dropdown fields
  • release of new YouTube tutorials.