When a new user clicks the "Activate account" link in the email, the Verify Account page opens with a "Checking Verification" popup window.
This window includes a "rolling circles" animation with text Please wait. And the waiting never ends...
Popup correctly instructs users to "Click if not redirect automatically", but how to make this work? In User Verification settings I have disabled to auto-login after verification and set redirect to Login page.
Hi MG,
When the "rolling circles" appear, please check your browser console for possible errors. I believe there might be some Javascript errors that are causing the circles to keep rolling. Once you find the error message, kindly let us know and we will provide you with a solution.
Hi Azizul,
I checked the browser console and found a few errors and three issues. Note, I’m not a web developer, so I just copied everything below.
CONSOLE—————————————
VM336:2 Uncaught TypeError: $.each is not a function
at :2:24
at t.activateScript (rocket-loader.min.js:1:11855)
at rocket-loader.min.js:1:11052
at t.run (rocket-loader.min.js:1:11259)
at rocket-loader.min.js:1:2907
at rocket-loader.min.js:1:8117
(anonymous) @ VM336:2
t.activateScript @ rocket-loader.min.js:1
(anonymous) @ rocket-loader.min.js:1
t.run @ rocket-loader.min.js:1
(anonymous) @ rocket-loader.min.js:1
(anonymous) @ rocket-loader.min.js:1
load (async)
t.runOnLoad @ rocket-loader.min.js:1
x @ rocket-loader.min.js:1
(anonymous) @ rocket-loader.min.js:1
(anonymous) @ rocket-loader.min.js:1
(anonymous) @ rocket-loader.min.js:1
jquery.js:3 [Deprecation] Listener added for a ‘DOMSubtreeModified’ mutation event. This event type is deprecated, and will be removed from this browser very soon. Usage of this event listener will cause performance issues today, and represents a large risk of future site breakage. Consider using MutationObserver instead. See https://chromestatus.com/feature/5083947249172480 for more information.
add @ jquery.js:3
(anonymous) @ jquery.js:3
each @ jquery.js:2
each @ jquery.js:2
ya @ jquery.js:3
on @ jquery.js:3
bind @ jquery.js:4
(anonymous) @ content.js:50
j @ jquery.js:2
k @ jquery.js:2
setTimeout (async)
(anonymous) @ jquery.js:2
i @ jquery.js:2
fireWith @ jquery.js:2
fire @ jquery.js:2
i @ jquery.js:2
fireWith @ jquery.js:2
ready @ jquery.js:2
setTimeout (async)
(anonymous) @ jquery.js:3
(anonymous) @ jquery.js:2
(anonymous) @ jquery.js:2
Show 20 more frames
Show less
verify-account/:1 Third-party cookie will be blocked. Learn more in the Issues tab.
jquery-migrate.min.js?ver=3.4.1:2 JQMIGRATE: Migrate is installed, version 3.4.1
ht-blocks-frontend.js?ver=1659598112:1 tabs-block-frontend loaded
verify-account/:1 Third-party cookie will be blocked. Learn more in the Issues tab.
ISSUES——————————————
Deprecated feature used
Unload event listeners are deprecated and will be removed.
1 source
jquery.js:3
Learn more: Check the feature status page for more details.
Deprecated feature used
DOM Mutation Events, including DOMSubtreeModified, DOMNodeInserted, DOMNodeRemoved, DOMNodeRemovedFromDocument, DOMNodeInsertedIntoDocument, and DOMCharacterDataModified are deprecated ( https://w3c.github.io/uievents/#legacy-event-types ) and will be removed. Please use MutationObserver instead.
1 source
jquery.js:3
Learn more: Check the feature status page for more details.
Learn more: This change will go into effect with milestone 127.
Reading cookie in cross-site context will be blocked in future Chrome versions
Cookies with the SameSite=None; Secure and not Partitioned attributes that operate in cross-site contexts are third-party cookies. In future Chrome versions, reading third-party cookies will be blocked. This behavior protects user data from cross-site tracking.
Please refer to the article linked to learn more about preparing your site to avoid potential breakage.
1 cookie
Name Domain & Path
ar_debug .region1.google-analytics.com/
Learn more: Prepare for phasing out third-party cookies
The error message might be caused by another plugin interacting with ours. Here’s what you can try:
Try deactivating all your plugins (except for the user verification plugin) and then reactivate them one by one. This will help you identify if another plugin is causing the issue.