JS errors/conflicts and forms not working after update

  • Resolved cjjkees

    (@cjjkees)


    2 years, 8 months ago

    After the latest update, there seems to be a conflict between Contact Form 7 and (in my case) Search & Filter Pro. My forms don’t work and I’m seeing these errors in the DevTools Console: (Uncaught) TypeError: t.replace is not a function.

    When I roll back the plugin to 5.6, everything works fine.

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

    (@takayukister)

    Where can we see the website in question?

    Thread Starter cjjkees

    (@cjjkees)

    I can provide you a URL to the staging environment. Is there a way I can send you this in private?

    I am also experiencing js conflicts on 5.6.1 which stop the form working completelt. I have rolled back to 5.6 and now have no issues. In my case, it conflicts with Search & Filter Pro when using version 5.6.1

    Please see console output below.

    
jquery-migrate.min.js?ver=3.3.2:2 JQMIGRATE: Migrate is installed, version 3.3.2
DevTools failed to load source map: Could not load content for chrome-extension://eakacpaijcpapndcfffdgphdiccmpknp/scripts/content_page.map: System error: net::ERR_BLOCKED_BY_CLIENT
XHR finished loading: GET "<URL>".
XHR finished loading: GET "<URL>".
XHR finished loading: GET "<URL>".
XHR finished loading: GET "<URL>".
XHR finished loading: GET "<URL>".
XHR finished loading: GET "<URL>".
XHR finished loading: GET "<URL>".
XHR finished loading: GET "<URL>".
XHR finished loading: GET "<URL>".
XHR finished loading: GET "<URL>".
XHR finished loading: GET "<URL>".
XHR finished loading: GET "<URL>".
XHR finished loading: GET "<URL>".
XHR finished loading: GET "<URL>".
XHR finished loading: GET "<URL>".
search-filter-build.min.js?ver=2.5.12:1 Uncaught TypeError: t.replace is not a function
    at String.replaceAll (search-filter-build.min.js?ver=2.5.12:1:641)
    at _ (index.js?ver=5.6.1:formatted:585:92)
    at index.js?ver=5.6.1:formatted:674:31
    at NodeList.forEach (<anonymous>)
    at L (index.js?ver=5.6.1:formatted:673:56)
    at index.js?ver=5.6.1:formatted:723:13
    at index.js?ver=5.6.1:formatted:94:42
    at i (index.js?ver=5.6.1:formatted:142:16)
    at Object.k [as reset] (index.js?ver=5.6.1:formatted:704:9)
    at HTMLFormElement.<anonymous> (index.js?ver=5.6.1:formatted:889:19)
String.replaceAll @ search-filter-build.min.js?ver=2.5.12:1
_ @ index.js?ver=5.6.1:formatted:585
(anonymous) @ index.js?ver=5.6.1:formatted:674
L @ index.js?ver=5.6.1:formatted:673
(anonymous) @ index.js?ver=5.6.1:formatted:723
(anonymous) @ index.js?ver=5.6.1:formatted:94
i @ index.js?ver=5.6.1:formatted:142
k @ index.js?ver=5.6.1:formatted:704
(anonymous) @ index.js?ver=5.6.1:formatted:889
(anonymous) @ index.js?ver=5.6.1:formatted:885
load (async)
EventTarget.addEventListener @ play.min.js?ver=10.0:1
T @ index.js?ver=5.6.1:formatted:884
(anonymous) @ index.js?ver=5.6.1:formatted:941
(anonymous) @ index.js?ver=5.6.1:formatted:941
recaptcha__en.js:576 XHR finished loading: POST "https://www.google.com/recaptcha/api2/reload?k=6Lc1BbsUAAAAAKOASegqE93nRNHfjGUCXzqUFCNe".
K5.send @ recaptcha__en.js:576
(anonymous) @ recaptcha__en.js:147
E.<computed>.bq.T @ recaptcha__en.js:592
(anonymous) @ recaptcha__en.js:19
Vf.dQ @ recaptcha__en.js:588
Vf.j2 @ recaptcha__en.js:588
bq.send @ recaptcha__en.js:589
(anonymous) @ recaptcha__en.js:594
Promise.then (async)
(anonymous) @ recaptcha__en.js:594
(anonymous) @ recaptcha__en.js:368
Bq @ recaptcha__en.js:421
Ud.send @ recaptcha__en.js:593
(anonymous) @ recaptcha__en.js:111
(anonymous) @ recaptcha__en.js:78
next @ recaptcha__en.js:235
(anonymous) @ recaptcha__en.js:38
(anonymous) @ recaptcha__en.js:38
(anonymous) @ recaptcha__en.js:115
(anonymous) @ recaptcha__en.js:110
x.H @ recaptcha__en.js:289
(anonymous) @ recaptcha__en.js:329
(anonymous) @ recaptcha__en.js:264
Bq.then.Bq.T @ recaptcha__en.js:524
(anonymous) @ recaptcha__en.js:354
Promise.then (async)
dW @ recaptcha__en.js:155
(anonymous) @ recaptcha__en.js:120
(anonymous) @ recaptcha__en.js:384
(anonymous) @ recaptcha__en.js:408
(anonymous) @ recaptcha__en.js:368
(anonymous) @ recaptcha__en.js:177
D$.N @ recaptcha__en.js:626
index.js?ver=5.6.1:formatted:117 Fetch finished loading: GET "https://www.mysite.com/wp-json/contact-form-7/v1/contact-forms/48384/feedback/schema".
(anonymous) @ index.js?ver=5.6.1:formatted:117
(anonymous) @ index.js?ver=5.6.1:formatted:669
(anonymous) @ index.js?ver=5.6.1:formatted:94
(anonymous) @ index.js?ver=5.6.1:formatted:726
(anonymous) @ index.js?ver=5.6.1:formatted:94
i @ index.js?ver=5.6.1:formatted:142
T @ index.js?ver=5.6.1:formatted:909
(anonymous) @ index.js?ver=5.6.1:formatted:941
(anonymous) @ index.js?ver=5.6.1:formatted:941

    Same error here! Last Contact Form version 5.6.1 and Search & Filter Pro plugin

    I have just popped a ticket into S&F PRO teams as well to see if we can get this resolved asap. It would be good if we could get some feedback from @takayukister aswell as it is most certainly the CF7 5.6.1 update causing the issue.

    To anyone experiencing an issue with S&F Pro and CF7, I allowed the S&F team to investigate the issue on my staging site and the issue has been resolved. Any update will be available shortly for S&F PRO.

    Same here… and I do not even use: S&F PRO.

    Rollback to 5.5.6.1 solves the matter.

    • This reply was modified 2 years, 7 months ago by peps23.

    Hi all, we released an update with a fix for this last Thursday.

    The issue was we were using an old polyfill for the JavaScript function String.replaceAll()

    Since this is now supported by all modern browsers, the solution was to remove this from our codebase.

    @peps23 you might want to check which plugin is causing this issue, and if it is exactly the same then you can contact the plugin/theme author with this information. IMO this specific issue (where the error comes from the use of replaceAll()) is not a bug with CF7.

    Thanks
    ~ Ross

    Thanks for the update.

    “we released an update with a fix for this last Thursday.”
    > Being version 5.6.1?

    The thing is, the issue is present with version: 5.6.1 and not with version: 5.5.6.1.

    Thanks for the most recent update, Version 5.6.2. It works as it should.

    So I need to be sure I have this straight. I’m using both Contact Form 7 and Search & Replace Pro 2.4.5. One of my forms recently stopped working and I reverted to 5.6 and it is again working.

    I just tried upgrading to CF7 version 5.6.2 and it again stopped working. So it appears that @codeamp is saying that CF7’s latest now works with the latest of Search & Replace Pro, correct? I’ve resisted relicensing S&R Pro for quite some time because it did not seem to be progressing in version 2.x, then I’ve seen a very long wait for version 3.x. This puts me in a bind if I want to move forth with CF7. Ross, am I clear on this?

    @mhair The update was for Search and Filter Pro NOT Search and Replace Pro. You will need to contact the plugin developer for that plugin.

    Hey @mhair

    Sounds like you might have got the name mixed up but based on the version numbers you supplied I assume we’re all talking about Search & Filter Pro.

    It sounds like your assumption is correct, in order to use Search & Filter with the latest CF7 you’ll need to update your copy of Search & Filter to 2.5.13.

    Thanks

    Seeing this same issue today with CF7 v5.7.2 and S&F Pro v2.5.13

    I’ve blocked updates for the plugin since Version 5.5.6.1?as it only gives issues.

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘JS errors/conflicts and forms not working after update’ is closed to new replies.