• Dear support volunteers,

    In CF7 5.3.2 the required field function isn’t working when I also use a placeholder for this field. Could somebody please quickly check on their installation if you get the same?

    In example:
    For design (space) reasons I prefer
    [text* city placeholder "city*"]
    over
    <label> City* [text* city] </label>

    When I use a placeholder, CF7 simply works like it is not a required field. Is this intended behavior, or might this be because an incompatible other plugin that I’m using (i.e. I’m using Contact Form 7 Conditional Fields Pro and Flamingo), or is this a small bug in CF7?
    Thanks in advance for your time!

    • This topic was modified 3 years, 10 months ago by hugob1979.

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Takayuki Miyoshi

    (@takayukister)

    What other plugins and theme do you use on the site?

    Thread Starter hugob1979

    (@hugob1979)

    Hi Takayuki,

    Thanks for your quick reply! I see my collegae Tasmara posted the same question, we are sorry for that. With corona and all working from home sometimes things happen twice ??

    Here are the answers your questions.

    ### Begin System Info ###

    — WordPress Configuration

    Version: 5.6
    Language: en_US
    Permalink Structure: /%category%/%postname%/
    Active Theme: Satellite7 3.1
    Show On Front: page
    Page On Front: Homepage (#2)
    Page For Posts: Unset
    Remote Post: wp_remote_post() works
    Table Prefix: Length: 3 Status: Acceptable
    WP_DEBUG: Disabled
    Memory Limit: 40M
    Registered Post Stati: publish, future, draft, pending, private, trash, auto-draft, inherit, request-pending, request-confirmed, request-failed, request-completed, flamingo-spam, paused, active, queued, finished, autoresponder

    — Must-Use Plugins

    Asset CleanUp Pro: Plugin Filtering: 1.0
    installatron_hide_status_test.php:

    — WordPress Active Plugins

    Asset CleanUp: Page Speed Booster: 1.3.7.3
    Asset CleanUp Pro: Page Speed Booster: 1.1.8.7
    Classic Editor: 1.6
    Contact Form 7: 5.3.2
    Contact Form 7 Conditional Fields Pro: 1.9.14
    Contact Form 7 Shortcode Enabler: 1.1
    Content Views: 2.3.4
    Content Views Pro: 5.8.4.1.1
    Cookie Notice: 1.3.2
    Envato Market: 2.0.6
    Flamingo: 2.2.1
    Helper Lite for PageSpeed: 3.0.6
    Hotjar: 1.0.9
    Invisible reCaptcha: 1.2.3
    LayerSlider WP: 6.11.2
    Limit Login Attempts Reloaded: 2.19.1
    Mailster – Email Newsletter Plugin for WordPress: 2.4.16
    Mailster Contact Form 7: 1.4
    Mailster Multi SMTP: 1.3
    Perfect Images + Retina: 6.1.2
    Popup Maker: 1.15.0
    Really Simple SSL: 4.0.6
    Redirection for Contact Form 7: 2.3.3
    Safe SVG: 1.9.9
    Satellite Core: 1.0.6
    Site Kit by Google: 1.24.0
    Team Showcase with Slider: 3.0
    WordPress Carousel: 2.1.16
    WordPress Importer: 0.7
    WP FAQ: 3.4
    WP Fastest Cache: 0.9.1.4
    WP Fastest Cache Premium: 1.5.9
    Yoast SEO: 15.6.2

    — WordPress Inactive Plugins

    — Webserver Configuration

    PHP Version: 7.2.34
    MySQL Version: 5.7.28
    Webserver Info: Apache/2

    — PHP Configuration

    Memory Limit: 256M
    Upload Max Size: 64M
    Post Max Size: 64M
    Upload Max Filesize: 64M
    Time Limit: 30
    Max Input Vars: 1000
    Display Errors: N/A

    — PHP Extensions

    cURL: Supported
    fsockopen: Supported
    SOAP Client: Installed
    Suhosin: Not Installed

    — Session Configuration

    Session: Disabled

    ### End System Info ###

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    Try switching to the default theme, deactivating all plugins excluding Contact Form 7, Classic Editor, Flamingo, WordPress Importer and Yoast SEO, and clearing all cache data.

    Why you are advised to deactivate plugins and switch to the default theme.

    Dear Takayuki,

    Eventually I found the issue. The theme had a “use place holder as value” script on it’s sitesearch. I disabled this piece of script and now it works just fine. This could be resolved by adding a “disable use place holder as value” script to the plugin so no one ever has to look for this ever again. I saw lot’s of people struggeling with this. they probably all have the same issue, more themes will use this option and a plugin is worth most when it works with all themes available.

    with kind regards,
    Tasmara van Ballegooij

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘CF7 unexpected result when combining * (required) text field with a placeholder’ is closed to new replies.