mamibe

CF7’s documentation backs my process description:
https://contactform7.com/file-uploading-and-attachment/

Still, I could not notice the temporary file saves with 3mb test data.

You should better use Form to post. It supports CF7 and is well documented.

Even after reading the sourcecode of this plugin here, I am not sure how it is supposed to work.

Because Contact Form 7 uses the custom posttype, you can easily export and import all forms with WordPress’ internal tools.

This will give you a WXR file, which is basically a XML file. You can now convert it to JSON with frankbille’s golang tool go-wxr-to-json-app or convert it online

A created a sample JSON for your consideration. It can still be tweaked for readibility and external editing, but this is a good start.

It should be rather easy to implement. I checked the database structure of the forms that Contact Form 7 creates:

• There is a custom post type wpcf7_contact_form
• Each form is a post, the post_title
• In the table wp_postmeta there are some related entries which are all linked to the post_id
• There are 6 setting entries per form, here are the corresponding meta_keys:

• _form – here you find the form itself in the same way you edit it in the backend with all [text*] and <p> tags
• _mail – serialized PHP with all mail settings
• _mail2 – see above
• _messages – PHP serialized messages
• _additional_settings – in cleartext as in the backend
• _locale – such as de_DE

• All meta data gets inserted into the posts field post_content, when you update the form, this content updates as well
• The different setting entries are separated by empty lines and occational 0s in the post_content

If you would not have the data in both the wp_postmeta and wp_post, all you would have to do to get a JSON/YAML export/import would be to pull that data from the database, transfrom and to the structured text and save it.

Maybe you can help me understand why the data is saved in both places and which one is the one to change it programmatically.

EDIT 1:
The form still works when you delete the data from post_content so maybe it is just a backup!?

I use CF7 on a job application plattform where the FROM is always from my domain but the TO is always the mail address of the company. So I have hundreds of different TO addresses. And no, I am in no way sending SPAM. This is the intended usage. I use Sendgrid for email delivery as a drop in replacement for wp_mail and my Sendgrid rating is 99%. So, obviously this new validator really does not take such a business logic in consideration and thinks that I do something wrong.

Yes, a very irritating error. All my forms now show errors, but they all work. Right now I just ignore it. This improvement needs some more thought to really help anyone.

Ah, that is great news. As long as the plugin does not track users via cookie, there should be no problem with using it in Germany.

It is actually two issues that are not directly linked.

1. You must ensure that real IP addresses are not recorded
2. You must give visitor an option to opt out from all tracking that is done via cookies or plugins

Hence, “Hashed IP” solves issue 1, but not issue 2.

Splendid, that worked! Thanks a million.