Bug: date format not working in 6.2

  • rosemaryik

    (@rosemaryik)


    3 days, 23 hours ago

    Upgraded to WordPress 7.1.3 and then Updated Contact Form 7 from 6.1.7 to 6.2.

    The Date field is not working with a date picker anymore. The issue happens on the docs page. Just select a date from the popup and you get the error Please enter a date in YYYY-MM-DD format.

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • meh1936

    (@meh1936)

    3 days, 12 hours ago

    I am also seeing this issue. Reverting to 6.17 resolved it for now.

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    3 days, 5 hours ago

    Where can we see the website in question?

    Thread Starter rosemaryik

    (@rosemaryik)

    2 days, 22 hours ago

    I reverted the update because I need it working but I provided a link to the date field example on the plugin’s documentation where it’s also happening. https://contactform7.com/date-field/

    Steps to reproduce on the documentation page are:

    • Click the date picker icon,
    • Select a date,

    You’ll see the message.

    • This reply was modified 2 days, 22 hours ago by rosemaryik.
    Plugin Author Takayuki Miyoshi

    (@takayukister)

    2 days, 8 hours ago

    Which browser do you use?

    Thread Starter rosemaryik

    (@rosemaryik)

    2 days, 7 hours ago

    I used Chrome but also same behavior in Safari and Firefox as well. If it helps I am on a Mac.

    I also tested in Safari on my iPhone and got the same behavior.

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    2 days, 5 hours ago

    Which date exactly did you select?

    Thread Starter rosemaryik

    (@rosemaryik)

    2 days ago

    I didn’t pay attention it was different each time I think. So trying again:

    First time: (selected from datepicker) 10/14/2026 – same behavior

    Second time: (selected from datepicker) 3/5/2013 – same behavior

    Third time: (typed in value instead of datepicker) 02/04/2023 – same behavior

    Not sure if it matters, but maybe, I’m in the US and America/New_York timezone.

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    1 day, 8 hours ago

    OK. Can you please share screenshots that include the inputs and errors?

    sergialarconrecio

    (@sergialarconrecio)

    23 hours, 22 minutes ago

    Update: Issue resolved — Satenet theme conflict identified

    Hi Takayuki Miyoshi @takayukister ,

    Thank you for your response and suggestions.

    I can now confirm that the issue has been resolved. After extensive debugging using WP-CLI, I identified the exact cause.

    The problem was a compatibility conflict between Contact Form 7 6.2.1 and the Satenet WordPress theme by Zozothemes.

    Root cause:

    The Satenet theme contains two functions in:

    wp-content/themes/satenet/inc/template-functions.php

    • satenet_search_post() — line 114
    • satenet_search_page() — line 122

    These functions are attached to pre_get_posts and modify the post type whenever $query->is_search is true.

    Since Contact Form 7 6.2 includes the s parameter in its administrative form-list query, the theme was overriding wpcf7_contact_form with the regular WordPress post type.

    This explains the exact symptoms:

    • The admin list displayed 8 empty rows.
    • Form titles were missing.
    • Edit links pointed to post=0.
    • The actual contact forms remained intact in the database.

    Verification:

    Using WP-CLI, the normal query returned 8 regular WordPress posts instead of contact forms.

    Running the same query with wp --skip-themes correctly returned 13 contact forms with valid IDs and titles.

    I then applied a temporary fix through WPCode, removing the Satenet search callbacks during admin_init:

    remove_action( 'pre_get_posts', 'satenet_search_post', 10 );

    remove_action( 'pre_get_posts', 'satenet_search_page', 10 );

    Result: Contact Form 7 now displays the 13 contact forms correctly, with their original titles and working Edit links.

    Clearing LiteSpeed Cache and expired WordPress transients had not resolved the issue.

    The permanent fix should be implemented by the Satenet theme developer, restricting these search functions to frontend queries.

    I am sharing this finding in case other users experience the same problem.

    Thank you again for your assistance.

Viewing 9 replies - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.