Sitewide Java Script bug & “Save settings” button not working in Async

  • Resolved merlinthewarlock

    (@merlinthewarlock)


    4 years, 9 months ago

    Recently, I have had a sitewide javascript error that affects multiple plugins on the backend such as Elementor, Advanced Custom Fields, and even Async JS (e.g. https://support.advancedcustomfields.com/forums/topic/buttons-not-working-in-field-group/#post-132270).

    In Async – I am trying to change the settings of JQuery to be excluded (and other settings), but the “Save Settings” button is not working. When I click, the page doesn’t refresh or anything. I opened developer tools and no errors or warnings show up.

    I am not sure if Async is causing the problem as the JS problem in other plugins persists even after deactivating Async.

    Other factors to consider: 1] Siteground changed my servers yesterday 2] I upgraded my PHP version to 7.4 (but the problem still persists after reverting to 7.3)

    Thank you in advance for your speedy reply.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    -> AsyncJS does not act on pages on the back-end (wp-admin)
    -> the problem remains when AsyncJS is not active

    so my conclusion: this is not due to AsyncJS really …

    what JS errors do you see on the browser console when trying to save settings?

    Thread Starter merlinthewarlock

    (@merlinthewarlock)

    That’s the thing – I don’t see any JS errors in the browser console. It just says: “JQMIGRATE: Migrate is installed, version 1.4.1”.

    Could the problem be due to Autoptimize? When I cleared the “Autoptimize” cache, the JS error in Advanced Custom Fields went away for 1 minute before coming back.

    Beyond that, do you know where I would look for corrupt JS files?

    Thanks!

    Thread Starter merlinthewarlock

    (@merlinthewarlock)

    I fixed it!!!!!

    I was creating a Chrome extension and had “developer mode” on. After I turned it off, everything went back to normal in all my plugins.

    I guess developer mode autobreaks JavaScript as a security measure?

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    no experience with chrome extension development & the impact of “developer mode”, but great find, good to know merlinthewarlock ??

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Sitewide Java Script bug & “Save settings” button not working in Async’ is closed to new replies.