Contact Form 7 – Conditional Fields

Descripción

Este plugin añade lógica condicional a Contact Form 7.

Si editas tu formulario de CF7, verás una etiqueta adicional llamada «Grupo de campos condicionales». Todo lo que pongas entre la etiqueta de inicio y fin estará oculto por defecto.
Una vez que hayas añadido el o los grupos de campos, haz clic en «Guardar» y ve a la pestaña «Campos condicionales» para crear una o más condiciones que hagan aparecer el o los grupos.

Cómo usar

Consulta este tutorial

Características principales

Compatibilidad para los campos obligatorios

Los campos obligatorios pueden usarse dentro de grupos ocultos sin causar problemas de validación.

Ocultar o mostrar información en los correos electrónicos con base en qué grupos son visibles

Los grupos condicionales ahora también pueden añadirse a los correos electrónicos.
Solo hay que envolver el contenido con las etiquetas [group-name] ... [/group-name].

Los grupos pueden anidarse

Los grupos pueden anidarse, tanto en el formulario como en el correo electrónico

Ejemplo de formulario:

[group group-1]
  [group group-inside-1]
    ...
  [/group]
[/group]

Ejemplo de correo electrónico:

[group-1]
  [group-inside-1]
    ...
  [/group-inside-1]
[/group-1]

Avanzado

Los usuarios avanzados pueden codificar las condiciones como texto plano en lugar de usar las cajas de selección, usando la vista de texto.

¿Necesitas más potencia?

Al igual que WordPress, la potencia de Contact Form 7 reside en su rico ecosistema de extensiones que se construyen sobre él. Sin embargo, puede ser difícil encontrar un conjunto de extensiones complejas que funcionen bien juntas.

Por eso he creado Conditional Fields Pro. Este añade algunas características poderosas a Contact Form 7 y garantiza que todo funcionará sin problemas con Conditional Fields.

Las características pro incluyen:

  • Campos repetibles (repetidores)
  • Formularios de múltiples pasos (multipasos)
  • Condiciones personalizadas con funciones de JavaScript
  • Operadores adicionales (mayor que, menor que, etc.)

¡Obtén Conditional Fields PRO!

Capturas

  • Los campos condicionales en acción
  • Definiendo reglas para mostrar u ocultar grupos de elementos de entrada en la interfaz del escritorio

Instalación

Por favor, consulta el procedimiento de instalación estándar para los plugins de WordPress.

Consulta este tutorial si no está seguro de cómo usar el plugin.

Preguntas frecuentes

El mensaje de correo electrónico no muestra los valores correctos o se envían valores incorrectos

Todos los nombres de campo deben ser únicos

Aunque tus campos nunca aparezcan al mismo tiempo, es importante saber que WPCF7CF no elimina los campos, simplemente los oculta. Así que todos los campos serán enviados cuando el formulario se envíe. Debido a esto, no deben haber dos campos que tengan el mismo nombre.

Forma incorrecta (2 elementos de entrada con el mismo nombre «a»):

[group group-1][select a "1" "2" "3"][/group]
[group group-2][select a "1" "2" "3"][/group]

Forma correcta (todos los grupos y campos tienen nombres únicos):

[group group-1][select a "1" "2" "3"][/group]
[group group-2][select b "1" "2" "3"][/group]

Todos mis grupos aparecen todo el tiempo y nunca se ocultan.

Razón #1: Error de JavaScript
Revisa la consola de tu navegador (F12) para ver si hay algún error de JavaScript. WPCF7CF carga sus scripts en la parte inferior de la página HTML, así que si algún error de JavaScript se produce antes de eso, el código no se ejecutará en la mayoría de los navegadores.
Antes de contactar con el foro de soporte, intenta determinar qué plugin o tema está causando el problema, desactivando gradualmente los plugins y cambiando el tema.

Razón #2: wp_footer() no está cargado
Comprueba si tu tema está llamando a la función wp_footer(). De forma típica esta función se llamará en el archivo footer.php de tu tema.
El código JavaScript de los campos condicionales se carga en wp_footer, por lo que una llamada a esta función es crucial. Si no hay tal llamada en tu tema, ve al archivo footer.php de tu tema y añade este código justo antes de la etiqueta de cierre </body>:
<?php wp_footer(); ?>

Reseñas

11 de abril de 2021
Pro-Version very recommandable, too. Allows multi-page-forms very easy and stable
9 de abril de 2021
First of all, I do appreciate all of the positive reviews, but for me, the fields are not hiding. However, one thing this plugin is lacking is the ability to add a button click that will show a hidden group. That would make it even better.
16 de marzo de 2021
This extension is really useful to my favourite contact plugin: CF7. Easy to use, fast and clean interface. Great work! Thanks for this solution!
Leer todas las 138 reseñas

Colaboradores y desarrolladores

«Contact Form 7 – Conditional Fields» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

«Contact Form 7 – Conditional Fields» ha sido traducido a 6 idiomas locales. Gracias a los traductores por sus contribuciones.

Traduce «Contact Form 7 – Conditional Fields» a tu idioma.

¿Interesado en el desarrollo?

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

Registro de cambios

2.0.2 (2021-04-06)

  • Fix bug: third-party required fields not triggering validation. Thanks @dedotombo!

2.0.1 (2021-03-31)

  • Force height:auto on groups. (Fixes regression errors with groups inside repeaters)
  • Allow more funky characters as conditional fields values (there was a problem with less than sign <)
  • Fix bug with hidden required file and multifile fields causing validation errors
  • Implemented extra tests so these errors cannot reoccur in future updates.

2.0 (2021-03-29)

  • WARNING! 2.0 requires at least Contact Form 7 version 5.4 to work!
  • Make plugin compatible with CF7 5.4
  • Modify wpcf7cf_generate_summary function, so it can be used without $_POST
  • fix animaton when showing group

1.9.16 (2021-03-09)

  • Make notice dismissable

1.9.15 (2021-03-03)

1.9.14 (2020-10-03)

  • PRO:Repeater: Hide Remove button initially when repeater has min:0
  • PRO:Multistep: Disable Next button while validating step.
  • IE11 compat: Fix classList bug (occured in IE11 if form contained SVG elements)

1.9.13 (2020-09-28)

  • IE11 compatibility: Add Array.from polyfill

1.9.12 (2020-09-24)

  • PRO:Multistep: add new event ‘wpcf7cf_step_invalid’, triggered after step validation failed. Example usage
  • PRO:Multifile: Fix bug where multifle* was not sending attachments

1.9.11 (2020-09-07)

1.9.10 (2020-08-19)

  • PRO: Fix multistep bug: general error message does not appear if step validation fails

1.9.9 (2020-07-29)

  • Fix bug when saving conditions from Text View
  • Probado con WP 5.5

1.9.8 (2020-07-20)

  • Make sure all posted data is analyzed after submitting (part of) a form. A recent update of CF7 stripped away some information, resulting in PHP Notices.

1.9.7 (2020-07-07)

  • corrige la compatibilidad con IE11

1.9.6 (2020-07-04)

  • PRO: Fixed bug: checkboxes and multiselect validation not working inside repeater

1.9.5 (2020-07-01)

  • PRO: Fixed bug: multistep forms interference with other forms after calling wpcf7cf.initForm()
  • PRO: Fixed bug: function operator no longer working.

1.9.4 (2020-06-23)

  • Fixed bug: JS error when conditonal fields settings where not saved manually by the user.

1.9.3 (2020-06-21)

  • Ignore conditions where group or field name does not exist, instead of throwing an error
  • Eliminado el aviso PHP relacionado con los nuevos ajustes
  • Something went wrong with SVN commit 1.9.1 and 1.9.2 (so although these version might show up, it’s not really a valid version)

1.9 (2020-06-21)

  • Mejoras de rendimiento
  • Added extra setting: «Conditional Fields UI». If you have a lot of conditions, set this to «Text mode» for better performance in the admin interface.
  • Improved styling on Conditional Fields Settings page
  • Improved docs
  • Improved the form tester
  • PRO: Multistep bug that was causing checkboxes and multiselect to not trigger validation errors
  • PRO: Summary added support for files, checkboxes and multiselect
  • Added test to ensure that normal view entries are always converted to text view correctly

1.8.7 (2020-06-01)

  • PRO: cambia el mecanismo de actualización automática
  • Algunas reprogramaciones menores de JS
  • Improved on some edge cases with equals "" and not equals ""
  • Suites de pruebas mejoradas.

1.8.6 (2020-04-18)

  • Fixed: accidentally packed the entire jQuery library in scripts.js
  • Cleaned up some console.logs that was still hanging around in the code.

1.8.5 (2020-04-17)

  • Probado con WP 5.4
  • corrige la multiselección
  • corrige el campo de archivo necesario dentro de multipasos
  • allow group names to contain . and : (https://github.com/pwkip/contact-form-7-conditional-fields/issues/46)
  • fix possible conflicts with require_once ‘init.php’ (https://wordpress.org/support/topic/conflict-with-theme-because-of-require_once/)
  • Created some unit tests and integration tests, so hopefully no more regression bugs from now on! (next step: automated CI before publish)
  • Got rid of warnings and notices when creating a new form.
  • Fix small clear_on_hide bug with select field (https://github.com/pwkip/contact-form-7-conditional-fields/issues/51)
  • PRO: fix «not empty» when using first_as_label in select field. (closes guthub issue #48)
  • PRO: fix error with nested repeater buttons text
  • PRO: new version of plugin_update_checker, compatible with PHP 7.3+

1.8.4 (2020-03-05)

  • PRO: Multistep: Improve autoscroll behavior (Tried to make it smoother and less annoying)
  • PRO: Multistep: Add wpcf7-not-valid class to input fields as needed after step-validation. Removed some other useless classes.

1.8.3 (2020-03-01)

  • Fix JS error on submit (reported by @wasi7186)
  • PRO multistep: On the last step of a multistep form, instead of cloning and hiding the submit button, we now simply move it to the next-step-container. This solves a compatibility issue with a third party recaptcha plugin (and probably some other plugins too)

1.8.2 (2020-02-27)

  • Small patch. Add a check in the ajaxComplete event, to make sure xhr.responseJSON is not null or undefined. (this caused a JS error on some websites)

1.8.1 (2020-02-23)

  • PRO: Bring form in initial state after submit, including going back to first step of multistep and resetting the initial number of sub-repeaters in each repeater.
  • PRO: New field: [summary]
  • PRO: Make form submission trigger next step (if not on last step)
  • PRO: Multistep: automatically scroll to top of form after moving to a different step.
  • PRO: Multistep: Replace h3 tag with div as step-title.
  • PRO: Made some small changes to the default multistep styles, for basic mobile friendly behaviour.
  • PRO: Make multistep compatibility with cf7-image-captcha plugin

1.8 (2020-02-03)

  • WPML compatibility: Force conditions to be an array. link

1.7.9 (2020-01-22)

  • PRO (01-02-20) Added quick fix for problem with [_format_date «d m Y»] inside repeater. link
  • (01-22-20) Fixed Ajax by adding global wpcf7cf variable to window.
  • Changed min PHP version to 5.6 (might still be compatible with 5.4, but I suspect some edge case errors with older versions of PHP)

1.7.8 (2019-11-26)

  • Updated/added Javascript events for groups, repeaters and multistep + added documentation
  • Fixed bug where using invalid regex as a value would give a JS error link
  • PRO Multistep: Added attribute to multistep data-current_step which holds the current step index. (can be used as css selector like this: div[data-current_step=1])
  • PRO Repeater: The string {{your-repeater_index}} inside a repeater called your-repeater will be replaced with the index of the current sub repeater. Check out the updated example

1.7.7 (2019-11-05)

  • PRO: Fix problem with parsing the «function» operator

1.7.6 (2019-11-01)

  • Fixed small compatibility problem with CF7 Smart Grid link
  • Fixed some more porblems with parsing conditions (regex changes)
  • Got rid of screen_icon notice on CF settings page

1.7.5 (2019-10-31)

  • Fixed bug in admin where settings got cleared if using some operators (mostly PRO operators)

1.7.4 (2019-10-29)

  • PRO: made repeater (80%) compatible with material-design-for-contact-form-7
  • PRO: made exclusive checkbox work with repeater fields
  • PRO: trigger events when a repeater adds fields: ‘wpcf7cf_repeater_added’ – and when a repeater removes fields: ‘wpcf7cf_repeater_removed’. Can be called with $('form').on('wpcf7cf_repeater_removed', function() { /*...*/ })
  • PRO: fixed bug with mutistep (formn did not work correctly if there were multiple forms on one page).

1.7.3 (2019-10-24)

  • removed @babel/polyfill. All seems to be working fine without it in IE11. JS file is now back to 25kb instead of 100kb.

1.7.2 (2019-10-24)

  • Bug fix: new javascript files where throwing errors. Should be okay now. (Also included JS source map for easier debugging)

1.7.1 (2019-10-23)

  • PRO: Added basic support for multistep. No options available yet. You can insert [step] tags inside your code. More info
  • Set up an NPM dev environment with babel and webpack. This means all the client side JS code will look super ugly, and it’s also more bytes. But the plus side is that the plugin should also work fine in older browsers now.
  • Probado con la versión 5.3 de WP

1.7 (2019-10-18)

  • code rewrite. Made code more testable by focusing more on a functional approach. Not completely finished yet, but getting there.
  • FIXED clear_on_hide not working for multi select github issue 35
  • PRO: FIXED github issue 34 – A real nest fest is now possible. You can put groups inside repeaters inside repeaters inside groups …
  • FIXED make clear_on_hide restore initial values instead of clearing github issue 31
  • WP-admin: Renamed «Import/Export» to «Text view». Conditions specified in the input fields are now semi-automatically synced with the text view.
  • Internal change: When saving conditions, instead of posting all the input fields, the input fields are added to the «text view» textarea, and only the textarea will be sent. This is to prevent issues with PHP max_input_vars

1.6.5 (2019-10-15)

  • Patched a minor security issue. From now on, only users with the ‘wpcf7_edit_contact_form’ capability will be able to reset the Conditional Fields settings to their defaults. Big thanks to Chloe from Wordfence for pointing this out!
  • Tested the plugin with WP version 5.2.4

1.6.4 (2019-07-04)

  • PRO: Repeater: Fixed invalid HTML for the remove button
  • Free: Initialize form.$groups as a new jQuery object instead of an empty array, in order to prevent exotic bugs in case $groups aren’t loaded by the time form.displayFields() is called. (https://wordpress.org/support/topic/typeerror-cannot-read-property-addclass-of-undefined-at-wpcf7cfform/)

1.6.3 (2019-07-04)

  • Removed the word «Pro» from the title in the free plugin

1.6.2 (2019-06-25)

  • Pequeños cambios en los botones del generador de etiquetas
  • Multistep bug fix. All group conditions are evaluated a second time after the page has fully loaded.
  • PRO: added new operator ‘function’, allowing you to write custom javascript functions to determine whether or not a group should be shown. link
  • PRO: fix bug with < (less than) operator

1.6.1 (2019-06-03)

  • JS refactoring and small compatibility fix after code rewrite.
  • FREE: Added «Get PRO» button under Contact > Conditional Fields

1.6 (2019-06-01)

  • Reescritura del código JS
  • PRO: permitir grupos dentro del repetidor
  • PRO: prepara el plugin para la versión PRO.

1.5.5 (2019-05-20)

  • Fixed and explained how to disable loading of the styles and scripts and only enable it on certain pages. More info
  • Made sure default settings get set after activating plugin, without the need to visit the Contact > Conditional Fields page first.
  • PRO: extended the repeater with min and max paramaters and the possibility to change the add and remove buttons texts
  • PRO: enabling the pro plugin will show a notification to disable the free plugin, instead of throwing a PHP error.

1.5.4 (2019-05-06)

  • Make sure scripts get loaded late enough (wp_enqueue_scripts priority set to 20), because there was a problem with multistep where the multistep script was changing a value after the cf script ran. https://wordpress.org/support/topic/1-5-x-not-expanding-selected-hidden-groups-with-multi-step-on-previous-page/

1.5.3 (2019-05-03)

  • Refix the fix from version 1.4.3 that got unfixed in version 1.5 somehow 🙄

1.5.2 (2019-05-03)

  • by reverting changes in 1.5.1, the possibility to load forms via AJAX was destroyed. So, from now on the wpcf7cf scripts will be loaded in the ‘wp_enqueue_scripts’ hook. Analogous with the WPCF7_LOAD_JS constant, a new constant is defined called WPCF7CF_LOAD_JS wich is set to true by default.

1.5.1 (2019-05-02)

  • revert changes: enqueue scripts in ‘wpcf7_contact_form’ hook instead of ‘wpcf7_enqueue_scripts’, because loading it in the latter would cause problems with plugins that disable WPCF7_LOAD_JS (like for example contact-form-7-paypal-add-on).

1.5 (2019-04-21)

  • Make it possible to load forms with AJAX. fixed github issue 25. updated docs
  • Massive code reorganization in scripts.js
  • Fixed bug that could appear after removing an AND condition.
  • solve WPCF7_ADMIN_READ_WRITE_CAPABILITY – https://github.com/pwkip/contact-form-7-conditional-fields/pull/16
  • disable part of the faulty remove_hidden_post_data function. – https://github.com/pwkip/contact-form-7-conditional-fields/pull/17
  • Fix «Dismiss notice» on Conditional Fields Settings page
  • use the «wpcf7_before_send_mail» hook instead of «wpcf7_mail_components» to hide mail groups. The wpcf7_before_send_mail hook is called earlier, so it allows to also hide groups in the attachment field and in messages.
  • Allow conditional group tags in success and error messages. https://github.com/pwkip/contact-form-7-conditional-fields/issues/23
  • duplicating a form will also duplicate conditions https://github.com/pwkip/contact-form-7-conditional-fields/issues/28

1.4.3 (2019-04-12)

  • Really fix clear_on_hide problem (https://wordpress.org/support/topic/clear_on_hide-still-not-working-right-after-1-4-2-update/)

1.4.2 (2019-04-10)

  • Disabled mailbox syntax errors if there are group tags present. (this is overkill, and should be changed if the necassary hooks become available) https://wordpress.org/support/topic/filter-detect_invalid_mailbox_syntax/
  • Checked issue: https://github.com/pwkip/contact-form-7-conditional-fields/issues/26 (nothing changed, but turns out to be working fine)
  • Fixed issue where mail_2 added extra lines in the email message. https://github.com/pwkip/contact-form-7-conditional-fields/issues/30
  • Made the clear_on_hide property a bit more useful (https://github.com/pwkip/contact-form-7-conditional-fields/issues/27)
  • Got rid of warning in PHP 7 (https://wordpress.org/support/topic/compatibility-warning-message-regarding-wpcf7_admin_read_write_capability/)
  • Fixed some javascript errors that appeared on non-CF7CF subpages of CF7
  • Probado WP versión 5.1.1

1.4.1 (2018-08-21)

  • Fixed some CSS issues (https://wordpress.org/support/topic/crash-view-admin-the-list-of-posts-entry/)
  • Dropped support for PHP version 5.2, now PHP 5.3+ is required to run the plugin. Let’s push things forward!
  • Added conditional group support to mail attachments field (https://github.com/pwkip/contact-form-7-conditional-fields/issues/22)
  • Añadido campo repetidor a la versión PRO.

1.4 (2018-08-15)

  • Added basic drag and drop functionality to the back-end so conditional rules can be rearranged.
  • Added possibility to create inline groups by adding the option inline. Example: [group my-group inline] ... [/group]
  • Added property clear_on_hide to clear all fields within a group the moment the group gets hidden. Example: [group my-group clear_on_hide] ... [/group]
  • Added AND conditions and added a bunch of other options in the PRO version (should be released very soon now)
  • Bug fix thanks to Aurovrata Venet (@aurovrata) https://wordpress.org/support/topic/bug-plugin-overwrite-cf7-hidden-fields/
  • Bug fix thanks to 972 creative (@toddedelman) https://wordpress.org/support/topic/conditional-fields-not-opening-using-radio-buttons/#post-10442923

1.3.4

  • pequeña corrección (https://wordpress.org/support/topic/wpcf7_contactform-object-is-no-longer-accessible/)

1.3.3

  • Changes tested with WP 4.7.5 and CF7 4.8
  • Changed the inner mechanics a bit to make the plugin more edge-case proof and prepare for future ajax support
  • Fix problems introduced by CF7 4.8 update
  • Because the CF7 author, Takayuki Miyoshi, decided to get rid of the ‘form-pre-serialize’ javascript event, the hidden fields containing data about which groups are shown/hidden will now be updated when the form is loaded and each time a form value changes. This might make the plugin slightly slower, but it is the only solution I found so far.
  • Pequeña corrección de fallo (https://wordpress.org/support/topic/php-depreciated-warning/#post-9151404)

1.3.2

  • Removed a piece of code that was trying to load a non existing stylesheet
  • Actualizadas las FAQ
  • Code rearangement and additions for the upcomming Conditional Fields Pro plugin

1.3.1

  • Fixed bug in 1.3 that broke everything

1.3

  • Fixed small bug with integration with Contact Form 7 Multi-Step Forms
  • Also trigger hiding/showing of groups while typing or pasting text in input fields
  • Added support for input type=»reset»
  • Añadidas animaciones
  • Added settings page to wp-admin: Contact > Conditional Fields

1.2.3

  • Make plugin compatible with CF7 Multi Step by NinjaTeam https://wordpress.org/plugins/cf7-multi-step/
  • Improve compatibility with Signature Addon some more.

1.2.2

  • Fix critical bug that was present in version 1.2 and 1.2.1

1.2.1

1.2

  • Made compatible with Contact Form 7 Multi-Step Forms
  • Small bug fix by Manual from advantia.net: now only considering fields which are strictly inside hidden group tags with form submit. Important in some edge cases where form elements get hidden by other mechanisms, i.e. tabbed forms.
  • Started work on WPCF7CF Pro, made some structural code modifications so the free plugin can function as the base for both plugins.
  • Eliminados algo de código de depuración
  • Actualizado el archivo readme

1.1

  • Added import feature
  • Added support for nested groups in email
  • Tested on WP version 4.7.2 with Contact Form 7 version 4.6.1

1.0

  • I feel that at this point the plugin is stable enough in most cases, so it’s about time to take it out of beta 🙂
  • Update JS en CSS version numbers
  • Fix PHP warning with forms that are not using conditional fields (https://wordpress.org/support/topic/conditional-formatting-error/)
  • Probado con WP 4.7.1

0.2.9

  • Re-added wpcf7_add_shortcode() function if wpcf7_add_form_tag() is not found, because some people claimed to get a «function not found» error for the wpcf7_add_form_tag function with the latest version of CF7 installed. (https://wordpress.org/support/topic/activation-issue-5/ and https://wordpress.org/support/topic/http-500-unable-to-handle-request-error-after-update/)
  • Fixed some PHP notices (https://wordpress.org/support/topic/undefined-index-error-in-ajax-response/)
  • Attempted to fix error with the CF7 success page redirects plugin (https://wordpress.org/support/topic/warning-invalid-argument-error-for-forms-without-conditional-fields/)

0.2.8

  • forgot to update version number in 0.2.7, so changing version to 0.2.8 now.

0.2.7

  • Added support for conditional fields in the email (2) field
  • Eliminadas algunas advertencias de PHP
  • Saving a form only once, directly after adding or removing conditions, caused conditional logic not to work. This is fixed now. Thanks to @cpaprotna for pointing me in the right direction. (https://wordpress.org/support/topic/no-more-than-3-conditional-statements/)
  • Fix validation error with hidden checkbox groups (https://wordpress.org/support/topic/hidden-group-required-field-is-showing-error/)

0.2.6

  • Fixed problems with exclusive checkboxes in IE (https://wordpress.org/support/topic/internet-explorer-conditional-exclusive-checkboxes/)

0.2.5

  • Changed deprecated function wpcf7_add_shortcode to wpcf7_add_form_tag as it was causing errors in debug mode. (https://wordpress.org/support/topic/wpcf7_add_shortcode-deprecated-notice-2/)
  • Removed the hide option and fixed the not-equals option for single checkboxes

0.2.4

  • Fixed bug that destroyed the conditional fields in email functionality

0.2.3

  • Added support for conditional fields in the other email fields (subject, sender, recipient, additional_headers). Thanks @stevish!
  • WP 4.7 broke the required conditional fields inside hidden groups, implemented in version 0.2. Thanks again to @stevish for pointing this out.
  • Got rid of checking which groups are hidden both on the front-end (JS) and in the back-end (PHP). Now this is only done in the front-end.
  • Plugin probado con WP 4.7

0.2.2

  • Prevent strict standards notice to appear while adding new group via the «Conditional Fields Group» popup.
  • Only load cf7cf admin styles and scripts on cf7 pages.
  • groups are now reset to their initial states after the form is successfully submitted.

0.2.1

  • Bug fix: arrow kept spinning after submitting a form without conditional fields. (https://wordpress.org/support/topic/version-0-2-gives-a-continues-spinning-arrow-after-submitting/)
  • Removed anonymous functions from code, so the plugin also works for PHP versions older than 5.3.
  • Suppress errors generated if user uses invalid HTML markup in their form code. These errors could prevent form success message from appearing.

0.2

  • Added support for required conditional fields inside hidden groups. A big thank you to @stevish for implementing this.
  • Added support for conditional fields in the email messages. This one also goes entirely to @stevish. Thanks man!
  • Added @stevish as a contributer to the project 🙂
  • Fix form not working in widgets or other places outside of the loop. Thanks to @ciprianolaru for the solution (https://wordpress.org/support/topic/problem-with-unit_tag-when-not-in-the-loop-form-not-used-in-post-or-page/#post-8299801)

0.1.7

  • Fix popup warning to leave page even tough no changes have been made. Thanks to @hhmaster2045 for reporting the bug. https://wordpress.org/support/topic/popup-warning-to-leave-page-even-though-no-changes-have-been-made
  • Added export option for easier troubleshooting.
  • Don’t include front end javascript in backend.

0.1.6

  • made compatible with wpcf7-form-control-signature-wrap plugin https://wordpress.org/support/topic/signature-add-on-not-working

0.1.5

  • fixed PHP notice thanks to @natalia_c https://wordpress.org/support/topic/php-notice-80
  • probado con WP 4.5.3

0.1.4

  • Prevent conflicts between different forms on one page.
  • Prevent conflicts between multiple instances of the same form on one page. (https://wordpress.org/support/topic/bug-153)
  • Changed regex to convert [group] tags to <div> tags, as it was posing some conflicts with other plugins (https://wordpress.org/support/topic/plugin-influence-cf7-send-button-style)

0.1.3

  • Removed fielset, id and class attributes for group tags, because they weren’t used anyway and broke the shortcode
  • If extra attributes are added to the group shortcode, this will no longer break functionality (even though no attributes are supported)

0.1.2

  • Make code work with select element that allows multiple options.
  • Only load javascript on pages that contain a CF7 form

0.1.1

Fixed bug with exclusive checkboxes (https://wordpress.org/support/topic/groups-not-showing)

0.1

Primera versión