Button class “not-allowed”

  • I’m using the storefront theme and WooCommerce along with a membership site plugin called iMember360.

    I have an infrequent issue where a user will be on the account login page but the “not-allowed” class is applied to the submit button so they cannot log in.

    I’ve looked through all the CSS that could be applied on that page, and it appears that it is being applied by Storefront.

    I wanted to see if there was a short list of scenarios that would trigger that class?

    input[type=submit]:disabled{opacity:.5!important;cursor:not-allowed}.added_to_cart.disabled:hover

    I’m not able to recreate the issue, but have customers report it pretty frequently on a variety of devices and (current) browsers.

    Thanks in advance!

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

  • Hi @michaewa

    The “not-allowed” class is added to a button in various situations, when the system won’t allow a button to be clicked.

    Can you give us a specific example of where (and when) you see this exactly?

    Thread Starter michaewa

    (@michaewa)

    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!

    RK a11n

    (@riaanknoetze)

    Thanks for the extra information here – I’ve just tried to replicate that on my side but came up short as well.

    You mentioned that it looks like Storefront might be causing that: Can you share a bit more detail on why Storefront is implicated here?

    Thread Starter michaewa

    (@michaewa)

    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.

    Thread Starter michaewa

    (@michaewa)

    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?

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Button class “not-allowed”’ is closed to new replies.