I just spunned off a new Discourse instance on Digital Ocean droplet, and tried to sign up with my google account. The account got verified with google successfully, but Create Now button remains disabled. I tried changing Name and Username manually, but it remains disabled for me.
[Extra info if it helps: I spunned two Digital Ocean droplets consecutively, both time I got the same server IP address, on first droplet when I tried signing in with google it worked successfully, but on second droplet it didn’t work. The console didn’t show any error.]
@neil I don’t think we should be disabling the button here, I think we should pop up an alert if they click and something is wrong. Login is too important to have people blocked by minor JS errors resulting in a disabled button…
plus if the check is performed at button press time, there’s a bit more time for the server to respond with name checks, email checks, etc.
toggle-off “tos accept required” option in Admin > Site Settings > Legal
add the missing tos checkbox HTML to our plugin’s handlebars template
manage “tos accept required” on or off
The strange thing, on the other hand, the bug was not persistent.
Many users successfully created accounts during the last two months…
so, under certain circumstances the button may have been both active and disabled at the same time… because Schrödinger?
The signup with 3rd party problem with the disabled button shouldn’t happen anymore. I fixed it so the button will never be disabled in that case. The server will return errors if anything is wrong in the form.
@reese That’s a bigger problem… When we change our templates, plugins that are overwriting the templates might need to be updated. It’s strange that people were able to signup at all on your site after we added tosAcceptRequired.