awesiome

@jamiek47,

If the field-name is the same for both your custom field and the CF7 field and all field labels for the checkboxes are the same in the custom field and CF7 then perhaps it is a plugin issue. In order to map checkboxes and radio buttons among other fields, you need to create custom fields in WordPress. Different plugins can get this done but due to the way some of them name the custom fields, not all plugins work well with other plugins. The best plugin to use would be Advanced Custom Fields plugin. I have personally never tried to map checkboxes.

In my personal experience, I tried prefilling CF7 with info from user profiles. You can do it with any field type even radio buttons but not with checkboxes. I have no idea why. But perhaps mapping is something different. Let me know how it goes.

Hey jamiek47,

You can edit by going to the main contact forms menu (where all the contact forms are listed) scroll to the contact form whose mapping you want to edit, select quick edit, look for “post type” drop down (it should be set to publish if you have done mapping to that form before) and then change it to draft.

Once you change it to draft it will set all the fields in your mapping to an editable state. Go to the mapping, edit everything you want, click create when you are done and that will change the “post type” setting back to published.

Thanks

I have tried the add-on but I did not have a problem with protecting individual custom posts. The plugin on it’s own can be used to protect each individual custom post without the need for an add-on. What I need is to protect the entire post type. So for instance if I have a custom post type called portfolio with say 100 posts how to I protect the entire portfolio post type instead of going into each individual post and manually changing it.

I could put all posts of the custom post type in a specific category and then use the plugin to restrict the category. But I would still have to add each individual post to the new category. New posts would not be added automatically. Changing the default WordPress post category only works for native WordPress post types and not custom posts.

For now I have decided to display all the posts in a grid on certain page and restrict the page itself to a membership level. I have also gone ahead to make the posts not publicly queryable anyway. So they can only be seen in the post grid section on that specific page.

But making it possible to restrict entire post types would be good for future versions of the plugin.

Thank you for responding to my questions ??

Hi,

That makes perfect sense. However, I am talking about a custom post type. Not just a single post. So I have indeed created the membership level but I cannot restrict access because there are many posts in that post type and more are created each day therefore manually restricting each individual post becomes hard.

The ACF plugin has a checkbox that creates a metabox for your custom fields when ticked which I have applied. The plugin interestingly is only still showing two of the four custom fields but at least now it shows the custom meta fields consistently (even though it only shows some of them)

if you map to a custom post, you can actually type out your own meta-fields and the plugin will create them for you.

In previous versions of the plugin, yes you could create your own custom fields while you configure mapping for a custom post but they would not be saved correctly (I assume this is no longer the case in the newest version although I haven’t checked.)

Overall, I could simply use the your plugin itself to create the custom post as well as the custom meta fields to solve the whole problem especially now that the publicly queryable function works. The reason I am opting to use the ACF plugin is for the amount of control it provides over custom meta fields.

I will wait patiently for updates to your plugin. Thanks for maintaining this project and not abandoning it like many developers do down the road.

Hi @aurovrata,

About the custom fields issue, I have already created the custom fields using the Advanced Custom Fields plugin. Your plugin can display custom posts in the drop down when you decide to map to an existing post.

However in the meta fields area, it sometimes displays custom meta fields and other times it doesn’t. I have not clue why. I just tested the most recent version and on one occasion the plugin detected three of my four custom meta fields and mapped the corresponding CF7 fields perfectly. However it appears to just have been a stroke of luck because although it worked for two forms, when I tried to map the third form it didn’t show me any of my custom meta fields in the drop down when I attempted to map to an existing post type. So I do not know exactly what’s going on but I’m glad two of my forms are 95% mapped successfully.

I appreciate the time taken in attaching the links to creating custom meta fields but I do not think that is the solution to the problem. The fields are already created and Post My CF7 found them on two occasions but failed after that.

Update: There is an easy fix for making the posts publicly queryable. Use any custom post plugin to make the custom post type that you want and then map the CF7 fields to your existing post type. That way all the CF7 posts can be perfectly viewed from the URL.

The downside is that if you create custom meta fields, they do not show up in the plugin currently. So you can only map CF7 fields to default WordPress fields and that’s a big downside. So any help with making the custom meta fields visible in the plugin would be much appreciated.

P.S. I used Custom Post Type UI plugin to make the custom post type and then Advanced Custom Fields to make my custom meta fields.

I found a great fix for this, the trick is to use Advanced Custom Fields plugin to create new user profile fields and then use the default pre-fill functionality in contact form 7. I works perfectly.

Other plugins do not seem to be able to use the default CF7 pre-fill function due to the way they create the custom fields.

I would also really love to see this (I’m a pro user by the way). For instance if a custom field such as “interests” was created and filled at the time of registration.

If the user wanted to change this they can login to a profile age with a form that pre-fills the username & password and whatever new data they put into the other fields replaces the old data.

Contact Form 7 already has the functionality to pre-fill fields like username and password for logged in users. So it would be up to the plugin to check if the user name and password exist and if so, what ever data is entered in the other fields just rewrites the existing data.

That Would be Fantastic ??.

Thanks a lot Sebastien

In which particular plugin file should I paste this code?