Gravity Forms

  • MCGWD

    (@mginop)


    1 day, 6 hours ago

    How would I go about preventing the caching of certain JS files? I have registration form set up with Gravity Forms and Authorize.net, but with the PC plugin turned on the form hangs when submitted. I’d like to exclude caching on the following plugin directories that contained the JavaScript files:

    /gravityforms/js/
    /wp-gateways/

    Can I add these directories into the do not cache pages field? Thanks in advance.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Mustafa Uysal

    (@m_uysl)

    1 day, 6 hours ago

    Hi @mginop,

    Powered Cache does not cache JavaScript files directly. However, if you mean excluding those files from JS optimization, you can add patterns like these:

    /gravityforms/js/(.*)
/wp-gateways/(.*)

    Also, if those forms rely on nonces, expired nonces may cause submission issues when the page is cached for too long. In that case, I recommend keeping the page cache TTL under 12 hours, or excluding the specific page where the forms are embedded from page cache.

    If you can share the page URL, I’d be happy to take a look.

    Regards,

    Thread Starter MCGWD

    (@mginop)

    1 day, 4 hours ago

    Thanks for the quick reply ! I’m not using any JavaScript optimization nor am I minifying the html. You can take a look at the page at: https://www.drivingright.org/graduated-driver-licensing/segment-1-mason-high-school/registration/

    Note I just use 4111111111111111 for the credit card number, and wait for error message. But it never arrives as the form just hangs.

    Also the correct directories are:
    /wp-content/plugins/gravityforms/js/(.*)
    /wp-content/plugins/gravityforms-authorize-net-gateway/js/(.*)

    • This reply was modified 1 day, 4 hours ago by MCGWD.
    Plugin Author Mustafa Uysal

    (@m_uysl)

    23 hours, 9 minutes ago

    I couldn’t reach the page. It returned ERR_CONNECTION_TIMED_OUT after a long wait.

    I also tried bypassing Powered Cache by adding ?nopoweredcache=1 to the end of the URL, but the issue still persisted.Could you please check the server error logs and see if there is anything related?

    Thread Starter MCGWD

    (@mginop)

    3 hours, 44 minutes ago

    Thanks for checking. I didn’t see an issue with the site being unavailable. I think I have this issue resolved now. Thanks for the support quick and response anyways!

    • This reply was modified 3 hours, 43 minutes ago by MCGWD.
Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.