Contact Form 7

Omschrijving

Met Contact Form 7 kan men meerdere contactformulieren beheren en heeft men de mogelijkheid het formulier en de e-mailberichten flexibel met eenvoudige opmaak aan te passen. Het formulier ondersteunt Ajax-submit, CAPTCHA, Akismet-spamfilteren en zo meer.

Documentatie & ondersteuning

Men kan uitgebreide documentatie, FAQ en meer gedetailleerde informatie vinden over Contact Form 7 op contactform7.com. Als u niet alle antwoorden kunt vinden in de documentatie, FAQ’s enz., dan kunt u het supportforum raadplegen op WordPress.org. Mochten er geen onderwerpen te vinden zijn dat met uw vraag te maken hebben, dan kunt u een nieuwe vraag stellen op het forum.

Contact Form 7 heeft uw hulp nodig

Het is lastig de ontwikkeling en support van deze gratis plugin door te laten gaan zonder bijdragen van gebruikers als u. Als u met plezier gebruik maakt van Contact Form 7 en de plugin handig vindt, overweeg dan een donatie te doen. Uw donatie moedigt de toekomstige ontwikkeling aan en zorgt voor betere support.

Privacy Notices

With the default configuration, 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.

If you activate certain features in this plugin, the contact form submitter’s personal data, including their IP address, may be sent to the service provider. Thus, confirming the provider’s privacy policy is recommended. These features include:

Aanbevolen plugins

De volgende plugins worden aanbevolen door gebruikers van Contact Form 7:

  • Flamingo door Takayuki Miyoshi – Met Flamingo is het mogelijk om verstuurde berichten van contactformulieren in de database op te slaan.
  • Bogo door Takayuki Miyoshi – Bogo is een rechttoe-rechtaan meertalige plugin die u geen hoofdpijn bezorgt.

Vertalingen

U kunt Contact Form 7 vertalen m.b.v. translate.wordpress.org.

Schermafdrukken

  • screenshot-1.png

Installatie

  1. Upload de volledige contact-form-7-map naar de /wp-content/plugins/-directory.
  2. Activeer de plugin d.m.v. het menu ‘Plugin’ in WordPress.

U zult het ‘Contact’-menu vinden in de WordPress-beheerdersconsole.

Voor basaal gebruik kunt u kijken op de pluginwebsite.

FAQ

Heeft u vragen of problemen met Contact Form 7, maak dan gebruik van één van de ondersteuningsmogelijkheden.

  1. Documentatie
  2. FAQ
  3. Supportforum

Support

Beoordelingen

Rollback to Version 5.0.5

Was surprised at how poorly the upgrade did… just rolled back to Version 5.0.5 and the checkbox / I’m not a robot is back.

Can’t quite understand why the upgrade was done?

I’m leaving the 5 star rating for 5.0.5. With the upgrade, I was flooded with junk.

Good plugin (read if you get spam after update)

After serving me well for years, today I updated the plugin to version 5.1, which requires version 3 of reCAPTCHA, yet silently fails (you just start getting tons of spam) if you don’t have the new v3 API keys.

My problem was that I had forgotten I was even using reCAPTCHA, so I ignored the generic verbiage (yes, there are instructions and a FAQ), and I was just surprised and a bit suspicious after getting tons of spam after the update. Because of the spam wave I thought the plugin had been hacked.

Alas, the plugin does not show you any warnings about you still having the old reCAPTCHA v2 setup enabled, it just silently fails and you start getting tons of spam. I think the author could address this, because as the sudden flow of one-star ratings show, this is not clear. The “instructions” are there, sure, but they are generic. As part of the plugin upgrade, I think there should be a specific warning, reminding you that you were actually using reCAPTCHA, and that it’s time to go to google.com/recaptcha and get new v3 API keys. And it should show this warning whenever you open your admin controls, to remind you that you are still using legacy settings.

The plugin that sabotaged itself

This was a brilliant plugin that my company had been using on dozens of sites for many years without any issues at all. Then the developer pushed a devastating update that broke spam filtering for everybody. It actually deleted our reCAPTCHA v2 keys from the database and left every site open to attack by default. If you weren’t paying close attention, you wouldn’t have even known to upgrade to v3 keys at all.

Even after you upgrade to v3, most of our sites experienced massive amounts of spam getting through, with the added kick in the pants of having a Google advertisement prominently displayed in the lower right-hand corner of every page, often overlapping essential website content. This was placed there without notification or consent. It just shows up once you insert v3 keys into the plugin.

The author’s recent comments that reCAPTCHA v3 is a “great masterpiece” and that he would not even consider adding v2 support back in make this latest update an absolute disaster with no hope of moving forward in a positive direction.

In short, this was a great plugin that grew to over 5 million installs for good reason. Then the author sabotaged himself and now we will get to watch its slow miserable decline. Sad to see it go. Hope he gets the message and rights the ship before it’s too late. I’d love to have a reason to update this review to reflect the many positive aspects about this plugin. But in its present state, I cannot recommend it to anybody in good faith.

Here’s another 1 star for Recaptcha v3

Started getting a lot of spam and came to find out that we are now being forced to use Recaptcha v3.

Already uninstalled this ancient plugin from our other sites. This was the last one and today it is gone also.

Lees alle 1.453 beoordelingen

Bijdragers & ontwikkelaars

“Contact Form 7” is open source software. De volgende personen hebben bijgedragen aan deze plugin.

Bijdragers

“Contact Form 7” is vertaald in 52 talen. Dank voor de vertalers voor hun bijdragen.

Vertaal “Contact Form 7” naar jouw taal.

Interesse in ontwikkeling?

Bekijk de code, haal de SVN repository op, of abonneer je op het ontwikkellog via RSS.

Changelog

Voor meer informatie zie de release notes.

5.1

  • Introduces the Constant Contact integration module.
  • Updates the reCAPTCHA module to support reCAPTCHA v3.
  • Adds Dark Mode style rules.

5.0.5

  • Fixes the inconsistency problem between get_data_option() and get_default_option() in the WPCF7_FormTag class.
  • Suppresses PHP errors occur on unlink() calls.
  • Introduces wpcf7_is_file_path_in_content_dir() to support the use of the UPLOADS constant.

5.0.4

  • Specifies the capability_type argument explicitly in the register_post_type() call to fix the privilege escalation vulnerability issue.
  • Local File Attachment – disallows the specifying of absolute file paths referring to files outside the wp-content directory.
  • Config Validator – adds a test item to detect invalid file attachment settings.
  • Fixes a bug in the JavaScript fallback function for legacy browsers that do not support the HTML5 placeholder attribute.
  • Acceptance Checkbox – unsets the form-tag’s do-not-store feature.

5.0.3

  • CSS: Applies the “not-allowed” cursor style to submit buttons in the “disabled” state.
  • Acceptance Checkbox: Revises the tag-generator UI to encourage the use of better options in terms of personal data protection.
  • Introduces wpcf7_anonymize_ip_addr() function.
  • Introduces the consent_for:storage option for all types of form-tags.

5.0.2

  • Added the Privacy Notices section to the readme.txt file.
  • Updated the Information meta-box content.
  • Use get_user_locale() instead of get_locale() where it is more appropriate.
  • Acceptance Checkbox: Reset submit buttons’ disabled status after a successful submission.

5.0.1

  • Fixed incorrect uses of _n().
  • Config validation: Fixed incorrect count of alerts in the Additional Settings tab panel.
  • Config validation: Fixed improper treatment for the [_site_admin_email] special mail-tag in the From mail header field.
  • Acceptance checkbox: The class and id attributes specified were applied to the wrong HTML element.
  • Config validation: When there is an additional mail header for mailboxes like Cc or Reply-To, but it has a possible empty value, “Invalid mailbox syntax is used” error will be returned.
  • Explicitly specify the fourth parameter of add_action() to avoid passing unintended parameter values.
  • Check if the target directory is empty before removing the directory.

5.0

  • Additional settings: on_sent_ok and on_submit have been removed.
  • New additional setting: skip_mail
  • Flamingo: Inbound channel title changes in conjunction with a change in the title of the corresponding contact form.
  • DOM events: Make an entire API response object accessible through the event.detail.apiResponse property.
  • HTML mail: Adds language-related attributes to the HTML header.
  • File upload: Sets the accept attribute to an uploading field.
  • Introduces the WPCF7_MailTag class.
  • Allows aborting a mail-sending attempt using the wpcf7_before_send_mail action hook. Also, you can set a custom status and a message through the action hook.
  • Acceptance checkbox: Allows the specifying of a statement of conditions in the form-tag’s content part.
  • Acceptance checkbox: Supports the optional option.
  • New special mail tags: [_site_title], [_site_description], [_site_url], [_site_admin_email], [_invalid_fields], [_user_login], [_user_email], [_user_url], [_user_first_name], [_user_last_name], [_user_nickname], and [_user_display_name]
  • New filter hooks: wpcf7_upload_file_name, wpcf7_autop_or_not, wpcf7_posted_data_{$type}, and wpcf7_mail_tag_replaced_{$type}
  • New form-tag features: zero-controls-container and not-for-mail