michaewa
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Storefront] Button class “not-allowed”Just wanted to check if it was possible to get a list of all the events that would trigger that class being applied to the submit button?
Forum: Themes and Templates
In reply to: [Storefront] Button class “not-allowed”Thank you RK.
Nothing too scientific, but I looked through all the included CSS on that page and couldn’t find any reference to “not-allowed” other than Storefront.
Is there any way to get a list of all the events that would trigger that class being applied to the submit button? I’m reaching at this point, but I thought that might help me be able to recreate it.
Forum: Themes and Templates
In reply to: [Storefront] Button class “not-allowed”Thanks for the reply.
The iMember plugin has a “mini login” – basically just a username / password field combo with a submit button.
Some small percentage of users, when going to that login page see the “not-allowed” cursor and the greyed out submit button on that form.
I’ve not been able to recreate it myself, but what appears to happen is that the user visits the home page of the site, navigates to the login page (https://athealth.com/sign-in-or-register/), clicks the “Returning User” button, and then is unable to submit the form after entering their username / password combination.
Most recently this was reported by a user on a Windows 10 machine using an up to date Chrome browser.
I’ve looked into a few scenarios – concurrent logins, already logged in, etc. but none of them have panned out. Concurrent logins are permitted with iMember, and there is functionality that prevents the user from navigating to the login page if they are already logged in.
I hope that helps, if you have any suggestions for troubleshooting I would appreciate it!