Support » Plugin: Contact Form 7 » When are you going to fix the v5.4?

  • Version 5.4 broke all forms on all websites. 2 weeks ago since the update… Why hasn’t the team fixed this bug yet?? They only answer to ask about the website. It’s crazy.

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

    (@takayukister)

    What problems do you have?

    @takayukister I think the same issue as everybody else. Forms do not work any more. Spinning wheel when sending. Plugin doesnt work anymore with every form of caching. See the other recent threads. Only solution for now is to go back to the previous version. Please solve this.

    update, this error is not related to the issue. It happens with Brave browser when shields are enabled. So no error is in the console when using the form. Spinning wheel keeps loading. The form is sent but for the end user it seems the form is not working so they will retry.

    @takayukister there’s this error in every console of every website where I run Contact form 7 5.4:

    Failed to load resource: the server responded with a status of 403 () /wp-json/contact-form-7/v1/contact-forms/29442/refill?_locale=user

    Hope this will help to solve the issue with version 5.4

    • This reply was modified 2 months, 1 week ago by Jaap de Wit.

    Autoptimize conflicts with the latest version of Contact Form 7, but it does not seem to affect every setup.
    https://wordpress.org/support/topic/contact-form-7-major-update-breaking-js-optimization/

    Not sure if this is the case here.

    @cnxsoft I’m not using autoptimize. I’m using WPRocket but even when I disable it or exclude contact form 7 from cache it’s still not working. Only solution for now is to roll back to 5.3.2

    @takayukister Version 5.4 has serious issues. And a huge number of people use this plugin. To my mind, the wisest decision would be to release version 5.5 which will be just previous version 5.3.2 and put the new version back into beta testing. Or bug-messages to this forum will snowball.

    Thread Starter alberto3

    (@alberto3)

    @takayukister Are you kidding? Have you read ALL the messages of the last 2 weeks? The worst support ever. 2 full weeks waiting. Forms stopped working in the latest version. You should check the Error Console of any website with that version:

    Uncaught TypeError: Cannot set property ‘innerText’ of null
    at l (/plugins/contact-form-7/includes/js/index.js?ver=5.4:1)
    at /plugins/contact-form-7/includes/js/index.js?ver=5.4:1
    at Object.p [as reset] (/plugins/contact-form-7/includes/js/index.js?ver=5.4:1)
    at HTMLFormElement.<anonymous> (/plugins/contact-form-7/includes/js/index.js?ver=5.4:1)
    at /plugins/contact-form-7/includes/js/index.js?ver=5.4:1

    They aren’t interested in solving the major error that thousands of people have. Just leave a 1 star review, move on and find another contact form.

    Not only is not working but also adding a lot of new js that slows the website.

    https://blog.futtta.be/2021/02/25/contact-form-7-update-breaks-autoptimize-js-optimization-workaround/

    The arrogant attitude of the plugin author has made me move to wpforms, a very easy to use plugin.

    @everyone

    CF7 version 5.4. has a conflict with caching combining/deferring Javascript. If you have WP-Rocket they have a fix. But that’s only half the problem. CF7 now uses nonces (security token) and it has to be refresh every 12 or 24 hours, which means you’ll have to clear your cache once or twice a day.

    Look down the forum and you’ll see tons of comments about this.

    Be forewarned that if you’re logged in as admin it may appear to work because you’re likely bypassing the cache. You either need to be logged out of WordPress or access the page through a web browser in private mode to test if it’s working for public users.

    @everyone

    I’m only suggesting these solutions as a workaround until the author fixes what’s broken. this updated design is really bad for performance, especially if you use something like CloudFlare or Cloudflare Argo.

    With the cache, a similar problem was with caldera-forms. I’m not sure.

    https://calderaforms.com/doc/caldera-forms-submission-rejected-token-invalid-mean/

    • This reply was modified 2 months, 1 week ago by vaka2vaka.
    • This reply was modified 2 months, 1 week ago by vaka2vaka.

    Same problem here.

    Thanks, I’ll be using WPforms from now on.

Viewing 15 replies - 1 through 15 (of 17 total)
  • You must be logged in to reply to this topic.