JS Combination + Forminator Turnstile

  • delanthear

    (@delanthear)


    1 day, 12 hours ago

    It looks like JS combination breaks turnstile when being used by Forminator. You can’t exclude the file from combination as it looks like the plugin is looking for script tag that is output into the head of the page. There also appears to be no forminator JS available to exclude either. Turning off JS combination entirely fixes it.

    Uncaught TurnstileError: [Cloudflare Turnstile] Could not find Turnstile valid script tag, some features may not be available.
    at y (siteground-optimizer-combined-js-c12ccd219ce92e5bdbe46254959ed316.js:77:10932)
    at Vr (siteground-optimizer-combined-js-c12ccd219ce92e5bdbe46254959ed316.js:77:11685)
    at siteground-optimizer-combined-js-c12ccd219ce92e5bdbe46254959ed316.js:77:59663
    at siteground-optimizer-combined-js-c12ccd219ce92e5bdbe46254959ed316.js:77:61553

Viewing 1 replies (of 1 total)
  • Plugin Support Simeon Boev

    (@k3llanved)

    5 hours ago

    Hello @delanthear,

    Can you provide a bit more information about the setup you use with Forminator and Turnstile on your end so we can recreate the issue and test it further. Is the issue present regardless of configuration used or specific settings are triggering the output in question.

    The dropdown menu automatically displays JavaScript files registered through standard coding practices. If a script was added using non-standard methods, it won’t appear by default. To include these scripts, you must apply an exclusion filter within your active theme’s functions.php file. Instead of referencing the script file name, you will need to use the specific handle associated with that script. The filter that you would need to use to exclude scripts from being combined:

    https://www.siteground.com/tutorials/wordpress/speed-optimizer/custom-filters/#plugin-compatibility

    One of the recommended methods to find the handle you need is to use WordPress’ native debug mode:

    One of the recommended methods to find the handle you need is to use WordPress’ native debug mode:
    define( 'WP_DEBUG', true );
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );

    Best Regards,

    Simeon Boev

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.