Support » Plugin: Google Analytics Dashboard for WP by ExactMetrics (formerly GADWP) » Javascript error on the login page causing a plugin conflict

  • Resolved WFMattR

    (@wfmattr)


    Hi,

    I work on the Wordfence plugin, and we’ve had some users report a conflict with Google Analytics Dashboard for WP, when using our 2FA feature on the wp-login page.

    If “track form submit actions” is enabled on the “Events Tracking” tab of GADWP, this javascript error occurs when attempting to log in, because the analytics.js file is not loaded on the login page:
    ReferenceError: ga is not defined

    This error occurs even if Wordfence isn’t installed, but logins still work since the regular login button doesn’t rely on javascript, but we also add a handler to the login button, so the error above stops our script from running.

    Could the click handler near the end of front/js/tracking-analytics-events.js bail out if ga is undefined? (I’m assuming the login form is intentionally not tracked, but I’m not sure.) If you have a proposed fix, I’d be happy to test to make sure it resolves the conflict with Wordfence.

    Thanks!

    -Matt R

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support jaygidwitz

    (@jaygidwitz)

    Hi @wfmattr,

    Thank you for this information.

    We’ll get a fix out for this issue next Wednesday.

    – Jay

    Great, thanks Jay!

    -Matt R

    WFMattR

    (@wfmattr)

    Hi Jay,

    Any update on the timing of the release that will fix this issue? It has been a few weeks, so I’m hoping there is a new estimate we can give to users who have this issue. Thanks!

    -Matt R

    Plugin Support jaygidwitz

    (@jaygidwitz)

    Hi Matt,

    Sorry for the delay here.

    If it’s not out shortly today it will go out tomorrow.

    Cheers,

    -Jay

    Plugin Support jaygidwitz

    (@jaygidwitz)

    Hi Matt,

    Quick update: this release will go out on Tuesday.

    Sorry for the delay.

    -Jay

    Plugin Support jaygidwitz

    (@jaygidwitz)

    Hey @wfmattr,

    The update is out for this.

    Cheers,

    Jay

    Awesome, thanks Jay! From a quick test, it looks like this has solved the javascript issue.

    -Matt R

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.