• Resolved Ponce918

    (@ponce918)


    After installing Wordfence and activating the plugin, I cannot get past the step where I am supposed to enter my Admin Contact Info, opt-in or out (Yes/No) of the mailing list and agree to terms. After entering my email, selecting Yes (or No), and checking the box, the Continue button never enables so I can click it.

    During each of those interactions, I notice a JS error in the Chrome debug console.

    Note: I am on a managed WordPress hosting account, but as far as I know my host (1&1 IONOS) does not block this plugin and in fact, they promote it on one of their WordPress marketing pages. I have not had issues with any other plugins I’ve tried on my site.

    Below are the three errors from the console:

    wfglobal.1566486436.js?ver=7.4.0:193 Uncaught TypeError: u is not a function
    at sjcl.hash.sha256.finalize (wfglobal.1566486436.js?ver=7.4.0:193)
    at Function.sjcl.hash.sha256.hash (wfglobal.1566486436.js?ver=7.4.0:191)
    at Object.hashSHA256 (wfglobal.1566486436.js?ver=7.4.0:104)
    at Object.isEmailBlacklisted (wfglobal.1566486436.js?ver=7.4.0:107)
    at Object.parseEmails (wfglobal.1566486436.js?ver=7.4.0:124)
    at plugins.php:935
    finalize @ wfglobal.1566486436.js?ver=7.4.0:193
    sjcl.hash.sha256.hash @ wfglobal.1566486436.js?ver=7.4.0:191
    hashSHA256 @ wfglobal.1566486436.js?ver=7.4.0:104
    isEmailBlacklisted @ wfglobal.1566486436.js?ver=7.4.0:107
    parseEmails @ wfglobal.1566486436.js?ver=7.4.0:124
    (anonymous) @ plugins.php:935
    setTimeout (async)
    (anonymous) @ plugins.php:934
    dispatch @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-widget,jquery-ui-position,jquery-ui-core,jquery-ui-mouse,jquery-ui-slider,jquery-ui-t&load[]=ooltip&ver=5.2.3:3
    r.handle @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-widget,jquery-ui-position,jquery-ui-core,jquery-ui-mouse,jquery-ui-slider,jquery-ui-t&load[]=ooltip&ver=5.2.3:3

    wfglobal.1566486436.js?ver=7.4.0:193 Uncaught TypeError: u is not a function
    at sjcl.hash.sha256.finalize (wfglobal.1566486436.js?ver=7.4.0:193)
    at Function.sjcl.hash.sha256.hash (wfglobal.1566486436.js?ver=7.4.0:191)
    at Object.hashSHA256 (wfglobal.1566486436.js?ver=7.4.0:104)
    at Object.isEmailBlacklisted (wfglobal.1566486436.js?ver=7.4.0:107)
    at Object.parseEmails (wfglobal.1566486436.js?ver=7.4.0:124)
    at plugins.php:935
    finalize @ wfglobal.1566486436.js?ver=7.4.0:193
    sjcl.hash.sha256.hash @ wfglobal.1566486436.js?ver=7.4.0:191
    hashSHA256 @ wfglobal.1566486436.js?ver=7.4.0:104
    isEmailBlacklisted @ wfglobal.1566486436.js?ver=7.4.0:107
    parseEmails @ wfglobal.1566486436.js?ver=7.4.0:124
    (anonymous) @ plugins.php:935
    setTimeout (async)
    (anonymous) @ plugins.php:934
    dispatch @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-widget,jquery-ui-position,jquery-ui-core,jquery-ui-mouse,jquery-ui-slider,jquery-ui-t&load[]=ooltip&ver=5.2.3:3
    r.handle @ load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-widget,jquery-ui-position,jquery-ui-core,jquery-ui-mouse,jquery-ui-slider,jquery-ui-t&load[]=ooltip&ver=5.2.3:3

    wfglobal.1566486436.js?ver=7.4.0:193 Uncaught TypeError: u is not a function
    at sjcl.hash.sha256.finalize (wfglobal.1566486436.js?ver=7.4.0:193)
    at Function.sjcl.hash.sha256.hash (wfglobal.1566486436.js?ver=7.4.0:191)
    at Object.hashSHA256 (wfglobal.1566486436.js?ver=7.4.0:104)
    at Object.isEmailBlacklisted (wfglobal.1566486436.js?ver=7.4.0:107)
    at Object.parseEmails (wfglobal.1566486436.js?ver=7.4.0:124)
    at HTMLLIElement.<anonymous> (plugins.php:925)
    at HTMLLIElement.dispatch (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-widget,jquery-ui-position,jquery-ui-core,jquery-ui-mouse,jquery-ui-slider,jquery-ui-t&load[]=ooltip&ver=5.2.3:3)
    at HTMLLIElement.r.handle (load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,utils,jquery-ui-widget,jquery-ui-position,jquery-ui-core,jquery-ui-mouse,jquery-ui-slider,jquery-ui-t&load[]=ooltip&ver=5.2.3:3)

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hey @ponce918,

    It sounds like there might be a conflict either with the theme or one of the plugins you’re using, could you try temporarily switching to a default theme if you’re not already using one and disabling all other plugins then reactivating them one by one to see if the issue persists?

    To do so I recommend the Health Check & Troubleshooting plugin which allows you to disable all plugins and switch to a default theme, but only for your user.

    Please let me know how it goes.

    Thanks,

    Gerroald

    Thread Starter Ponce918

    (@ponce918)

    I suspected as much. I exported my production site to a sandbox instance and found the incompatible plugin via process of elimination.

    mb.miniAudioPlayer

    https://ww.wp.xz.cn/support/plugin/wp-miniaudioplayer/

    I can alert that plugin author, but is there evidence suggesting that the issue is with their plugin vs. Wordfence?

    Hi @ponce918,

    Very nice debugging work! I see that you’re a developer, so I’ll provide more technical details here:

    During the initial Wordfence setup, your email address is hashed and checked with a list of blacklisted addresses.

    The library we use to hash strings uses a global function called u. The plugin wp-miniaudioplayer also uses the same name for a variable.

    This caused Wordfence’s script to crash whenever trying to hash your email address, and so the continue button would never enable:

    wfglobal.js: Uncaught TypeError: u is not a function

    In the meantime, you can temporarily disable wp-miniaudioplayer so that the Wordfence installation will work.

    I’ve gone ahead and submitted a bug report to the Wordfence team, and this should be fixed soon.

    Dave

    Thread Starter Ponce918

    (@ponce918)

    OK, great – thanks. I did confirm on my sandbox that Wordfence installs once wp-miniaudioplayer is disabled. I’ll consider that option.

    Hi again,

    I’m glad to report that this bug has been filed and should be fixed in future releases of Wordfence. (Internal ref: FB8972)

    Dave

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Continue Button Disabled on Activation Flow – JS Errors’ is closed to new replies.