Not working if form is invalid after update to 5.4

  • Resolved nataliia123

    (@nataliia123)


    4 years ago

    Console error is gotten when form that is submitted is invalid
    TypeError: Cannot read property ‘querySelector’ of null
    at a (index.js?ver=5.4:1)
    at Array.forEach (<anonymous>)
    at index.js?ver=5.4:1

    This place is erroring – querySelector(“.wpcf7-form-control”);r.classList.add(“wpcf7-not-valid”),r

Viewing 4 replies - 1 through 4 (of 4 total)
  • pca2014

    (@pca2014)

    1. CF7 5.4 is incompatible with caching, specifically combining and deferring JavaScript files, which will cause a performance hit.

    2. CF7 use of “nonces” means a website has to be re-caches every 12 or 24-hours, I think? This will obviously cause a performance hit when using CloudFlare since all of the files have to be re-cache and with something like CloudFlare ARGO where the cache is distributed almost all of the benefit will be lost.

    The bottomline is that this is a hassle and bad for performance.

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    Where can we see the website in question?

    Thread Starter nataliia123

    (@nataliia123)

    For example this form After sending the empty forms the console error is happened. Neither validations messages are displayed under the field nor in response-output. It is not a live site so I deactivated all unnecessary plugin, cleared cache – nothing helped

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    See Editing form template

    What content do you have in the Form tab panel?

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Not working if form is invalid after update to 5.4’ is closed to new replies.