Ref: https://developers.google.com/style/capitalization#capitalization-in-titles-and-headings_1

See Date/Time component improvements in WordPress 5.3

Related support topic: Bug with RTL languages on input fields with numbers and spaces

Code-style input like URL, email or telephone number should be displayed in Left-to-Right direction. This is true even in languages that are written in Right-to-Left direction like Hebrew or Arabic.

This is not a problem in most cases because the CSS stylesheet used on the site applies appropriate direction style rules, but some WordPress themes don't care about it. It is safer to set such rules in the plugin's stylesheet by default.

Based on a request posted in the support forum.

Also doing_it_wrong notice for the cases the $mail_tag isn't given and comments that clarify the arguments are necessary.

For example, if you have modules/recaptcha/recaptcha.php, the mod file is loaded preferentially. This makes it possible to have modules of more complex structure.

WPCF7_ContactForm::additional_setting() returns an array. It would be useful to have a shortcut method that returns the first item of the array.

Improve the telephone number pattern in wpcf7_is_tel().

Just converting this wp.org forum thread into an issue.

Some people have already written Contact Form 7 blocks (e.g. this one), which should be easy to add to your plugin. Given WordPress core's growing emphasis on blocks, doing this becomes more and more needed every day.

Use PHP time() instead.

See https://make.wordpress.org/core/2019/09/23/date-time-improvements-wp-5-3/

Instead the mail-tag appears as-is.

As WPCF7_FormTag::get_option() returns false when the option is not set.

When providing a form-tag field with a URL, the server makes a DNS query to that URL.

A form with the following form-tag:
[text* textfield akismet:author placeholder "ABC"]

If I enter an URL (http://www.example.org) in the input field "textfield" the server makes a DNS query for www.example.org. Why is that? This doesn't feel like something the plugin should do but when I'm looking for a cause I can't find anything else causing this to happen.

I've tried to locate where in the plugin code this would occur but can't find anything that would cause this behavior. I want to make sure if this is an issue with the plugin.

There have been many updates since the last time I modified the module.

https://v3.developer.constantcontact.com/api_guide/release_notes.html

hash_equals()

Currently it is affected by PHP timezone.

• Update Version and the WPCF7_VERSION constant to 5.1.9 in wp-contact-form-7.php
• Update Stable tag to 5.1.8 in readme.txt
• Add 5.1.9 change log to readme.txt

To make it consistent with apply_filters( 'wpcf7_special_mail_tags' ) in includes/mail.php.

Hi @takayukister

I used Version 5.2.1 and it produced an error:
PHP Fatal error: Uncaught Error: Call to a member function to_array() on null in ... .../public_html/wp-content/plugins/contact-form-7/includes/rest-api.php:397

Would you please have a look?

Thanks

• Update Requires at least in readme.txt and the WPCF7_REQUIRED_WP_VERSION constant in wp-contact-form-7.php to 5.3
• Update Version and the WPCF7_VERSION constant in wp-contact-form-7.php to 5.2
• Update Stable tag in readme.txt to the current stable version (5.1.9)
• Add 5.2 change log to readme.txt

• Update Version and the WPCF7_VERSION constant in wp-contact-form-7.php to 5.2.2
• Add 5.2.2 change log to readme.txt

https://github.com/takayukister/contact-form-7/blob/5c960f802304db9b5a149649f2e420f975d6d5b4/includes/js/scripts.js#L197

• Avoid duplicated message announcement

Related topic: https://wordpress.org/support/topic/accessibility-alert-problem/

• Add aria-live to screen reader response area

wp_basename()

Ref: ID attribute value are used multiple times in "Custom Field" form

The latest release (5.2) is returning an empty response alert field (with red border) in our Avada theme

<div class="fusion-alert alert custom alert-custom fusion-alert-center wpcf7-response-output fusion-alert-capitalize alert-dismissable" style="border-width:1px;"><button type="button" class="close toggle-alert" data-dismiss="alert" aria-hidden="true">×</button><div class="fusion-alert-content-wrapper"><span class="fusion-alert-content"></span></div></div>

This is not displayed after we rolled back to the (5.19) previous release.

In Flamingo 2.2, the id property of Flamingo_Contact and Flamingo_Inbound_Message objects has become a private property, and id() is recommended to use as an alternative.

If it's missing you'll see a PHP notice like this:

PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>contact-form-7/v1/contact-forms/(?P<id>\d+)/feedback</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback.

For details about permission_callback, see the REST API Handbook.

WordPress 5.4.2 has introduced a new filter hook that just works as the existing set-screen-option hook as part of security enhancement. This change also causes a minor issue that Number of items per page in the Screen Options is not saved. To fix the issue, support both of the set_screen_option_{$option} and set-screen-option hooks. The filter registration for the set-screen-option hook will become unnecessary when the required WP version rises to 5.4.

The wpcf7_ajax_json_echo and wpcf7_ajax_onload filter hooks used in includes/rest-api.php have a very old origin (WP REST API didn't exist at the time) and now they sound weird and too different from what they are in reality.

So, let's rename them as:

• wpcf7_ajax_json_echo => wpcf7_feedback_response
• wpcf7_ajax_onload => wpcf7_refill_response

Keep old hooks available for backward compatibility.

Role is unchangeable during a play, and all the men and women are merely players.

• Add 5.1.8 change log to readme.txt
• Update Version and the WPCF7_VERSION constant to 5.1.8 in wp-contact-form-7.php

Use DOM events instead.

Following https://akismet.com/development/api/#comment-check

• Update the copyright year in license.txt to 2007-2020
• Revise readme.txt based on the documentation style guide
  • Use sentence case for headings
  • Use ** to wrap a menu item
  • Use ` to wrap a code in text
• Add 5.1.7 change log to readme.txt
• Update Tested up to (5.4)
• Update Version and the WPCF7_VERSION constant to 5.1.7 in wp-contact-form-7.php

We need that code at: wp-content/plugins/contact-form-7/modules/recaptcha.php, line 78 described here: https://wordpress.org/support/topic/error-grecaptcha-execute-is-not-a-function/#post-12658099

At the moment Contact Form 7 loads Scripts & Styles on every page load on the front end. Realistically the contact form is only used on a few pages.

I would suggest loading the scripts and styles only on pages where the shortcode is included.

WordPress provided two functions to include a script / style:

wp_register_script and wp_enqueue_script
wp_register_style and wp_enqueue_style

The register function just register the script / style and does not load it on the frontend. If you later call enqueue with just the same handle, it will load the script / style on the frontend.

I would suggest changing all enqueue here: https://github.com/takayukister/contact-form-7/blob/master/includes/controller.php to register and call wp_enqueue_script( 'contact-form-7' ) and wp_enqueue_style( 'contact-form-7' ) if the shortcode is included: https://github.com/takayukister/contact-form-7/blob/master/includes/contact-form-functions.php#L93

It's no problem to run wp_enqueue_script with the handle multiple times and works great in the shortcode function.

Ref: https://core.trac.wordpress.org/changeset/47156

Filters hooked to wpcf7_mail_tag_replaced and wpcf7_mail_tag_replaced_{$type} are not applied when get_posted_data() returns null. This is unintended.

• Update Stable tag in readme.txt to the current stable version (5.2)
• Update Version and the WPCF7_VERSION constant in wp-contact-form-7.php to 5.2.1
• Update Tested up to in readme.txt to 5.5
• Add 5.2.1 change log to readme.txt