We've recently seen users blocked at the signature step or submitting with "blank" signatures. This seems to be browser/OS-specific. We tried updating the JS library in BlueprintKansas/ksvotes.org#635 and some debug in BlueprintKansas/ksvotes.org#639.
Now we've added a user_agent db column in BlueprintKansas/ksvotes.org#649 so we can track browser/OS more easily. Still looking for a clear pattern so we can determine a workaround.
We've recently seen users blocked at the signature step or submitting with "blank" signatures. This seems to be browser/OS-specific. We tried updating the JS library in BlueprintKansas/ksvotes.org#635 and some debug in BlueprintKansas/ksvotes.org#639.
Now we've added a
user_agentdb column in BlueprintKansas/ksvotes.org#649 so we can track browser/OS more easily. Still looking for a clear pattern so we can determine a workaround.