Formulario de contacto 7

Descripción

Formulario de contacto 7 puede gestionar múltiples formularios de contacto, además, puedes personalizar el formulario y el contenido de los correos electrónicos de manera sencilla mediante un simple marcado. El formulario soporta envíos por Ajax, CAPTCHA, filtrado de spam de Akismet y mucho más.

Documentación y soporte

You can find docs, FAQ and more detailed information about Contact Form 7 on contactform7.com. If you were unable to find the answer to your question on the FAQ or in any of the documentation, you should check the support forum on WordPress.org. If you can’t locate any topics that pertain to your particular issue, post a new topic for it.

Formulario de contacto 7 necesita de tu apoyo

It is hard to continue development and support for this free plugin without contributions from users like you. If you enjoy using Contact Form 7 and find it useful, please consider making a donation. Your donation will help encourage and support the plugin’s continued development and better user 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:

Plugins recomendados

Los siguientes plugins están recomendados para usuarios de Contact Form 7:

  • Flamingo por Takayuki Miyoshi – Con Flamingo, puedes guardar en la base de datos los mensajes enviado mediante formulario de contacto.
  • Bogo por Takayuki Miyoshi – Bogo es un plugin multi idioma que no causa jaquecas.

Translations

You can translate Contact Form 7 on translate.wordpress.org.

Capturas de pantalla

  • screenshot-1.png

Instalación

  1. Sube la carpeta completa de contact-form-7 al directorio /wp-content/plugins/.
  2. Activa el plugin a través del menú de ‘Plugins’ de WordPress.

Encontrarás el menú “Contacto” en el panel de administración de tu WordPress.

For basic usage, you can also have a look at the plugin web site.

FAQ

¿Tienes preguntas o problemas con Contact Form 7? Utiliza los canales de soporte correctos.

  1. Docs
  2. FAQ
  3. Support Forum

Support

Opiniones

reCAPTCHA V3が効いていない

最新にバージョンにしたら reCAPTCHA V3 にしろとなっていたのでしたのはいいが、まったく効いておらず、BOTのSPAMが届くようになってしまいました。
はっきり言って、このバージョンは使い物になりません。

Catastrophic update

This plugin has always been awesome, until the 5.1 update where recaptcha v3 was forced. Not only is the v3 intrusive with its fixed badge and the amount of data collected, but there is also a bug in the plugin that makes spam protection no longer working at all. This is probably the worst decision ever made by the plugin developer. This update does not consider users, no warning is given before the update… Yet it completely breaks the forms that worked well with v2! I sincerely hope that the developer will make the right choice and restore the v2 that worked very well. I understand it’s a free plugin, but you can’t do that when you know that millions of sites are using it… I will give 5 stars back when this regrettable mistake will be corrected.

Backwards incompatible changes are not a thing today

Updating to 5.1 broke all sites with recaptcha. Because the author decided we all need to for some reason update to the Recaptcha v3.

First it doesn’t work with old Recaptcha keys (because v3 keys are incompatible with v2).

Second it broke the UI. Now all web pages with V3 recaptcha has a recycling badge fixed positioned on the bottom right! The users does not understand what that is. We developers do, but the users don’t. Having a recycling badge fixed on the bottom right of all pages is really bad idea.

Naturally plugin that is installed on 5 million sites needs to be conservative on changes. There can’t be backwards incompatible changes that breaks the UI or the spam prevention.

Please add the recaptcha v2 support back in.

We need some information now!

Dear Takayuki Miyoshi,

please post some information comment about the future of this Plugin as soon as possible!

Will you add the possibility to let the website-administrator decide if he likes to use recapcha 2 or recapcha 3? (In this case we can wait on 5.0.5 for an update.)

Or will you keep the plugin using the bad working recapcha 3 with its annoying advertisements on every page? (In this case most of your users have to search for an other plugin.)

…but we need some information now!

They are forgetting their users!

If you do not care about us, your users, it’s time to look for other options … The latest updates are forcing us all to migrate to something that is not yet good for use!

WARNING DON’T UPDATE TO 5.1!

Very bad update! 5.1 forces us to change to ReCaptcha v3 BUT there’s a bug in 5.1 which stops this working. My clients are now getting tons of spam and are furious. We need this fixed – really fast.

Leer los 1,476 comentarios

Colaboradores & Desarrolladores

“Formulario de contacto 7” es software de código abierto. Las siguientes personas han contribuido a este plugin.

Colaboradores

“Formulario de contacto 7” ha sido traducido en 53 idiomas. Gracias a los traductores por sus contribuciones.

Traduce & #8220;Formulario de contacto 7” a tu idioma.

¿interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN , o suscríbete al log de desarrollo por RSS .

Historial de cambios

For more information, see Releases.

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